From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: Jean-Francois Moine <moinejf@free.fr>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: tda998x: Fix lack of required reg in DT documentation
Date: Thu, 20 Mar 2014 14:32:18 +0100 [thread overview]
Message-ID: <532AEDE2.3080306@gmail.com> (raw)
In-Reply-To: <20140320140156.5d768b1f@armhf>
On 03/20/2014 02:01 PM, Jean-Francois Moine wrote:
> On Thu, 20 Mar 2014 13:32:24 +0100
> Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> wrote:
>
>>> + - reg: I2C address - must be <0x70>
>>
>> TDA9983b datasheet says:
>>
>> "Bits A0 and A1 of the I2C-bus device address are externally selected
>> by pins A0 and A1."
>>
>> Therefore, 0x70, 0x71, 0x72, and 0x73 are valid i2c addresses.
>
> Sebastian,
>
> That's interesting!
>
> For the Cubox and the AMX33XX boards, the I2C address of the HDMI
> registers is 0x70, and the I2C address of the CEC registers is 0x34.
>
> For other boards using the TDA998x family, if the I2C address is
> different from 0x70, have you an idea about what can be the CEC I2C
> address? (this value is actually hard-coded in the TDA998x driver)
>
Ok, I had another round of google'ing and found this:
http://hipstercircuits.com/wp-content/uploads/2013/05/TDA19988.pdf
There, the datasheet specifically for TDA19988 only states 0x70 and
0x34 as the two i2c addresses. Therefore, TDA19988 has fixed i2c
addresses while TDA9983b has configurable (main) i2c address.
Not as easy as we thought ;)
I suggest reword the reg property to:
"- reg: shall be set to the I2C address"
and optionally list all known addresses for each TDA[1]998x in the
binding.
Sebastian
next prev parent reply other threads:[~2014-03-20 13:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-20 8:58 [PATCH] ASoC: tda998x: Fix lack of required reg in DT documentation Jean-Francois Moine
[not found] ` <20140320092639.48F68A6279-0zphjBnwxSw1Wri2s2gf/1AUjnlXr6A1@public.gmane.org>
2014-03-20 12:32 ` Sebastian Hesselbarth
2014-03-20 12:36 ` Russell King - ARM Linux
2014-03-20 13:01 ` Jean-Francois Moine
2014-03-20 13:25 ` Jean-Francois Moine
2014-03-20 13:26 ` Russell King - ARM Linux
2014-03-20 13:32 ` Sebastian Hesselbarth [this message]
2014-03-20 13:52 ` Jean-Francois Moine
2014-03-20 14:19 ` Sebastian Hesselbarth
2014-03-20 14:31 ` Russell King - ARM Linux
2014-03-20 14:59 ` Jean-Francois Moine
2014-03-20 15:15 ` Robert Nelson
2014-03-20 15:19 ` Russell King - ARM Linux
2014-03-20 15:54 ` Jean-Francois Moine
2014-03-20 16:22 ` Russell King - ARM Linux
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=532AEDE2.3080306@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=moinejf@free.fr \
/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).