All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peng Fan <peng.fan@oss.nxp.com>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>
Cc: devicetree@vger.kernel.org, imx@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Peng Fan <peng.fan@nxp.com>,
	Frank Li <Frank.Li@nxp.com>,
	Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH v4 0/2] Make i.MX9 OCOTP work as accessing controller
Date: Tue, 31 Dec 2024 10:19:38 +0800	[thread overview]
Message-ID: <20241231021938.GA11277@localhost.localdomain> (raw)
In-Reply-To: <20241223-imx-ocotp-v4-0-f504c1420640@nxp.com>

Hi Srinivas,

Is this patchset good for you to pick up?

Thanks,
Peng
On Mon, Dec 23, 2024 at 08:46:12AM +0800, Peng Fan (OSS) wrote:
>Previously there was discussion on using "feature-controller" or
>adding a specific node to group the fuse information for U-Boot to
>parse and update node. But rejected by DT maintainer(Rob).
>
>Since the STM32 engineers added access controller concept and landed
>the support in Linux Kernel, reuse the concept for i.MX.
>
>i.MX OCOTP eFuse has some bits to indicate a specific periphral or
>function is avaiable for current chip, for example i.MX93 has variants
>that not have NPU. So introduce '#access-controller-cells' for OCOTP,
>and add "#access-controllers = <&ocotp [gate_index]>" for periphrals
>that needs accessing control checking.
>
>In OCOTP driver, the nodes under "/" will be iterated, and checked
>if property "#access-controllers" exsits. If not allow access, detach
>the node.
>
>In the end, cpu nodes should still be handled by bootloader.
>And I may also update i.MX8M to use same method to support variants
>if this patchset is good.
>
>Signed-off-by: Peng Fan <peng.fan@nxp.com>
>---
>Changes in v4:
>- Add missing of_node_put(provider)
>- Typo fix in commit log
>- Link to v3: https://lore.kernel.org/r/20241219-imx-ocotp-v3-0-b22371098071@nxp.com
>
>Changes in v3:
>- Add A-b for patch 1
>- Use scoped API when iterate nodes and address build warning in patch 2
>- I am also thinking that to drop patch 2 to let
> bootloader to iterate the nodes that have access-controllers property and
> update the nodes before booting the kernel. Then just need patch 1 for
> the binding updates. Anyway, comments are welcomed.
>- Link to v2: https://lore.kernel.org/r/20241217-imx-ocotp-v2-0-3faa6cbff41b@nxp.com
>
>Changes in v2:
>- Add R-b for patch 1
>- Use '/' root node instead of '/soc' or '/soc@0' for patch 2
>- Link to v1: https://lore.kernel.org/r/20241212-imx-ocotp-v1-0-198bb0af86a0@nxp.com
>
>---
>Peng Fan (2):
>      dt-bindings: nvmem: imx-ocotp: Introduce #access-controller-cells
>      nvmem: imx-ocotp-ele: Support accessing controller for i.MX9
>
> .../devicetree/bindings/nvmem/imx-ocotp.yaml       |   5 +
> drivers/nvmem/imx-ocotp-ele.c                      | 184 ++++++++++++++++++++-
> include/dt-bindings/nvmem/fsl,imx93-ocotp.h        |  24 +++
> include/dt-bindings/nvmem/fsl,imx95-ocotp.h        |  43 +++++
> 4 files changed, 255 insertions(+), 1 deletion(-)
>---
>base-commit: 6d13015b67d58ddba56631c56e0a6f376ade0867
>change-id: 20241212-imx-ocotp-cbef304140f5
>
>Best regards,
>-- 
>Peng Fan <peng.fan@nxp.com>
>

      parent reply	other threads:[~2024-12-31  1:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-23  0:46 [PATCH v4 0/2] Make i.MX9 OCOTP work as accessing controller Peng Fan (OSS)
2024-12-23  0:46 ` [PATCH v4 1/2] dt-bindings: nvmem: imx-ocotp: Introduce #access-controller-cells Peng Fan (OSS)
2024-12-23  0:46 ` [PATCH v4 2/2] nvmem: imx-ocotp-ele: Support accessing controller for i.MX9 Peng Fan (OSS)
2025-01-06 10:32   ` Sascha Hauer
2024-12-31  2:19 ` Peng Fan [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=20241231021938.GA11277@localhost.localdomain \
    --to=peng.fan@oss.nxp.com \
    --cc=Frank.Li@nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=conor.dooley@microchip.com \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peng.fan@nxp.com \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --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.