From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Finn Thain <fthain@telegraphics.com.au>
Cc: linux-kernel@vger.kernel.org, linux-m68k@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, Darren Hart <dvhart@infradead.org>,
ibm-acpi-devel@lists.sourceforge.net,
platform-driver-x86@vger.kernel.org
Subject: Re: [RFC 07/24] x86/thinkpad_acpi: Use arch_nvram_ops methods instead of nvram_read_byte() and nvram_write_byte()
Date: Sun, 31 May 2015 11:34:22 -0300 [thread overview]
Message-ID: <20150531143422.GA12337@khazad-dum.debian.net> (raw)
In-Reply-To: <alpine.LNX.2.00.1505311605420.23528@nippy.intranet>
On Sun, 31 May 2015, Finn Thain wrote:
> On Sun, 31 May 2015, Henrique de Moraes Holschuh wrote:
> > On Sun, 31 May 2015, Finn Thain wrote:
> > > Make use of arch_nvram_ops in the thinkpad_acpi driver so that the
> > > nvram_* function exports can be removed.
> > >
> > > This patch series was tested on a ThinkPad T43.
> >
> > Can you describe how you did the testing? A specific procedure is
> > required to test the hotkey NVRAM polling codepaths (which will read
> > several NVRAM bytes @10Hz by default) in a T43...
> >
> > > Signed-off-by: Finn Thain <fthain@telegraphics.com.au>
> >
> > The patch looks correct, so I don't expect any problems.
> >
> > Provided that your test procedure did enable hotkey NVRAM polling in the
> > T43 and your hotkeys all still worked fine, you have my Acked-by.
>
> The procedure I used was this,
>
> 1. $ xev
> 2. # rmmod thinkpad_acpi
> 3. Press <Access IBM> key and confirm that xev does not report any
> events.
> 4. # modprobe thinkpad_acpi
> 5. Press <Access IBM> key and confirm that xev now reports the key press
> events.
>
> Is this sufficient?
No. Please try:
modprobe thinkpad_acpi
echo 0xfb88c0 > /sys/devices/platform/thinkpad_acpi/hotkey_source_mask
test the hotkeys. Please test several of them, as not all of them are
available through NVRAM polling... at least Fn+SPACE, Fn+F1..FN+F12
Please test the brightness keys. In the T43 we use "direct EC mode", which
depends on the NVRAM to sync with the SMBIOS firmware.
to reset the driver to normal mode, it is enough to do this:
echo 0 > /sys/devices/platform/thinkpad_acpi/hotkey_source_mask
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
next prev parent reply other threads:[~2015-05-31 14:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150531010132.289674310@telegraphics.com.au>
2015-05-31 1:01 ` [RFC 07/24] x86/thinkpad_acpi: Use arch_nvram_ops methods instead of nvram_read_byte() and nvram_write_byte() Finn Thain
2015-05-31 4:11 ` Henrique de Moraes Holschuh
2015-05-31 6:15 ` Finn Thain
2015-05-31 14:34 ` Henrique de Moraes Holschuh [this message]
[not found] ` <20150531143422.GA12337-ZGHd14iZgfaRjzvQDGKj+xxZW9W5cXbT@public.gmane.org>
2015-06-02 10:09 ` Henrique de Moraes Holschuh
2015-06-03 3:34 ` Darren Hart
2015-06-03 7:38 ` Finn Thain
2015-06-03 10:37 ` Henrique de Moraes Holschuh
2015-06-04 5:14 ` Darren Hart
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=20150531143422.GA12337@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=dvhart@infradead.org \
--cc=fthain@telegraphics.com.au \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=platform-driver-x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox