[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e7a5cc9c-1ee1-053d-1372-9ba2300565d1@microchip.com>
Date: Tue, 19 Sep 2023 10:40:45 +0000
From: <Parthiban.Veerasooran@...rochip.com>
To: <andrew@...n.ch>
CC: <davem@...emloft.net>, <edumazet@...gle.com>, <kuba@...nel.org>,
<pabeni@...hat.com>, <robh+dt@...nel.org>,
<krzysztof.kozlowski+dt@...aro.org>, <conor+dt@...nel.org>,
<corbet@....net>, <Steen.Hegelund@...rochip.com>,
<rdunlap@...radead.org>, <horms@...nel.org>,
<casper.casan@...il.com>, <netdev@...r.kernel.org>,
<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-doc@...r.kernel.org>, <Horatiu.Vultur@...rochip.com>,
<Woojung.Huh@...rochip.com>, <Nicolas.Ferre@...rochip.com>,
<UNGLinuxDriver@...rochip.com>, <Thorsten.Kummermehr@...rochip.com>
Subject: Re: [RFC PATCH net-next 6/6] microchip: lan865x: add device-tree
support for Microchip's LAN865X MACPHY
Hi Andrew,
On 14/09/23 7:37 am, Andrew Lunn wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
>> + oa-chunk-size: true
>> + oa-tx-cut-through: true
>> + oa-rx-cut-through: true
>> + oa-protected: true
>
> Please split this up into properties all OA TC6 devices are expected
> to use, and those specific to the LAN865x. Put the generic properties
> into a .yaml file, which you then inherit into the device specific
> yaml file.
>
> Also, LAN865x specific properties should have a vendor prefix.
Sure, will do both.
Best Regards,
Parthiban V
>
> Andrew
Powered by blists - more mailing lists