All of lore.kernel.org
 help / color / mirror / Atom feed
From: sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ASoC: tda998x: Fix lack of required reg in DT documentation
Date: Thu, 20 Mar 2014 13:32:24 +0100	[thread overview]
Message-ID: <532ADFD8.80301@gmail.com> (raw)
In-Reply-To: <20140320092639.48F68A6279@smtp3-g21.free.fr>

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@free.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
>

WARNING: multiple messages have this Message-ID (diff)
From: Sebastian Hesselbarth <sebastian.hesselbarth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Jean-Francois Moine <moinejf-GANU6spQydw@public.gmane.org>,
	Russell King - ARM Linux
	<linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] ASoC: tda998x: Fix lack of required reg in DT documentation
Date: Thu, 20 Mar 2014 13:32:24 +0100	[thread overview]
Message-ID: <532ADFD8.80301@gmail.com> (raw)
In-Reply-To: <20140320092639.48F68A6279-0zphjBnwxSw1Wri2s2gf/1AUjnlXr6A1@public.gmane.org>

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-GANU6spQydw@public.gmane.org>
> ---
> 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 devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: Jean-Francois Moine <moinejf@free.fr>,
	Russell King - ARM Linux <linux@arm.linux.org.uk>,
	devicetree@vger.kernel.org
Cc: 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 13:32:24 +0100	[thread overview]
Message-ID: <532ADFD8.80301@gmail.com> (raw)
In-Reply-To: <20140320092639.48F68A6279@smtp3-g21.free.fr>

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@free.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
>


  reply	other threads:[~2014-03-20 12:32 UTC|newest]

Thread overview: 44+ 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
2014-03-20  8:58 ` Jean-Francois Moine
2014-03-20  8:58 ` Jean-Francois Moine
2014-03-20 12:32 ` Sebastian Hesselbarth [this message]
2014-03-20 12:32   ` Sebastian Hesselbarth
2014-03-20 12:32   ` Sebastian Hesselbarth
2014-03-20 12:36   ` Russell King - ARM Linux
2014-03-20 12:36     ` Russell King - ARM Linux
2014-03-20 12:36     ` Russell King - ARM Linux
2014-03-20 13:01   ` Jean-Francois Moine
2014-03-20 13:01     ` Jean-Francois Moine
2014-03-20 13:01     ` Jean-Francois Moine
2014-03-20 13:25     ` Jean-Francois Moine
2014-03-20 13:25       ` Jean-Francois Moine
2014-03-20 13:25       ` Jean-Francois Moine
2014-03-20 13:26     ` Russell King - ARM Linux
2014-03-20 13:26       ` Russell King - ARM Linux
2014-03-20 13:26       ` Russell King - ARM Linux
2014-03-20 13:32     ` Sebastian Hesselbarth
2014-03-20 13:32       ` Sebastian Hesselbarth
2014-03-20 13:52       ` Jean-Francois Moine
2014-03-20 13:52         ` Jean-Francois Moine
2014-03-20 13:52         ` Jean-Francois Moine
2014-03-20 14:19         ` Sebastian Hesselbarth
2014-03-20 14:19           ` Sebastian Hesselbarth
2014-03-20 14:19           ` Sebastian Hesselbarth
2014-03-20 14:31         ` Russell King - ARM Linux
2014-03-20 14:31           ` Russell King - ARM Linux
2014-03-20 14:31           ` Russell King - ARM Linux
2014-03-20 14:59           ` Jean-Francois Moine
2014-03-20 14:59             ` Jean-Francois Moine
2014-03-20 14:59             ` Jean-Francois Moine
2014-03-20 15:15             ` Robert Nelson
2014-03-20 15:15               ` Robert Nelson
2014-03-20 15:15               ` Robert Nelson
2014-03-20 15:19             ` Russell King - ARM Linux
2014-03-20 15:19               ` Russell King - ARM Linux
2014-03-20 15:19               ` Russell King - ARM Linux
2014-03-20 15:54               ` Jean-Francois Moine
2014-03-20 15:54                 ` Jean-Francois Moine
2014-03-20 15:54                 ` Jean-Francois Moine
2014-03-20 16:22                 ` Russell King - ARM Linux
2014-03-20 16:22                   ` Russell King - ARM Linux
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=532ADFD8.80301@gmail.com \
    --to=sebastian.hesselbarth@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.