mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: srini@kernel.org
To: gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org, Judith Mendez <jm@ti.com>,
	Kunihiko Hayashi <hayashi.kunihiko@socionext.com>,
	Srinivas Kandagatla <srini@kernel.org>
Subject: [PATCH 3/9] nvmem: uniphier-efuse: Enable for K3 SoCs
Date: Fri,  2 Oct 2026 11:13:46 +0100	[thread overview]
Message-ID: <20261002101352.1084447-4-srini@kernel.org> (raw)
In-Reply-To: <20261002101352.1084447-1-srini@kernel.org>

From: Judith Mendez <jm@ti.com>

Add ARCH_K3 dependency and set to always build for K3 architecture.
The uniphier-efuse driver must be builtin to support early probe of
k3-socinfo during boot. The k3-socinfo driver requires the efuse
provider for reading silicon revision information on AM62p device.

Signed-off-by: Judith Mendez <jm@ti.com>
Reviewed-by: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
Signed-off-by: Srinivas Kandagatla <srini@kernel.org>
---
 drivers/nvmem/Kconfig | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/drivers/nvmem/Kconfig b/drivers/nvmem/Kconfig
index c36c2a4c2a0b..df65e7ecfa21 100644
--- a/drivers/nvmem/Kconfig
+++ b/drivers/nvmem/Kconfig
@@ -541,8 +541,9 @@ config NVMEM_U_BOOT_ENV
 
 config NVMEM_UNIPHIER_EFUSE
 	tristate "UniPhier SoCs eFuse support"
-	depends on ARCH_UNIPHIER || COMPILE_TEST
+	depends on ARCH_UNIPHIER || ARCH_K3 || COMPILE_TEST
 	depends on HAS_IOMEM
+	default y if ARCH_K3
 	help
 	  This is a simple driver to dump specified values of UniPhier SoC
 	  from eFuse.
-- 
2.53.0


  parent reply	other threads:[~2026-10-02 10:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-02 10:13 [PATCH 0/9] nvmem: patches for 7.4 srini
2026-10-02 10:13 ` [PATCH 1/9] dt-bindings: nvmem: qfprom: Add compatible for Qualcomm Maili srini
2026-10-02 10:13 ` [PATCH 2/9] dt-bindings: nvmem: uniphier-efuse: Add ti,am62p-efuse compatible srini
2026-10-02 10:13 ` srini [this message]
2026-10-02 10:13 ` [PATCH 4/9] nvmem: core: Add const to pattrs allocation type srini
2026-10-02 10:13 ` [PATCH 5/9] nvmem: layouts: Support fixed-layout as the nvmem device node itself srini
2026-10-02 10:13 ` [PATCH 6/9] dt-bindings: mfd: mediatek: mt6397: add mt6323 PMIC EFUSE srini
2026-10-02 10:13 ` [PATCH 7/9] nvmem: add mt6323 PMIC EFUSE driver srini
2026-10-02 10:13 ` [PATCH 8/9] nvmem: remove duplicated reference counting srini
2026-10-02 10:13 ` [PATCH 9/9] nvmem: protect nvmem_device::ops with SRCU srini

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=20261002101352.1084447-4-srini@kernel.org \
    --to=srini@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hayashi.kunihiko@socionext.com \
    --cc=jm@ti.com \
    --cc=linux-kernel@vger.kernel.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®