linux-renesas-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Biju Das <biju.das.jz@bp.renesas.com>
To: Rob Herring <robh+dt@kernel.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
	Magnus Damm <magnus.damm@gmail.com>,
	"linux-renesas-soc@vger.kernel.org" 
	<linux-renesas-soc@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Chris Paterson <Chris.Paterson2@renesas.com>,
	Biju Das <biju.das@bp.renesas.com>,
	Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: RE: [PATCH v4 6/6] arm64: dts: renesas: beacon-renesom-baseboard: Move connector node out of hd3ss3220 device
Date: Tue, 27 Oct 2020 08:54:20 +0000	[thread overview]
Message-ID: <TYBPR01MB5309E301D3EA84E56064B88286160@TYBPR01MB5309.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <20200920134905.4370-7-biju.das.jz@bp.renesas.com>

Hi Geert,

The dependencies patches hit on 5.10-rc1 [1] [2][3].  This patch cleanly applies on renesas-devel. 

[1]  https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.10-rc1&id=588614be61b7cb46f697c3e141b2aef7f6b49347
[2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.10-rc1&id=a6806e32e7a41c20c6b288009cb6f30929668327
[3] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.10-rc1&id=1c6e8ee63adbaf02a1e5177610fe9b77bec93d8a


Regards,
Biju


> Subject: [PATCH v4 6/6] arm64: dts: renesas: beacon-renesom-baseboard:
> Move connector node out of hd3ss3220 device
> 
> Move connector node out of hd3ss3220 device in order to comply with usb
> connector bindings.
> 
> Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
> Reviewed-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
> ---
> v3->v4: No change
> v2->v3: No change
> v1->v2: No change
> ---
>  .../dts/renesas/beacon-renesom-baseboard.dtsi | 67 ++++++++++++++-----
>  1 file changed, 50 insertions(+), 17 deletions(-)
> 
> diff --git a/arch/arm64/boot/dts/renesas/beacon-renesom-baseboard.dtsi
> b/arch/arm64/boot/dts/renesas/beacon-renesom-baseboard.dtsi
> index 66c9153b3101..e66b5b36e489 100644
> --- a/arch/arm64/boot/dts/renesas/beacon-renesom-baseboard.dtsi
> +++ b/arch/arm64/boot/dts/renesas/beacon-renesom-baseboard.dtsi
> @@ -223,6 +223,29 @@
>  		#clock-cells = <0>;
>  		clock-frequency = <25000000>;
>  	};
> +
> +	connector {
> +		compatible = "usb-c-connector";
> +		label = "USB-C";
> +		data-role = "dual";
> +
> +		ports {
> +			#address-cells = <1>;
> +			#size-cells = <0>;
> +			port@0 {
> +				reg = <0>;
> +				hs_ep: endpoint {
> +					remote-endpoint = <&usb3_hs_ep>;
> +				};
> +			};
> +			port@1 {
> +				reg = <1>;
> +				ss_ep: endpoint {
> +					remote-endpoint =
> <&hd3ss3220_in_ep>;
> +				};
> +			};
> +		};
> +	};
>  };
> 
>  &audio_clk_a {
> @@ -427,20 +450,19 @@
>  		interrupt-parent = <&gpio6>;
>  		interrupts = <4 IRQ_TYPE_LEVEL_LOW>;
> 
> -		connector {
> -			compatible = "usb-c-connector";
> -			label = "USB-C";
> -			data-role = "dual";
> -
> -			ports {
> -				#address-cells = <1>;
> -				#size-cells = <0>;
> -
> -				port@1 {
> -					reg = <1>;
> -					hd3ss3220_ep: endpoint {
> -						remote-endpoint =
> <&usb3_role_switch>;
> -					};
> +		ports {
> +			#address-cells = <1>;
> +			#size-cells = <0>;
> +			port@0 {
> +				reg = <0>;
> +				hd3ss3220_in_ep: endpoint {
> +					remote-endpoint = <&ss_ep>;
> +				};
> +			};
> +			port@1 {
> +				reg = <1>;
> +				hd3ss3220_out_ep: endpoint {
> +					remote-endpoint =
> <&usb3_role_switch>;
>  				};
>  			};
>  		};
> @@ -714,9 +736,20 @@
>  	status = "okay";
>  	usb-role-switch;
> 
> -	port {
> -		usb3_role_switch: endpoint {
> -			remote-endpoint = <&hd3ss3220_ep>;
> +	ports {
> +		#address-cells = <1>;
> +		#size-cells = <0>;
> +		port@0 {
> +			reg = <0>;
> +			usb3_hs_ep: endpoint {
> +				remote-endpoint = <&hs_ep>;
> +			};
> +		};
> +		port@1 {
> +			reg = <1>;
> +			usb3_role_switch: endpoint {
> +				remote-endpoint = <&hd3ss3220_out_ep>;
> +			};
>  		};
>  	};
>  };
> --
> 2.17.1


  reply	other threads:[~2020-10-27  8:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-20 13:48 [PATCH v4 0/6] Remodel HD3SS3220 device nodes Biju Das
2020-09-20 13:49 ` [PATCH v4 1/6] dt-bindings: update usb-c-connector example Biju Das
2020-10-13 12:53   ` Rob Herring
2020-09-20 13:49 ` [PATCH v4 2/6] dt-bindings: usb: convert ti,hd3ss3220 bindings to json-schema Biju Das
2020-09-20 13:49 ` [PATCH v4 3/6] dt-bindings: usb: renesas,usb3-peri: Document HS and SS data bus Biju Das
2020-09-20 13:49 ` [PATCH v4 4/6] usb: typec: hd3ss3220: Use OF graph API to get the connector fwnode Biju Das
2020-09-20 13:49 ` [PATCH v4 5/6] arm64: dts: renesas: cat874: Move connector node out of hd3ss3220 device Biju Das
2020-10-27  8:55   ` Biju Das
2020-10-29 13:38   ` Geert Uytterhoeven
2020-09-20 13:49 ` [PATCH v4 6/6] arm64: dts: renesas: beacon-renesom-baseboard: " Biju Das
2020-10-27  8:54   ` Biju Das [this message]
2020-10-29 13:40   ` Geert Uytterhoeven

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=TYBPR01MB5309E301D3EA84E56064B88286160@TYBPR01MB5309.jpnprd01.prod.outlook.com \
    --to=biju.das.jz@bp.renesas.com \
    --cc=Chris.Paterson2@renesas.com \
    --cc=biju.das@bp.renesas.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
    --cc=robh+dt@kernel.org \
    --cc=yoshihiro.shimoda.uh@renesas.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).