From: "Miguel Gómez" <magomez@igalia.com>
To: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>
Cc: don@syst.com.br, mjg@redhat.com,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1 v2] classmate-laptop: Add support for Classmate V4 accelerometer.
Date: Wed, 18 Jul 2012 15:53:48 +0200 [thread overview]
Message-ID: <5006BFEC.1010407@igalia.com> (raw)
In-Reply-To: <20120717224749.GA20813@nautilus.holoscopio.com>
> On Fri, Jun 29, 2012 at 03:39:48PM +0200, Miguel Gómez wrote:
>> Classmate V4 laptop includes a new accelerometer that can't be handled by
>> previous driver. This patch adds a new driver to handle it.
>>
>> Signed-off-by: Miguel Gómez <magomez@igalia.com>
>
> Hi, Miguel.
>
> This seems OK to me. Thanks for this work. Do you have the other
> functionality of the driver working? I am interested to know if you have
> the function buttons working.
Hi Thadeu
I've been giving a look to the buttons code. Currently they are not
working because the hardware id reported by the device (FNBT0000) is not
the same as the one defined by the driver (FnBT0000), as you an one of
my colleagues commented in this thread:
https://lkml.org/lkml/2011/6/21/341
I've replaced the id in the driver to FNBT0000 and it made the buttons
work like a charm (enabling control of the backlight and LAN as well).
To ensure compatibility with older versions of the kernel, a new id can
be added (FNBT0000) besides the existent one (FnBT0000), and that works
as well (as proposed in the thread).
It seems that this problem got a bit forgotten in the lists. Quoting
yourself from the last email in the thread:
> I am copying the acpi list and Len Brown to see if they can tell us
> which one should be the right solution:
>
> 1) reverting the patch in acpica that puts all names in uppercase
> 2) using a case-insensitive match in acpi bus driver
> 3) using uppercase name in classmate-laptop driver
I think the easiest and less risky way to fix this is by adding a new
hardware id (as proposed in the thread's patch), as it doesn't add any
side effects (that the other solutions might add), and it doesn't break
the behaviour of the old code.
What do you think?
Regards!
--
Miguel Gómez
Igalia - http://www.igalia.com
next prev parent reply other threads:[~2012-07-18 13:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 12:46 [PATCH 0/1] Add support for Classmate V3 accelerometer to classmate-laptop Miguel Gómez
2012-06-29 12:46 ` [PATCH] classmate-laptop: Add support for Classmate V3 accelerometer Miguel Gómez
2012-06-29 13:39 ` [PATCH 0/1 v2] Add support for Classmate V4 accelerometer to classmate-laptop Miguel Gómez
2012-06-29 13:39 ` [PATCH 1/1 v2] classmate-laptop: Add support for Classmate V4 accelerometer Miguel Gómez
2012-07-17 22:47 ` Thadeu Lima de Souza Cascardo
2012-07-18 13:53 ` Miguel Gómez [this message]
2012-07-23 13:28 ` Matthew Garrett
2012-07-23 13:33 ` Miguel Gómez
2012-07-23 13:36 ` Matthew Garrett
2012-07-23 13:44 ` Miguel Gómez
2012-07-24 3:09 ` Thadeu Lima de Souza Cascardo
2012-07-24 13:05 ` [PATCH] classmate-laptop: Fix extra keys hardware id Miguel Gómez
2012-07-24 13:17 ` Miguel Gómez
2012-07-24 13:21 ` Matthew Garrett
2012-07-17 14:34 ` [PATCH 0/1 v2] Add support for Classmate V4 accelerometer to classmate-laptop Miguel Gómez
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=5006BFEC.1010407@igalia.com \
--to=magomez@igalia.com \
--cc=cascardo@holoscopio.com \
--cc=don@syst.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).