Proposal /sys/bus/class/hwmon/hwmon#/device/foo#_label

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Am Sonntag 08 April 2007 20:56 schrieb Hans de Goede:

> >
> > Good point. Anyway, most sensor drivers have no way of knowing which of
> > their inputs are actually used. The LM93 driver I'm currently working on
> > is a monster that creates about 160 (!) sysfs files. I don't find it easy
> > to judge what's worse, having a few unused sysfs files or a large table
> > in kernel space.
>
> Only 160? My abituguru 1/2 driver creates 177 for my motherboard and even
> more on some others (it can detect used versus unused inputs). And the
> abituguru3 driver can create 230 with known motherboards, and if i wouldn't
> use the table approach it would create 384 entries. Sorry I'm bragging here
> I couldn't help myself, and hopefully this also makes it even clearer why I
> went with the table approach.
>
> Also notice that the table (except for the used entry) could be made so
> that it is freed after module initialisation (currently it isn't).
>

That's not bragging... I thank you for your explanations!

Cheers,
Hans




[Index of Archives]     [Linux Kernel]     [Linux Hardware Monitoring]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux