public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
	linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c / ACPI: Pick the first address if device has multiple
Date: Tue, 13 Jan 2015 17:48:29 +0100	[thread overview]
Message-ID: <20150113164829.GO7660@katana> (raw)
In-Reply-To: <1421167477.4459.229.camel@spandruv-desktop.jf.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1394 bytes --]

On Tue, Jan 13, 2015 at 08:44:37AM -0800, Srinivas Pandruvada wrote:
> On Tue, 2015-01-13 at 16:50 +0100, Wolfram Sang wrote: 
> > On Mon, Dec 29, 2014 at 03:48:48PM +0200, Mika Westerberg wrote:
> > > ACPI specification allows I2C devices with multiple addresses. The current
> > > implementation goes over all addresses and assigns the last one to the
> > > device. This is typically not the primary address of the device.
> > > 
> > > Instead of doing that we assign the first address to the device and then
> > > let the driver handle rest of the addresses as it wishes.
> > > 
> > > Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
> > > Cc: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
> > 
> > Yes, seems better than what we do know. But maybe taking the lowest
> > address is a bit better heuristic than taking the first address?
> > Not sure, though...
> The problem in taking lowest is that in many cases in current devices,
> the lowest address may end being 0x0C, which is reserved address for
> SMBUS (ARA). This will require different handling. Unfortunately ACPI
> doesn't have a way to distinguish whether SMBUS support is desired or
> not. 
> The other option is to skip all reserved addresses for SMBUS also and
> then create on the lowest.

Well, this makes me think that Mika's approach is probably the sanest
one...


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-01-13 16:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-29 13:48 [PATCH] i2c / ACPI: Pick the first address if device has multiple Mika Westerberg
2015-01-13 15:50 ` Wolfram Sang
2015-01-13 16:44   ` Srinivas Pandruvada
2015-01-13 16:48     ` Wolfram Sang [this message]
2015-01-13 17:00       ` Mika Westerberg
2015-01-14 10:55 ` Wolfram Sang

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=20150113164829.GO7660@katana \
    --to=wsa@the-dreams.de \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --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