From: Wolfram Sang <wsa@the-dreams.de>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: Marc CAPDEVILLE <m.capdeville@no-log.org>,
Kevin Tsai <ktsai@capellamicro.com>,
Jonathan Cameron <jic23@kernel.org>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Subject: Re: [PATCH v4] iio : Add cm3218 smbus ara and acpi support
Date: Thu, 2 Nov 2017 16:04:07 +0100 [thread overview]
Message-ID: <20171102150407.bparxxskfo5pzvvs@ninjato> (raw)
In-Reply-To: <20171102143550.00005a66@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 1251 bytes --]
On Thu, Nov 02, 2017 at 02:35:50PM +0000, Jonathan Cameron wrote:
> On Fri, 27 Oct 2017 18:27:02 +0200
> Marc CAPDEVILLE <m.capdeville@no-log.org> wrote:
>
> > On asus T100, Capella cm3218 chip is implemented as ambiant light
> > sensor. This chip expose an smbus ARA protocol device on standard
> > address 0x0c. The chip is not functional before all alerts are
> > acknowledged.
> > On asus T100, this device is enumerated on ACPI bus and the
> > description give tow I2C connection. The first is the connection to
> > the ARA device and the second gives the real address of the device.
> >
> > So, on device probe,If the i2c address is the ARA address and the
> > device is enumerated via acpi, we lookup for the real address in
> > the ACPI resource list and change it in the client structure.
> > if an interrupt resource is given, and only for cm3218 chip,
> > we declare an smbus_alert device.
> >
> > Signed-off-by: Marc CAPDEVILLE <m.capdeville@no-log.org>
>
> Wolfram - this needs input from you on how to neatly handle
> an ACPI registered ARA.
ACPI is really not my field. Try asking the I2C ACPI maintainers or
Benjamin Tissoires <benjamin.tissoires@redhat.com> who did work on SMBus
interrupts recently.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-11-02 15:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-27 16:27 Marc CAPDEVILLE
2017-10-27 17:57 ` Peter Meerwald-Stadler
2017-11-02 14:35 ` Jonathan Cameron
2017-11-02 14:49 ` Srinivas Pandruvada
2017-11-02 15:05 ` Phil Reid
2017-11-02 15:04 ` Wolfram Sang [this message]
2017-11-19 16:35 ` Jonathan Cameron
2017-11-20 10:57 ` Mika Westerberg
2017-11-21 1:22 ` Phil Reid
2017-11-25 13:57 ` Jonathan Cameron
2017-11-27 2:55 ` Phil Reid
2017-11-25 14:00 ` Jonathan Cameron
2017-11-27 11:35 ` Mika Westerberg
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=20171102150407.bparxxskfo5pzvvs@ninjato \
--to=wsa@the-dreams.de \
--cc=Jonathan.Cameron@huawei.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=ktsai@capellamicro.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.capdeville@no-log.org \
--cc=pmeerw@pmeerw.net \
--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
all inboxes | Powered by JetHome®