mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sean Anderson <sean.anderson@seco.com>
To: Richard Alpe <richard@bit42.se>, srinivas.kandagatla@linaro.org
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	niklas.soderlund+renesas@ragnatech.se,
	Michael Walle <michael@walle.cc>
Subject: Re: [PATCH v5 2/2] nvmem: add new NXP QorIQ eFuse driver
Date: Tue, 12 Mar 2024 18:13:02 -0400	[thread overview]
Message-ID: <3bfc0393-70bb-4120-abfb-530eaaa88b25@seco.com> (raw)
In-Reply-To: <7fc69bf7-4f89-41c0-a800-6e7d450d8b20@seco.com>

On 3/12/24 18:09, Sean Anderson wrote:
> On 4/10/23 04:20, Richard Alpe wrote:
>> Add SFP (Security Fuse Processor) read support for NXP (Freescale)
>> QorIQ series SOC's.
>>
>> This patch adds support for the T1023 SOC using the SFP offset from
>> the existing T1023 device tree. In theory this should also work for
>> T1024, T1014 and T1013 which uses the same SFP base offset.
>>
>> Signed-off-by: Richard Alpe <richard@bit42.se>
>
> This seems like a duplicate of layerscape-sfp.c. The hardware is
> (presumably) quite similar, with the T1024RM referencing the QorIQ Trust
> Architecture User Guide version 2.0, and the L1046 (e.g.) referencing
> version 2.1.
>
> I think this driver should be removed in favor of the older driver.
> There are some problematic bits: most notably no offset is applied by
> this driver, so all fuses have an offset of 0x200. So we will need to
> implement/document this only for the "fsl,t1023-sfp" compatible, which
> has already made its way into the T1023 devicetree...

Actually, it seems like the driver was added long after the compatible
was added to t1023si-post.dtsi, so maybe we can just change the semantics
of the nvmem cell offset.

--Sean

> This really should have been caught during review; a quick grep for
> "SFP" would have revealed the duplication.
>
> --Sean


[Embedded World 2024, SECO SpA]<https://www.messe-ticket.de/Nuernberg/embeddedworld2024/Register/ew24517689>

  reply	other threads:[~2024-03-12 22:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-10  8:20 [PATCH v5 1/2] dt-bindings: nvmem: Add t1023-sfp efuse support Richard Alpe
2023-04-10  8:20 ` [PATCH v5 2/2] nvmem: add new NXP QorIQ eFuse driver Richard Alpe
2023-05-09 19:20   ` Niklas Söderlund
2023-07-28  7:20   ` richard
2024-03-12 22:09   ` Sean Anderson
2024-03-12 22:13     ` Sean Anderson [this message]
2023-04-10 17:15 ` [PATCH v5 1/2] dt-bindings: nvmem: Add t1023-sfp efuse support Krzysztof Kozlowski
2023-07-26  5:35 ` richard
2023-07-26  7:56   ` Krzysztof Kozlowski
2023-07-28  7:25 ` Srinivas Kandagatla

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=3bfc0393-70bb-4120-abfb-530eaaa88b25@seco.com \
    --to=sean.anderson@seco.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael@walle.cc \
    --cc=niklas.soderlund+renesas@ragnatech.se \
    --cc=richard@bit42.se \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®