From: Wadim Egorov <w.egorov@phytec.de>
To: Vignesh Raghavendra <vigneshr@ti.com>,
nm@ti.com, kristo@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, upstream@lists.phytec.de
Subject: Re: [PATCH] arm64: dts: ti: k3-am642-phyboard-electra: Fix PRU-ICSSG Ethernet ports
Date: Mon, 26 May 2025 17:03:08 +0300 [thread overview]
Message-ID: <eae561e2-a600-4d68-994d-6f619a7c86b6@phytec.de> (raw)
In-Reply-To: <4f660adb-1cb4-4bcf-9d1c-c13e62818f07@ti.com>
Am 26.05.25 um 08:32 schrieb Vignesh Raghavendra:
>
>
> On 21/05/25 11:03, Wadim Egorov wrote:
>> For the ICSSG PHYs to operate correctly, a 25 MHz reference clock must
>> be supplied on CLKOUT0. Previously, our bootloader configured this
>> clock, which is why the PRU Ethernet ports appeared to work, but the
>> change never made it into the device tree.
>>
>
> Should this patch have a Fixes tag then?
Yes,
Fixes: 87adfd1ab03a ("arm64: dts: ti: am642-phyboard-electra: Add
PRU-ICSSG nodes")
>
>> Add clock properties to make EXT_REFCLK1.CLKOUT0 output a 25MHz clock.
>>
>> Signed-off-by: Wadim Egorov <w.egorov@phytec.de>
>> ---
>> arch/arm64/boot/dts/ti/k3-am642-phyboard-electra-rdk.dts | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/ti/k3-am642-phyboard-electra-rdk.dts b/arch/arm64/boot/dts/ti/k3-am642-phyboard-electra-rdk.dts
>> index f63c101b7d61..129524eb5b91 100644
>> --- a/arch/arm64/boot/dts/ti/k3-am642-phyboard-electra-rdk.dts
>> +++ b/arch/arm64/boot/dts/ti/k3-am642-phyboard-electra-rdk.dts
>> @@ -322,6 +322,8 @@ AM64X_IOPAD(0x0040, PIN_OUTPUT, 7) /* (U21) GPMC0_AD1.GPIO0_16 */
>> &icssg0_mdio {
>> pinctrl-names = "default";
>> pinctrl-0 = <&icssg0_mdio_pins_default &clkout0_pins_default>;
>> + assigned-clocks = <&k3_clks 157 123>;
>> + assigned-clock-parents = <&k3_clks 157 125>;
>> status = "okay";
>>
>> icssg0_phy1: ethernet-phy@1 {
>
next prev parent reply other threads:[~2025-05-26 14:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 5:33 Wadim Egorov
2025-05-26 5:32 ` Vignesh Raghavendra
2025-05-26 14:03 ` Wadim Egorov [this message]
2025-06-24 18:45 ` Vignesh Raghavendra
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=eae561e2-a600-4d68-994d-6f619a7c86b6@phytec.de \
--to=w.egorov@phytec.de \
--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=upstream@lists.phytec.de \
--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
all inboxes | Powered by JetHome®