[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOCHtYhK36QyKOmQhY+Q31rB23ASoxUXTX+0R1tzK-ZhvvWSLA@mail.gmail.com>
Date: Fri, 23 Aug 2024 10:33:37 -0500
From: Robert Nelson <robertcnelson@...il.com>
To: Roger Quadros <rogerq@...nel.org>
Cc: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>,
Vignesh Raghavendra <vigneshr@...com>, Nishanth Menon <nm@...com>, Andrew Davis <afd@...com>, Jai Luthra <j-luthra@...com>,
Siddharth Vadapalli <s-vadapalli@...com>, Jared McArthur <j-mcarthur@...com>,
Jason Kridner <jkridner@...gleboard.org>, Deepak Khatri <lorforlinux@...gleboard.org>,
Drew Fustini <drew@...gleboard.org>
Subject: Re: [PATCH v3 2/2] arm64: dts: ti: Add k3-am67a-beagley-ai
> > +
> > +&cpsw3g {
> > + pinctrl-names = "default";
> > + pinctrl-0 = <&rgmii1_pins_default>, <&gbe_pmx_obsclk>;
>
> Why do you need OBSCLK for Ethernet MAC?
> The OBSCLK is connected to the Ethernet PHY via C406 which is not even populated.
> It seems that the PHY is clocked by a crystal oscillator X5 so doesn't really
> need OBSCLK in the stock configuration?
Ah crap, I'll take a look at this... I bet it's left over from the
first pcb, (all my first rev pcb's are now locked up so i don't use
them anymore).. Seeed/BeagleBoard was playing it safe and designing
in both options.. Once the internal clocks were verified newer
revisions removed the external clock.
Yeah, I'm pretty sure final production boards removed every external
clock option.
Thanks!
--
Robert Nelson
https://rcn-ee.com/
Powered by blists - more mailing lists