From: Hans de Goede <hdegoede@redhat.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] [RFC] Asus ATK0110 ACPI hwmon driver
Date: Sun, 04 Jan 2009 19:14:25 +0000 [thread overview]
Message-ID: <49610A91.9010907@redhat.com> (raw)
In-Reply-To: <20081229205537.GA11072@dreamland.darkstar.lan>
Luca Tettamanti wrote:
<snip>
>> So summarizing:
>> 1) I like it :)
>> 2) I see some opportunities for removing duplicate code /
>> simplifying (only one list).
>> 3) Blocker: must protect against userspace abuse causing lots of IO /
>> an ACPI call storm
>> 4) Blocker: we must make sure we do not have ACPI and native IC drivers
>> banging IO's of the same IC
>
> 2 has been taken care of
Nice! One small mistake though, you forgot to do the value *= 100 when its a
temp sensor in the show_limitX functions.
> will do 3.
Ok.
> About 4: not my fault ;) The IO region
> of the SMBUS controller is reserved by the firmware; once the resource
> enforcing is set to strict the drivers will be exclusive.
Ack, I'm not claiming that this is your fault. Still this is something which
must be fixed before we can drop the atk0110 driver in to the mainline, esp. as
it will autoload when build.
> There's is of
> course the possibility of broken firmwares where the IO range is not
> marked as reserved (I wouldn't be suprised...).
Yeah I know, well since this is all Asus only, lets hope the IO reservations
are done properly on all Asus motherboards. I prefer not to try and think about
what if there are Asus boards where this does not hold true.
> Here's another iteration of the patch, I'll implement caching ASAP.
Besides the value *= 100 in case of temp sensor for the limits, I have one
small nitpick left, I think that the atk_create_files and atk_remove_files have
lost their value as separate functions, and that it would be better to just
move the code to where they all called all in all this would be a reduction in
the number of lines, and more importantly if someone tries to follow the code
flow while reading through the code it is one less function call / jump to
follow, while figuring out what is exactly happening.
Regards,
Hans
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2009-01-04 19:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-29 20:55 [lm-sensors] [RFC] Asus ATK0110 ACPI hwmon driver Luca Tettamanti
2008-12-30 14:01 ` Gabriel C
2008-12-30 14:09 ` Luca Tettamanti
2008-12-30 14:28 ` Gabriel C
2009-01-01 22:09 ` Hans de Goede
2009-01-01 22:10 ` Hans de Goede
2009-01-04 12:32 ` Hans de Goede
2009-01-04 14:56 ` Iain Paton
2009-01-04 18:08 ` Luca Tettamanti
2009-01-04 19:14 ` Hans de Goede [this message]
2009-01-04 21:23 ` Luca Tettamanti
2009-01-04 22:13 ` Hans de Goede
2009-01-05 17:25 ` Luca Tettamanti
2009-01-05 17:26 ` Luca Tettamanti
2009-01-05 18:12 ` Iain Paton
2009-01-05 19:00 ` Hans de Goede
2009-01-05 20:10 ` Luca Tettamanti
2009-01-06 8:20 ` Hans de Goede
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49610A91.9010907@redhat.com \
--to=hdegoede@redhat.com \
--cc=lm-sensors@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.