From: Patrice CHOTARD <patrice.chotard@foss.st.com>
To: Alain Volmat <avolmat@me.com>, <patrice.chotard@st.com>,
<robh+dt@kernel.org>, <mark.rutland@arm.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 06/12] ARM: dts: sti: update stih418-b2199 following stih407-family DT update
Date: Thu, 10 Feb 2022 09:37:05 +0100 [thread overview]
Message-ID: <746858c4-09bb-7a95-a9c4-a5d2267ef8b9@foss.st.com> (raw)
In-Reply-To: <20211202075105.195664-7-avolmat@me.com>
Hi Alain
On 12/2/21 08:50, Alain Volmat wrote:
> Put of the miphy28lp_phy node out of the soc section following similar
> update within stih407-family.dtsi file update.
>
> Signed-off-by: Alain Volmat <avolmat@me.com>
> ---
> arch/arm/boot/dts/stih418-b2199.dts | 22 +++++++++++-----------
> 1 file changed, 11 insertions(+), 11 deletions(-)
>
> diff --git a/arch/arm/boot/dts/stih418-b2199.dts b/arch/arm/boot/dts/stih418-b2199.dts
> index b66e2b29edea..d21bcc7c1271 100644
> --- a/arch/arm/boot/dts/stih418-b2199.dts
> +++ b/arch/arm/boot/dts/stih418-b2199.dts
> @@ -37,6 +37,17 @@ green {
> };
> };
>
> + miphy28lp_phy: miphy28lp {
> +
> + phy_port0: port@9b22000 {
> + st,osc-rdy;
> + };
> +
> + phy_port1: port@9b2a000 {
> + st,osc-force-ext;
> + };
> + };
> +
> soc {
> sbc_serial0: serial@9530000 {
> status = "okay";
> @@ -84,17 +95,6 @@ mmc0: sdhci@9060000 {
> non-removable;
> };
>
> - miphy28lp_phy: miphy28lp@0 {
> -
> - phy_port0: port@9b22000 {
> - st,osc-rdy;
> - };
> -
> - phy_port1: port@9b2a000 {
> - st,osc-force-ext;
> - };
> - };
> -
> st_dwc3: dwc3@8f94000 {
> status = "okay";
> };
Reviewed-by: Patrice Chotard <patrice.chotard@foss.st.com>
Thanks
Patrice
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-02-10 8:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 7:50 [PATCH 00/12] ARM: dts: sti: various DT fixes to avoid warnings Alain Volmat
2021-12-02 7:50 ` [PATCH 01/12] ARM: dts: sti: ensure unique unit-address in stih407-clock Alain Volmat
2022-02-10 8:35 ` Patrice CHOTARD
2021-12-02 7:50 ` [PATCH 02/12] ARM: dts: sti: ensure unique unit-address in stih410-clock Alain Volmat
2022-02-10 8:36 ` Patrice CHOTARD
2021-12-02 7:50 ` [PATCH 03/12] ARM: dts: sti: ensure unique unit-address in stih418-clock Alain Volmat
2022-02-10 8:36 ` Patrice CHOTARD
2021-12-02 7:50 ` [PATCH 04/12] ARM: dts: sti: move some nodes out of the soc section in stih407-family.dtsi Alain Volmat
2022-02-10 8:36 ` Patrice CHOTARD
2021-12-02 7:50 ` [PATCH 05/12] ARM: dts: sti: update stih410-b2260 following stih407-family DT update Alain Volmat
2022-02-10 8:36 ` Patrice CHOTARD
2021-12-02 7:50 ` [PATCH 06/12] ARM: dts: sti: update stih418-b2199 " Alain Volmat
2022-02-10 8:37 ` Patrice CHOTARD [this message]
2021-12-02 7:51 ` [PATCH 07/12] ARM: dts: sti: update stihxxx-b2120 " Alain Volmat
2022-02-10 8:37 ` Patrice CHOTARD
2021-12-02 7:51 ` [PATCH 08/12] ARM: dts: sti: remove delta node from stih410.dtsi Alain Volmat
2022-02-10 8:37 ` Patrice CHOTARD
2021-12-02 7:51 ` [PATCH 09/12] ARM: dts: sti: move usb picophy nodes out of soc in stih410.dtsi Alain Volmat
2022-02-10 8:37 ` Patrice CHOTARD
2021-12-02 7:51 ` [PATCH 10/12] ARM: dts: sti: move usb picophy nodes out of soc in stih418.dtsi Alain Volmat
2022-02-10 8:37 ` Patrice CHOTARD
2021-12-02 7:51 ` [PATCH 11/12] ARM: dts: sti: move usb picophy nodes in stih410-b2120.dts Alain Volmat
2022-02-10 8:57 ` Patrice CHOTARD
2021-12-02 7:51 ` [PATCH 12/12] ARM: dts: sti: move usb picophy nodes in stih410-b2260.dts Alain Volmat
2022-02-10 8:38 ` Patrice CHOTARD
2022-02-10 8:59 ` [PATCH 00/12] ARM: dts: sti: various DT fixes to avoid warnings Patrice CHOTARD
2022-02-11 18:13 ` Alain Volmat
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=746858c4-09bb-7a95-a9c4-a5d2267ef8b9@foss.st.com \
--to=patrice.chotard@foss.st.com \
--cc=avolmat@me.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=patrice.chotard@st.com \
--cc=robh+dt@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).