From: Bastien Nocera <hadess@hadess.net>
To: Jonathan Cameron <jic23@kernel.org>,
Mike Mestnik <cheako@mikemestnik.net>,
Daniel Baluta <daniel.baluta@gmail.com>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Subject: Re: [PATCH] Asus T300CHI.
Date: Mon, 21 Sep 2015 00:42:40 +0200 [thread overview]
Message-ID: <1442788960.1030.11.camel@hadess.net> (raw)
In-Reply-To: <55FF0433.6050900@kernel.org>
On Sun, 2015-09-20 at 20:08 +0100, Jonathan Cameron wrote:
> On 19/09/15 20:03, Mike Mestnik wrote:
> > On Sat, Sep 19, 2015 at 1:48 PM, Daniel Baluta <
> > daniel.baluta@gmail.com> wrote:
> > > On Fri, Sep 18, 2015 at 12:07 AM, Mike Mestnik <
> > > cheako@mikemestnik.net> wrote:
> > > > Hello,
> > > > I'm looking to know the result of adding ACPI support for a
> > > > new
> > > > tablet, the existing support shouldn't work because of a
> > > > misplaced
> > > > __init that causes the function to be removed prior to being
> > > > called.
> > >
> > > Are you sure about this? It seems that the existing support
> > > doesn't work
> > > because you have different product ids.
> > >
> > The driver worked much better prior to me adding the product ids.
> > The
> > sensors were exposed to sysfs and all the data they collected
> > seemed
> > correct to me. The big issue is that there is no software, even
> > iio-sensor-proxy didn't know how to access the data.
> Cc'd Bastien Nocera.
iio-sensor-proxy not finding the sensor, and with it working otherwise,
would be an iio-sensor-proxy bug. I have one of those already for the
accelerometer in the WinBook TW100 that I haven't had time to root down
though. See:
https://github.com/hadess/iio-sensor-proxy/issues/39
The main problem being that sensor types are already hard to detect,
and the iio subsystem doesn't make it any easier to check whether
there's buffered output available, or the application needs to poll.
If anyone wants to fix that in the kernel, that would certainly make my
life easier.
Cheers
next prev parent reply other threads:[~2015-09-20 22:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 21:07 [PATCH] Asus T300CHI Mike Mestnik
2015-09-19 18:31 ` Mike Mestnik
2015-09-19 18:48 ` Daniel Baluta
2015-09-19 19:03 ` Mike Mestnik
2015-09-20 19:08 ` Jonathan Cameron
2015-09-20 22:42 ` Bastien Nocera [this message]
2015-09-20 22:55 ` Mike Mestnik
2015-09-21 14:26 ` Mike Mestnik
2015-09-21 19:46 ` Jonathan Cameron
2015-09-24 15:57 ` Mike Mestnik
2015-09-25 14:19 ` Srinivas Pandruvada
2015-09-25 16:40 ` Mike Mestnik
2015-09-21 19:47 ` Jonathan Cameron
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=1442788960.1030.11.camel@hadess.net \
--to=hadess@hadess.net \
--cc=cheako@mikemestnik.net \
--cc=daniel.baluta@gmail.com \
--cc=jic23@kernel.org \
--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).