From: Conor Dooley <conor@kernel.org>
To: Sean Anderson <sean.anderson@linux.dev>
Cc: "Srinivas Kandagatla" <srinivas.kandagatla@linaro.org>,
"Richard Alpe" <richard@bit42.se>,
linux-kernel@vger.kernel.org,
"Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
"Michael Walle" <michael@walle.cc>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Rob Herring" <robh+dt@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: nvmem: Remove fsl,t1023-sfp in favor of fsl,layerscape-sfp
Date: Mon, 18 Mar 2024 15:40:45 +0000 [thread overview]
Message-ID: <20240318-scarf-startup-64088b1d8d35@spud> (raw)
In-Reply-To: <9daf9c8f-6606-4ff6-8065-6a32fa0d152c@linux.dev>
[-- Attachment #1: Type: text/plain, Size: 506 bytes --]
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-03-18 15:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-16 0:20 [PATCH 1/2] dt-bindings: nvmem: Remove fsl,t1023-sfp in favor of fsl,layerscape-sfp Sean Anderson
2024-03-16 0:20 ` [PATCH 2/2] nvmem: Remove qoriq-efuse in favor of layerscape-sfp Sean Anderson
2024-03-18 8:32 ` richard
2024-03-18 15:08 ` Sean Anderson
2024-03-17 15:10 ` [PATCH 1/2] dt-bindings: nvmem: Remove fsl,t1023-sfp in favor of fsl,layerscape-sfp Conor Dooley
2024-03-18 15:08 ` Sean Anderson
2024-03-18 15:40 ` Conor Dooley [this message]
2024-03-18 15:48 ` Sean Anderson
2024-03-19 17:55 ` Conor Dooley
2024-03-21 16:21 ` Sean Anderson
2024-03-22 7:01 ` Krzysztof Kozlowski
2024-03-22 16:26 ` Sean Anderson
2024-03-22 18:14 ` Conor Dooley
2024-03-22 18:26 ` Sean Anderson
2024-03-17 21:12 ` Rob Herring
2024-03-18 8:16 ` richard
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=20240318-scarf-startup-64088b1d8d35@spud \
--to=conor@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@walle.cc \
--cc=niklas.soderlund@ragnatech.se \
--cc=richard@bit42.se \
--cc=robh+dt@kernel.org \
--cc=sean.anderson@linux.dev \
--cc=srinivas.kandagatla@linaro.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.