From: Jean-Francois Moine <moinejf@free.fr>
To: Jean-Francois Moine <moinejf@free.fr>
Cc: devicetree@vger.kernel.org,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Subject: Re: [PATCH] ASoC: tda998x: Fix lack of required reg in DT documentation
Date: Thu, 20 Mar 2014 14:25:08 +0100 [thread overview]
Message-ID: <20140320142508.557fb860@armhf> (raw)
In-Reply-To: <20140320140156.5d768b1f@armhf>
On Thu, 20 Mar 2014 14:01:56 +0100
Jean-Francois Moine <moinejf@free.fr> wrote:
> 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)
I had a look again on the tda998x driver from NXP and the linux tda998x
driver:
- the NXP driver handles the TDAs 19989, 19988, 9984, 9983 and 9981.
It accesses the tda registers only at I2C address 0x70 and 0x34
(hard-coded values in the driver).
- the linux tda998x driver handles only the TDAs 19988 and 19989.
As we have no documentation about the chips TDA 19988 and 19989,
may the HDMI I2C addresses of these chips be different from 0x70?
--
Ken ar c'hentañ | ** Breizh ha Linux atav! **
Jef | http://moinejf.free.fr/
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-03-20 13:25 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 [this message]
2014-03-20 13:26 ` Russell King - ARM Linux
2014-03-20 13:32 ` Sebastian Hesselbarth
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=20140320142508.557fb860@armhf \
--to=moinejf@free.fr \
--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=sebastian.hesselbarth@gmail.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;
as well as URLs for NNTP newsgroup(s).