From: Lars-Peter Clausen <lars@metafoo.de>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Jean-Michel Hautbois <jean-michel.hautbois@vodalys.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
mark.rutland@arm.com
Subject: Re: [PATCH] i2c: Add generic support passing secondary devices addresses
Date: Sun, 21 Sep 2014 21:23:25 +0200 [thread overview]
Message-ID: <541F25AD.7030204@metafoo.de> (raw)
In-Reply-To: <20140921174902.GA1479@katana>
On 09/21/2014 07:49 PM, Wolfram Sang wrote:
>
>>> This raises the first question for me: Are the additional addresses
>>> configurable? Sadly, I can't find good documentation for the adv7604.
>>> Otherwise, if I know I have a adv7604 and know its addresses, this
>>> information should go into the driver and not the DT.
>>>
>>
>> They are. The current driver hard codes the other addresses, but that's not
>> working when you have multiple adv7604s on the same I2C bus.
>
> How is this configured? I can't imagine every address has its own
> setting, but rather some 1-3 pins which select a certain block of
> addresses?
>
Every secondary address has its own register and can be set to any valid I2C
address.
- Lars
next prev parent reply other threads:[~2014-09-21 19:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 14:02 [PATCH] i2c: Add generic support passing secondary devices addresses Jean-Michel Hautbois
2014-09-20 16:49 ` Wolfram Sang
2014-09-20 19:50 ` Lars-Peter Clausen
2014-09-21 17:49 ` Wolfram Sang
2014-09-21 19:23 ` Lars-Peter Clausen [this message]
2014-09-22 10:45 ` Mika Westerberg
2014-09-22 13:27 ` Lars-Peter Clausen
2014-09-22 13:45 ` Mika Westerberg
2014-09-22 14:11 ` Lars-Peter Clausen
2014-09-22 14:41 ` Mika Westerberg
2014-10-03 10:46 ` Wolfram Sang
2014-10-15 18:54 ` Srinivas Pandruvada
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=541F25AD.7030204@metafoo.de \
--to=lars@metafoo.de \
--cc=jean-michel.hautbois@vodalys.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.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).