From: Shrirang Bagul <shrirang.bagul@canonical.com>
To: Jonathan Cameron <jic23@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/3] iio: st_accel: Support sensor i2c probe using acpi
Date: Tue, 29 Nov 2016 12:27:31 +0800 [thread overview]
Message-ID: <1480393651.3233.7.camel@canonical.com> (raw)
In-Reply-To: <fbc223ef-46e8-9fb2-92e7-a0d8b4cd04e3@kernel.org>
On Sun, 2016-11-27 at 11:14 +0000, Jonathan Cameron wrote:
> On 24/11/16 14:26, Linus Walleij wrote:
> > On Thu, Nov 24, 2016 at 6:33 AM, Shrirang Bagul
> > <shrirang.bagul@canonical.com> wrote:
> >
> > > Add support to probe st_accel sensors on i2c bus using ACPI. Compatible
> > > strings are not avaialable on ACPI based systems.
> > >
> > > Signed-off-by: Shrirang Bagul <shrirang.bagul@canonical.com>
> >
> > (...)
> >
> > > +#ifdef CONFIG_ACPI
> > > +static const struct acpi_device_id st_accel_acpi_match[] = {
> > > + {"SMO8A90", LNG2DM},
> > > + { },
> > > +};
> >
> > Why is ACPI only supporting one out of 14 devices?
> >
> > Surely there are some out-of-tree ACPI platforms using one
> > or more of the others?
> >
> > Apart from that it looks nice.
>
> Applied to the togreg branch of iio.git and pushed out as testing
> for the autobuilders to play with it.
>
> Anyone know where the ACPI names come from? Is there some big
> list somewhere to prevent clashes?
>
> Jonathan
I'll take a look at the HW in our lab and send patches to identify more st_accel
sensors used mostly on Dell laptops.
Shrirang
> >
> > Yours,
> > Linus Walleij
> > --
> > 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:[~2016-11-29 4:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-24 5:33 [PATCH 0/3] iio: st_sensors: Support ACPI probe for st_sensors Shrirang Bagul
2016-11-24 5:33 ` [PATCH 1/3] iio: st_sensors: match sensors using ACPI handle Shrirang Bagul
2016-11-27 11:15 ` Jonathan Cameron
2016-11-24 5:33 ` [PATCH 2/3] iio: st_accel: Support sensor i2c probe using acpi Shrirang Bagul
2016-11-24 14:26 ` Linus Walleij
2016-11-27 11:14 ` Jonathan Cameron
2016-11-29 4:27 ` Shrirang Bagul [this message]
2016-11-24 5:33 ` [PATCH 3/3] iio: st_pressure: Support " Shrirang Bagul
2016-11-24 14:28 ` Linus Walleij
2016-11-27 11:12 ` Jonathan Cameron
2016-11-29 4:25 ` Shrirang Bagul
2016-11-30 13:04 ` Linus Walleij
2016-11-30 17:20 ` 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=1480393651.3233.7.camel@canonical.com \
--to=shrirang.bagul@canonical.com \
--cc=jic23@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@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).