From: Jonathan Cameron <jic23@kernel.org>
To: Bastien Nocera <hadess@hadess.net>,
Daniel Baluta <daniel.baluta@intel.com>
Cc: linux-iio@vger.kernel.org, srinivas.pandruvada@linux.intel.com
Subject: Re: [PATCH] iio:kxcjk-1013: Add support for SMO8500 device
Date: Sun, 14 Sep 2014 15:11:58 +0100 [thread overview]
Message-ID: <5415A22E.2050802@kernel.org> (raw)
In-Reply-To: <1410524654.32328.34.camel@hadess.net>
On 12/09/14 13:24, Bastien Nocera wrote:
> On Fri, 2014-09-12 at 15:24 +0300, Daniel Baluta wrote:
>> On 09/11/2014 09:18 PM, Bastien Nocera wrote:
>>> On Tue, 2014-09-09 at 21:53 +0300, Daniel Baluta wrote:
>>>> Hi Bastien,
>>>>
>>>> On Tue, Sep 9, 2014 at 8:19 PM, Bastien Nocera <hadess@hadess.net> wrote:
>>>>> The Onda v975w tablet contains an accelerometer that's advertised over
>>>>> ACPI as SMO8500. This device is however a KXCJ9 accelerometer as
>>>>> can be seen in the Windows driver's INF file.
>>>>> ---
>>>>>
>>>>> I tested the patch, and it works correctly in my testing. However,
>>>>> there's no GPIO pin for the "data ready" interrupt, and this throws an
>>>>> error that looks fatal in the logs (could this be downgraded?), and
>>>>> the name of the device doesn't match the hid-sensor-hub ones, making it
>>>>> hard for user-space to discover them.
>>>>> (https://github.com/hadess/iio-sensor-proxy is my attempt at something
>>>>> that integrates with user-space and the IIO sensors)
>>>>>
>> How did you test it?
>
> Cat on the /sys files for each of the axis. I can see the values of
> x/y/z changing depending on the position of the device.
>
>> There is no GpioInt associated with your device in
>> the the .dsl file.
>
> I know, that's because the GPIO (according to the driver) is only used
> to know when there's more data to be read. We just have to poll
> instead...
>
>> What kind of error do you see in the logs?
>
> The "acpi gpio get index failed" error when it fails to find a GPIO pin
> for the "data ready" interrupt. Except that it works just fine without
> such an interrupt.
>
>>>> How does your ACPI .dsl file looks like?
>>>>
>>>>> It will also conflict with Daniel's patch here:
>>>>> http://www.spinics.net/lists/linux-iio/msg14438.html
>>>> It shouldn't. The patch is already in togreg branch of Jonathan's tree
>>>> [1]. Anyhow,
>>>> it will conflict with this one [2].
>>> Do you want me to rebase the patch on a particular tree? Do you need any
>>> particular changes done in my commit message or patch to get this
>>> merged?
>>>
>> I would suggest you wait until Jonathan merges this patch [1] in togreg
>> branch [2].
>> Then rebase your patch on togreg branch and get feedback from Jonathan
>> and Srinivas.
I've applied the patch [1] to my local copy and pushed out as testing.
Once the autobuilders come back to me in an hour or so, I'll push it out as
the togreg branch. I'm planning a pull request to Greg tonight at which point
it will head for linux-next.
>
> OK, I'll have to monitor those.
>
> Cheers
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2014-09-14 14:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 17:19 [PATCH] iio:kxcjk-1013: Add support for SMO8500 device Bastien Nocera
2014-09-09 18:53 ` Daniel Baluta
2014-09-09 18:58 ` Bastien Nocera
2014-09-11 18:18 ` Bastien Nocera
2014-09-12 12:24 ` Daniel Baluta
2014-09-12 12:24 ` Bastien Nocera
2014-09-14 14:11 ` Jonathan Cameron [this message]
2014-09-25 8:49 ` Bastien Nocera
2014-09-25 12:47 ` Jonathan Cameron
2014-09-14 14:05 ` Jonathan Cameron
-- strict thread matches above, loose matches on Subject: below --
2014-11-03 23:07 Bastien Nocera
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=5415A22E.2050802@kernel.org \
--to=jic23@kernel.org \
--cc=daniel.baluta@intel.com \
--cc=hadess@hadess.net \
--cc=linux-iio@vger.kernel.org \
--cc=srinivas.pandruvada@linux.intel.com \
/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).