From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Wolfram Sang <wsa@the-dreams.de>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Marc CAPDEVILLE <m.capdeville@no-log.org>,
Kevin Tsai <ktsai@capellamicro.com>,
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>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Jarkko Nikula <jarkko.nikula@linux.intel.com>
Subject: Re: [PATCH v4] iio : Add cm3218 smbus ara and acpi support
Date: Mon, 27 Nov 2017 13:35:44 +0200 [thread overview]
Message-ID: <20171127113544.GI22431@lahna.fi.intel.com> (raw)
In-Reply-To: <20171125140034.10d6e581@archlinux>
On Sat, Nov 25, 2017 at 02:00:34PM +0000, Jonathan Cameron wrote:
> > There does not seem to be any way in ACPI to tell which "connection" is
> > used to describe ARA so that part currently is something each driver
> > needs to handle as they know the device the best. I don't think we have
> > any means to handle it in generic way in I2C core except to provide some
> > helpers that work on top of i2c_setup_smbus_alert() but understand ACPI
> > resources. Say provide function like this:
> >
> > int acpi_i2c_setup_smbus_alert(struct i2c_adapter *adapter, int index);
> >
> > Which then extracts automatically I2cSerialBus connection from "index"
> > and calls i2c_setup_smbus_alert() accordingly.
> >
> > In the long run we could introduce _DSD property that can be used to
> > name the connection in the same way DT does;
> >
> > Name (_CRS, ResourceTemplate () {
> > I2cSerialBus () { ... } // ARA
> > I2cSerialBus () { ... } // normal device address
> > })
> >
> > Name (_DSD, Package () {
> > ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"),
> > Package () {
> > Package () {"smbus_alert", 0} // Where 0 means the first I2cSerialBus
> > ...
> > }
> > })
> >
> > But it does not help the existing systems.
>
> I'm curious - how would we go about promoting this piece of common sense?
I guess a proper patch series including relevant mailing lists (like
linux-acpi and linux-i2c) would be a good starting point :)
prev parent reply other threads:[~2017-11-27 11:42 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
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 [this message]
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=20171127113544.GI22431@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=benjamin.tissoires@redhat.com \
--cc=jarkko.nikula@linux.intel.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