Re: [PATCH] base: add sysfs socs info

[Kay Sievers]

On Wed, Dec 15, 2010 at 08:39, Jean-Christophe PLAGNIOL-VILLARD
<plagnioj@xxxxxxxxxxxx> wrote:
>> > >
>> > > Also, isn't this information already in /proc/cpu/ today?
>> > no all this information are not present in /proc/cpu and a cpu is not a soc
>> >
>> > basicaly on a board you will have one soc but some boards have more as example
>> > some ST boards you have two sh4 soc or on some amcc you have two powerpc soc
>> >
>> > with these information you are allow to dynamise the userspace based on the
>> > soc or the companion soc and also be able to display this information in a UI
>>
>> Ok, but then why not make it "real" devices and not sysdev? ÂWe are
>> trying to fix the sysdev code to be semi-real devices, so you might as
>> well make them real ones now.
> ok I base my work on drivers/base/cpu.c
>
> where we also use sysdev
>
> can we point me a code how you want I implement it

Sysdevs devices in general are really broken concept. They duplicate
all the usual class/bus/subsystem logic in some stupid custom way,
which does not fit into the rest of the driver model. They have a have
broken event handling, so that  udev/libudev can not even "see" them
properly.

Create your own bus "soc", and register a device "id" there which has
these attributes in a group, which is assigned to the device before it
is registered.

Or maybe (really no idea ow how that fits) use the "dmi" class's
device "id", if that fits, or create a "soc" device in the "dmi" class
that has all these attributes.

Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/