From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [RFC V2 3/4] ARM: shmobile: r8a7790: lager: add i2c-demuxer to dts
Date: Tue, 17 Mar 2015 09:13:02 +0000 [thread overview]
Message-ID: <1452186.xZUSqiyjm5@avalon> (raw)
In-Reply-To: <1426576524-22315-4-git-send-email-wsa@the-dreams.de>
Hi Wolfram,
Thank you for the patch.
On Tuesday 17 March 2015 08:15:23 Wolfram Sang wrote:
> From: Wolfram Sang <wsa+renesas@sang-engineering.com>
>
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> ---
>
> Changes since RFC V1: rebased, added the sound-codec entry, fixed a typo
>
> arch/arm/boot/dts/r8a7790-lager.dts | 66 ++++++++++++++++++++++++----------
> 1 file changed, 46 insertions(+), 20 deletions(-)
>
> diff --git a/arch/arm/boot/dts/r8a7790-lager.dts
> b/arch/arm/boot/dts/r8a7790-lager.dts index 0c3b6783b72add..bf0065d676428d
> 100644
> --- a/arch/arm/boot/dts/r8a7790-lager.dts
> +++ b/arch/arm/boot/dts/r8a7790-lager.dts
> @@ -222,6 +222,40 @@
> };
> };
> };
> +
> + i2c-demux {
> +
> + compatible = "i2c-demux-pinctrl";
> + i2c-parent = <&iic2>, <&i2c2>;
Purely from a DT point of view, wouldn't it make sense to call the node i2c-
bus and rename the i2c-parent property to i2c-masters ?
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + i2c@0 {
> + reg = <0>;
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> +
> + ak4643: sound-codec@12 {
> + compatible = "asahi-kasei,ak4643";
> + #sound-dai-cells = <0>;
> + reg = <0x12>;
> + };
> +
> + composite-in@20 {
> + compatible = "adi,adv7180";
> + reg = <0x20>;
> + remote = <&vin1>;
> +
> + port {
> + adv7180: endpoint {
> + bus-width = <8>;
> + remote-endpoint = <&vin1ep0>;
> + };
> + };
> + };
> + };
> + };
> };
>
> &du {
> @@ -303,6 +337,11 @@
> renesas,function = "iic1";
> };
>
> + i2c2_pins: i2c2 {
> + renesas,groups = "i2c2";
> + renesas,function = "i2c2";
> + };
> +
> iic2_pins: iic2 {
> renesas,groups = "iic2";
> renesas,function = "iic2";
> @@ -481,31 +520,18 @@
> pinctrl-names = "default";
> };
>
> +&i2c2 {
> + status = "ok";
> + pinctrl-0 = <&i2c2_pins>;
> + pinctrl-names = "active";
> +};
> +
> &iic2 {
> status = "okay";
> pinctrl-0 = <&iic2_pins>;
> - pinctrl-names = "default";
> + pinctrl-names = "active";
>
> clock-frequency = <100000>;
> -
> - ak4643: sound-codec@12 {
> - compatible = "asahi-kasei,ak4643";
> - #sound-dai-cells = <0>;
> - reg = <0x12>;
> - };
> -
> - composite-in@20 {
> - compatible = "adi,adv7180";
> - reg = <0x20>;
> - remote = <&vin1>;
> -
> - port {
> - adv7180: endpoint {
> - bus-width = <8>;
> - remote-endpoint = <&vin1ep0>;
> - };
> - };
> - };
> };
>
> &iic3 {
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2015-03-17 9:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 7:15 [RFC V2 3/4] ARM: shmobile: r8a7790: lager: add i2c-demuxer to dts Wolfram Sang
2015-03-17 9:13 ` Laurent Pinchart [this message]
2015-03-17 10:45 ` Wolfram Sang
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=1452186.xZUSqiyjm5@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-sh@vger.kernel.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 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).