public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Dragan Simic <dsimic@manjaro.org>
To: Andrey Leonchikov <andreil499@gmail.com>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	heiko@sntech.de, dmitry.osipenko@collabora.com,
	tglx@linutronix.de, amadeus@jmu.edu.cn,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: arm64: dts: rockchip: RK356x: Add OTP description.
Date: Tue, 16 Sep 2025 20:02:11 +0200	[thread overview]
Message-ID: <957705f3b0f6407031f76ca433a0541d@manjaro.org> (raw)
In-Reply-To: <20250912135542.2304150-1-andreil499@gmail.com>

Hello Andrey,

On 2025-09-12 15:55, Andrey Leonchikov wrote:
> Add OTP mapping, can be used on future by drivers.
> Contain a factory-programmed values for a various peripheral.
> U-Boot already use "CPU-ID" OTP value ("otp_id" on this patch).
> All values from original Rockchip sources tree on github.
> 
> Signed-off-by: Andrey Leonchikov <andreil499@gmail.com>

Thanks for the revised version of this patch.  As Jonas already pointed
out, [1] this patch needs more work before it can be accepted.

I'd suggest that this patch is temporarily dropped, and I'll include it
as part of my upcoming patch series that will handle the SoC binning,
with the appropriate tags.

[1] 
https://lore.kernel.org/linux-rockchip/6bd28aaf-aafd-436e-8799-fcdb07082660@kwiboo.se/

      parent reply	other threads:[~2025-09-16 18:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-12 13:55 arm64: dts: rockchip: RK356x: Add OTP description Andrey Leonchikov
2025-09-12 14:22 ` Jonas Karlman
2025-09-16 18:02 ` Dragan Simic [this message]

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=957705f3b0f6407031f76ca433a0541d@manjaro.org \
    --to=dsimic@manjaro.org \
    --cc=amadeus@jmu.edu.cn \
    --cc=andreil499@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.osipenko@collabora.com \
    --cc=heiko@sntech.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=robh@kernel.org \
    --cc=tglx@linutronix.de \
    /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