All of lore.kernel.org
 help / color / mirror / Atom feed
From: richard@bit42.se
To: Sean Anderson <sean.anderson@linux.dev>
Cc: "Srinivas Kandagatla" <srinivas.kandagatla@linaro.org>,
	linux-kernel@vger.kernel.org,
	"Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
	"Michael Walle" <michael@walle.cc>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Subject: Re: [PATCH 2/2] nvmem: Remove qoriq-efuse in favor of layerscape-sfp
Date: Mon, 18 Mar 2024 09:32:35 +0100	[thread overview]
Message-ID: <6f5636e65df5616395cc8e24f63b09ef@bit42.se> (raw)
In-Reply-To: <20240316002026.1808336-2-sean.anderson@linux.dev>

On 2024-03-16 01:20, Sean Anderson wrote:
> The qoriq-efuse driver is a duplicate of layerscape-sfp.c. The T-series
> uses TA 2.0, while Layerscape uses TA 2.1 or 3.0 (depending on the
> chip). Add appropriate compatibles to the layerscape-sfp driver and
> remove the qoriq-efuse driver. I did not add support for P-series SoCs,
> since they use TA 1.0 which doesn't share a major version with either 
> of
> the existing implementations.
> 
> The qoriq-efuse driver does not properly abstract the location/offset 
> of
> the fuses properly, instead exposing the device's whole address range 
> to
> userspace. This is not appropriate, as the fuses only occupy a small
> portion of this range. The layerscape-sfp module correctly constrains
> the nvmem size to the fuses size. This represents a (necessary)
> compatibility break. The qoriq-efuse driver has been in-tree for around
> six months. Hopefully this will limit the fallout.
> 
> I would appreciate if someone with access to trust architecture 2.0 
> user
> guide could confirm the number of fuses.
> 
> Fixes: 0861110bb421 ("nvmem: add new NXP QorIQ eFuse driver")
> Signed-off-by: Sean Anderson <sean.anderson@linux.dev>
I don't think Fixes is appropriate here. Apart from that:

Acked-by: Richard Alpe <richard@bit42.se>

  reply	other threads:[~2024-03-18  8:32 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 [this message]
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
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=6f5636e65df5616395cc8e24f63b09ef@bit42.se \
    --to=richard@bit42.se \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael@walle.cc \
    --cc=niklas.soderlund@ragnatech.se \
    --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.