[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <532ADFD8.80301@gmail.com>
Date: Thu, 20 Mar 2014 13:32:24 +0100
From: Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>
To: Jean-Francois Moine <moinejf@...e.fr>,
Russell King - ARM Linux <linux@....linux.org.uk>,
devicetree@...r.kernel.org
CC: dri-devel@...ts.freedesktop.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: tda998x: Fix lack of required reg in DT documentation
On 03/20/2014 09:58 AM, Jean-Francois Moine wrote:
> The I2C address (reg) is required for the TDA998x driver to be loaded
> and initialized.
>
> Signed-off-by: Jean-Francois Moine <moinejf@...e.fr>
> ---
> This patch applies to linux-next.
> ---
> Documentation/devicetree/bindings/drm/i2c/tda998x.txt | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/drm/i2c/tda998x.txt b/Documentation/devicetree/bindings/drm/i2c/tda998x.txt
> index d7df01c..fc7effa 100644
> --- a/Documentation/devicetree/bindings/drm/i2c/tda998x.txt
> +++ b/Documentation/devicetree/bindings/drm/i2c/tda998x.txt
> @@ -3,6 +3,8 @@ Device-Tree bindings for the NXP TDA998x HDMI transmitter
> Required properties;
> - compatible: must be "nxp,tda998x"
>
> + - 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
> Optional properties:
> - interrupts: interrupt number and trigger type
> default: polling
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists