From: sashiko-bot@kernel.org
To: "Alexander Dahl" <ada@thorsis.com>
Cc: devicetree@vger.kernel.org, linux-clk@vger.kernel.org,
robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v4 15/16] ARM: dts: microchip: sam9x60_curiosity: Enable OTP Controller
Date: Thu, 05 Nov 2026 14:27:16 +0000 [thread overview]
Message-ID: <sashiko-outbox-199240@kernel.org> (raw)
In-Reply-To: <20261105110715.2486432-16-ada@thorsis.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] ARM: dts: microchip: redundant otpc status in sam9x60_curiosity.dts
--
commit 3ab977663934498a6526ef5c90d107058dabd158
Author: Alexander Dahl <ada@thorsis.com>
ARM: dts: microchip: sam9x60_curiosity: Enable OTP Controller
This commit sets status = "okay" on the &otpc node in
at91-sam9x60_curiosity.dts to enable the OTP controller on the SAM9X60
Curiosity board.
> diff --git a/arch/arm/boot/dts/microchip/at91-sam9x60_curiosity.dts b/arch/arm/boot/dts/microchip/at91-sam9x60_curiosity.dts
> index b9ffd9e5faacc..c110a8e87568a 100644
> --- a/arch/arm/boot/dts/microchip/at91-sam9x60_curiosity.dts
> +++ b/arch/arm/boot/dts/microchip/at91-sam9x60_curiosity.dts
> @@ -252,6 +252,10 @@ ethernet-phy@0 {
> };
> };
>
> +&otpc {
> + status = "okay";
> +};
[Severity: Medium]
Is this status override needed, or is status = "disabled" missing from the
base otpc node in arch/arm/boot/dts/microchip/sam9x60.dtsi?
In arch/arm/boot/dts/microchip/sam9x60.dtsi (added in commit 35ed4513c16e),
the otpc node is defined without a status property:
otpc: efuse@eff00000 {
compatible = "microchip,sama7g5-otpc", "syscon";
reg = <0xeff00000 0xec>;
#address-cells = <1>;
#size-cells = <1>;
clocks = <&pmc PMC_TYPE_CORE SAM9X60_PMC_MAIN_RC>, <&pmc PMC_TYPE_PERIPHERAL 46>;
};
Because __of_device_is_available() in drivers/of/base.c treats a node without
a status property as enabled by default, the OTP controller is already
enabled on all boards that include sam9x60.dtsi (such as at91-sam9x60ek.dts).
When mchp_otpc_probe() in drivers/nvmem/microchip-otpc.c probes the node, it
calls devm_clk_bulk_get_all_enabled(), keeping SAM9X60_PMC_MAIN_RC and
peripheral clock 46 permanently enabled.
Should otpc in sam9x60.dtsi have status = "disabled" by default so individual
boards opt in with status = "okay", or is this override in
at91-sam9x60_curiosity.dts redundant?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261105110715.2486432-1-ada@thorsis.com?part=15
next prev parent reply other threads:[~2026-11-05 14:27 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 11:06 [PATCH v4 00/16] Microchip OTPC driver on SAM9X60 exposing UIDxR as additional nvmem device Alexander Dahl
2026-11-05 11:06 ` [PATCH v4 01/16] MAINTAINERS: Add sam9/sama to (AT91) SoC support Alexander Dahl
2026-11-05 11:06 ` [PATCH v4 02/16] dt-bindings: clock: at91: Split up per SoC partially Alexander Dahl
2026-11-05 14:21 ` sashiko-bot
2026-11-06 10:57 ` Krzysztof Kozlowski
2026-11-06 11:02 ` Alexander Dahl
2026-11-05 11:06 ` [PATCH v4 03/16] dt-bindings: clock: at91: Allow referencing main rc oscillator in DT Alexander Dahl
2026-11-06 11:03 ` Krzysztof Kozlowski
2026-11-05 11:06 ` [PATCH v4 04/16] clk: at91: Use new per SoC PMC clock index definitions Alexander Dahl
2026-11-05 11:06 ` [PATCH v4 05/16] clk: at91: Allow enabling main_rc_osc through DT Alexander Dahl
2026-11-05 14:22 ` sashiko-bot
2026-11-06 2:39 ` kernel test robot
2026-11-05 11:06 ` [PATCH v4 06/16] clk: at91: Add peripheral clock id for OTPC Alexander Dahl
2026-11-05 14:29 ` sashiko-bot
2026-11-05 11:06 ` [PATCH v4 07/16] dt-bindings: nvmem: microchip-otpc: Add required clocks Alexander Dahl
2026-11-05 14:21 ` sashiko-bot
2026-11-06 11:05 ` Krzysztof Kozlowski
2026-11-05 11:06 ` [PATCH v4 08/16] nvmem: microchip-otpc: Avoid reading a write-only register Alexander Dahl
2026-11-05 11:06 ` [PATCH v4 09/16] nvmem: microchip-otpc: Fix swapped 'sleep' and 'timeout' parameters Alexander Dahl
2026-11-05 11:06 ` [PATCH v4 10/16] nvmem: microchip-otpc: Enable necessary clocks Alexander Dahl
2026-11-05 11:06 ` [PATCH v4 11/16] nvmem: microchip-otpc: Expose UID registers as 2nd nvmem device Alexander Dahl
2026-11-05 11:06 ` [PATCH v4 12/16] ARM: dts: microchip: Use new per SoC PMC bindings Alexander Dahl
2026-11-05 11:06 ` [PATCH v4 13/16] ARM: dts: microchip: sama7g5: Add OTPC clocks Alexander Dahl
2026-11-05 14:26 ` sashiko-bot
2026-11-05 11:06 ` [PATCH v4 14/16] ARM: dts: microchip: sam9x60: Add OTPC node Alexander Dahl
2026-11-05 11:06 ` [PATCH v4 15/16] ARM: dts: microchip: sam9x60_curiosity: Enable OTP Controller Alexander Dahl
2026-11-05 14:27 ` sashiko-bot [this message]
2026-11-05 11:06 ` [PATCH v4 16/16] dt-bindings: clock: at91: Remove old PMC definitions Alexander Dahl
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=sashiko-outbox-199240@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=ada@thorsis.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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.