[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fa047914-da03-4234-b48f-eebdf350795e@linux.dev>
Date: Mon, 18 Mar 2024 11:48:06 -0400
From: Sean Anderson <sean.anderson@...ux.dev>
To: Conor Dooley <conor@...nel.org>
Cc: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
Richard Alpe <richard@...42.se>, linux-kernel@...r.kernel.org,
Niklas Söderlund <niklas.soderlund@...natech.se>,
Michael Walle <michael@...le.cc>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Conor Dooley <conor+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Rob Herring <robh+dt@...nel.org>, devicetree@...r.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: nvmem: Remove fsl,t1023-sfp in favor of
fsl,layerscape-sfp
On 3/18/24 11:40, Conor Dooley wrote:
> On Mon, Mar 18, 2024 at 11:08:00AM -0400, Sean Anderson wrote:
>> On 3/17/24 11:10, Conor Dooley wrote:
>
>> > Additionally, should
>> > they fall back to t1023-sfp? I see that there's already some dts files
>> > with these compatibles in them but seemingly no driver support as there
>> > is for the t1023-sfp.
>>
>> I checked the reference manuals for these processors, and all of them use TA 2.0.
>
> Sounds like a fallback is suitable then, although that will require
> updating the various dts files.
Yes, a fallback (like what is done for the T-series) would be suitable,
but given that these devicetrees have been in-tree for eight years I
think it would be preferable to support the existing bindings for
compatibility purposes.
--Sean
Powered by blists - more mailing lists