From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
Jeremy Cline <jeremy@jcline.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Lars Kellogg-Stedman <lars@oddbit.com>,
Steven Presser <steve@pressers.name>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
Wolfram Sang <wsa@the-dreams.de>
Subject: Re: [PATCH 2/2] iio: accel: bmc150: Check for a second ACPI device for BOSC0200
Date: Mon, 4 Dec 2017 12:41:40 +0200 [thread overview]
Message-ID: <20171204104140.GZ22431@lahna.fi.intel.com> (raw)
In-Reply-To: <045185e0-927e-f004-2ec6-44205e5f6c13@redhat.com>
On Mon, Dec 04, 2017 at 11:29:31AM +0100, Hans de Goede wrote:
> i2c_new_secondary_device() is for a different purpose, this is for when
> a single i2c device listens on multiple addresses and the driver wants
> separate i2c_client-s to use to talk to each address.
>
> In this case there are 2 separate devices, not a single device listening
> on multiple addresses. Something like i2c_new_secondary_device() ACPI
> support might be useful for i2c devices where a single device / "IC" listens
> on multiple addresses and all these addresses are listed in the ACPI resource
> table, but not for this specific case.
Right, thanks Hans for correcting me.
next prev parent reply other threads:[~2017-12-04 10:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171129223016.17848-1-jeremy@jcline.org>
2017-11-29 22:31 ` [PATCH 2/2] iio: accel: bmc150: Check for a second ACPI device for BOSC0200 Jeremy Cline
2017-12-02 12:19 ` Jonathan Cameron
2017-12-04 9:58 ` Mika Westerberg
2017-12-04 10:29 ` Hans de Goede
2017-12-04 10:41 ` Mika Westerberg [this message]
2017-12-05 11:27 ` Jonathan Cameron
2017-12-05 11:38 ` Mika Westerberg
2017-12-05 11:54 ` Jonathan Cameron
2017-12-04 18:58 ` Jeremy Cline
2017-11-29 22:31 ` [PATCH 1/2] iio: accel: bmc150: Move struct definitions into the header Jeremy Cline
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=20171204104140.GZ22431@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=jeremy@jcline.org \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=lars@oddbit.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=steve@pressers.name \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.