linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phil Reid <preid@electromag.com.au>
To: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	Marc CAPDEVILLE <m.capdeville@no-log.org>
Cc: Kevin Tsai <ktsai@capellamicro.com>,
	Jonathan Cameron <jic23@kernel.org>,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
	Wolfram Sang <wsa@the-dreams.de>,
	Hartmut Knaack <knaack.h@gmx.de>,
	Lars-Peter Clausen <lars@metafoo.de>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] iio : Add cm3218 smbus ara and acpi support
Date: Thu, 2 Nov 2017 23:05:02 +0800	[thread overview]
Message-ID: <76773afb-8428-645f-2cf7-98bd7dd3a21c@electromag.com.au> (raw)
In-Reply-To: <1509634178.782.5.camel@linux.intel.com>

On 2/11/2017 22:49, Srinivas Pandruvada wrote:
> On Thu, 2017-11-02 at 14:35 +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.
> There was another RFC from Alan cox
> https://patchwork.ozlabs.org/patch/381773/
> 

Wolfram just merged this from me:
[PATCH v11 00/10] Add sbs-manager with smbalert support
https://www.spinics.net/lists/devicetree/msg191947.html

Cleans up the smbus_alert driver a bit.
note: alert_edge_triggered was removed.

And for OF systems core creates the ara device.


-- 
Regards
Phil Reid

  reply	other threads:[~2017-11-02 15:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-27 16:27 [PATCH v4] iio : Add cm3218 smbus ara and acpi support 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 [this message]
2017-11-02 15:04   ` Wolfram Sang
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=76773afb-8428-645f-2cf7-98bd7dd3a21c@electromag.com.au \
    --to=preid@electromag.com.au \
    --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 \
    --cc=wsa@the-dreams.de \
    /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).