From: Chintan Vankar <c-vankar@ti.com>
To: Nishanth Menon <nm@ti.com>
Cc: Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>, Tero Kristo <kristo@kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>, <s-vadapalli@ti.com>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm64: dts: ti: k3-am62-main: Add bootph-all property in phy_gmii_sel node
Date: Thu, 25 Apr 2024 18:00:07 +0530 [thread overview]
Message-ID: <c13ac165-7cbd-4e53-914e-8c6bc28250e3@ti.com> (raw)
In-Reply-To: <20240425115535.t6bpcfhddacqfrbr@during>
On 25/04/24 17:25, Nishanth Menon wrote:
> On 15:24-20240425, Chintan Vankar wrote:
>> Add missing bootph-all property for CPSW MAC's PHY node
>> phy_gmii_sel.
>>
>> Signed-off-by: Chintan Vankar <c-vankar@ti.com>
>> ---
>>
>> This patch is based on linux-next tagged next-20240424.
>>
>> arch/arm64/boot/dts/ti/k3-am62-main.dtsi | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/arch/arm64/boot/dts/ti/k3-am62-main.dtsi b/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
>> index e9cffca073ef..7a6f7cdc4cbe 100644
>> --- a/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
>> +++ b/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
>> @@ -52,6 +52,7 @@ phy_gmii_sel: phy@4044 {
>> compatible = "ti,am654-phy-gmii-sel";
>> reg = <0x4044 0x8>;
>> #phy-cells = <1>;
>> + bootph-all;
>
> Do not do this at SoC level for peripherals that may or maynot be used
> at various boards.
>
Okay. I will move it to "k3-am625-sk.dts".
>> };
>>
>> epwm_tbclk: clock-controller@4130 {
>> --
>> 2.34.1
>>
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2024-04-25 12:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 9:54 [PATCH] arm64: dts: ti: k3-am62-main: Add bootph-all property in phy_gmii_sel node Chintan Vankar
2024-04-25 11:55 ` Nishanth Menon
2024-04-25 12:30 ` Chintan Vankar [this message]
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=c13ac165-7cbd-4e53-914e-8c6bc28250e3@ti.com \
--to=c-vankar@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=s-vadapalli@ti.com \
--cc=vigneshr@ti.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