[PATCH 2/4] net: phy: marvell: Allow targets to skip MII RX/TX errata
Timothy Pearson
tpearson at raptorengineering.com
Sat Mar 22 05:03:29 AEDT 2025
----- Original Message -----
> From: "Paul Fertser" <fercerpav at gmail.com>
> To: "Timothy Pearson" <tpearson at raptorengineering.com>
> Cc: "openbmc" <openbmc at lists.ozlabs.org>
> Sent: Friday, March 21, 2025 1:02:11 PM
> Subject: Re: [PATCH 2/4] net: phy: marvell: Allow targets to skip MII RX/TX errata
> On Fri, Mar 21, 2025 at 12:50:51PM -0500, Timothy Pearson wrote:
>> >> + /* Per the vendor, certain Marvell devices will not function if
>> >> + * the RGMII TX/RX delay registers are modified. If an
>> >> + * affected design has been selected, do not write the
>> >> + * RX/TX delay registers.
>> >> + */
>> >
>> > This doesn't say much. Please reference the actual errata document
>> > number or cite its text or find some other way to explain which
>> > devices are affected how. Proper implementation depends a lot on those
>> > details.
>>
>> Understood. I am navigating a bit of a sea of NDA restricted / proprietary
>> components here, apologies for the lack of detail.
>>
>> Let me see if I can get that information and get approval for public
>> disclosure. These patches are in support of the SIE Cronos board,
>> which unfortunately was designed by a third party without proper
>> U-boot / OpenBMC integration in mind. As a result, there are unique
>> hardware decisions that were made, and the DT is not authoritative
>> on these platforms.
>
> DT should be capable of describing any hardware, that's what it's made
> for. If some particular property is missing it can be added upstream
> and then added to the board's DT. It's not yet clear from this patch
> and its commit message what specifically is unique about this board.
Understood. I will attempt to get authorization to describe publicly in more detail.
More information about the openbmc
mailing list