From: Peter Feuerer <peter@piie.net>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Acer Aspire One fan control
Date: Fri, 13 Feb 2009 19:59:16 +0100 [thread overview]
Message-ID: <cone.1234551556.57236.4642.1000@onepiie> (raw)
In-Reply-To: <20090213134024.GA26549@srcf.ucam.org>
Matthew Garrett writes:
> That depends on how you're doing it. Is the code available somewhere?
Just cleaned up the code and released it on my homepage, you can download
it from: http://piie.net/files/acerhdf_kmod-0.2.tar.gz
> If
> these io ports are also used by the firmware then you'll need to find
> ACPI methods to call to perform the fan control.
I get the temperature by calling ec_read(0x58) and can read/write the state
of the fan by ec_write to / ec_read from 0x55. Actually I don't know if
those embedded controller registers are used by the firmware. How can I find
it out?
> If there aren't any
> then it's not safe to have a driver to do this.
I think there should not be a problem when calling ec_write and ec_read
from my kernel module, as those functions are atomic. Or am I wrong?
--peter
next prev parent reply other threads:[~2009-02-13 18:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 20:37 Peter Feuerer
2009-02-12 21:03 ` Ralf Hildebrandt
2009-02-12 21:14 ` Peter Feuerer
2009-03-09 10:54 ` Maxim Levitsky
2009-02-13 10:35 ` Thomas Renninger
2009-02-13 19:34 ` Peter Feuerer
2009-02-13 13:40 ` Matthew Garrett
2009-02-13 18:59 ` Peter Feuerer [this message]
2009-02-13 19:18 ` Matthew Garrett
2009-02-13 19:45 ` Peter Feuerer
2009-02-27 18:58 ` [PATCH] acerhdf: " Peter Feuerer
[not found] ` <1235763653.24506.6.camel@localhost>
2009-02-28 18:58 ` Peter Feuerer
2009-03-01 14:38 ` Matthew Garrett
2009-03-26 22:22 ` Peter Feuerer
2009-04-01 12:44 ` Peter Feuerer
2009-04-12 20:49 ` Peter Feuerer
2009-04-04 10:51 ` Peter Feuerer
2009-03-01 15:27 ` Ed Tomlinson
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=cone.1234551556.57236.4642.1000@onepiie \
--to=peter@piie.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®