public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Alexander Dahl <ada@thorsis.com>
To: Claudiu Beznea <claudiu.beznea@tuxon.dev>
Cc: Alexander Dahl <ada@thorsis.com>,
	Nicolas Ferre <nicolas.ferre@microchip.com>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Ryan Wanner <ryan.wanner@microchip.com>,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
	Srinivas Kandagatla <srini@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>
Subject: Re: [PATCH v3 09/19] dt-bindings: nvmem: microchip-otpc: Add required clocks
Date: Fri, 20 Feb 2026 10:58:25 +0100	[thread overview]
Message-ID: <20260220-bloomers-runny-e69ab1966b9c@thorsis.com> (raw)
In-Reply-To: <f406abde-c7d1-4ed6-b7dd-5336956bc795@tuxon.dev>

Hello Claudiu,

Am Sat, Jan 31, 2026 at 05:47:05PM +0200 schrieb Claudiu Beznea:
> 
> 
> On 1/20/26 17:44, Alexander Dahl wrote:
> > The OTPC requires both the peripheral clock through PMC and the main RC
> > oscillator.  Seemed to work without explicitly enabling those clocks on
> > sama7g5 before, but did not on sam9x60.
> > 
> > Older datasheets were not clear and explicit about this, but recent are,
> > e.g. SAMA7G5 series datasheet (DS60001765B),
> > section 30.4.1 Power Management:
> > 
> > > The OTPC is clocked through the Power Management Controller (PMC).
> > > The user must power on the main RC oscillator and enable the
> > > peripheral clock of the OTPC prior to reading or writing the OTP
> > > memory.
> 
> As this was not mentioned in the previous datasheet versions, the current
> driver don't handle those clocks, and it probably worked as the clocks were
> enabled by bootloaders, I think the clocks should be marked as required and
> this patch to be propagated as a fix along with fixes on driver and device
> trees.

What do you mean by "clocks should be marked as required"?  Where?
How?  Is something more necessary, than already done here?

> I'll let DT binding maintainers for the final decision on this.
> 
> > 
> > Link: https://lore.kernel.org/linux-clk/ec34efc2-2051-4b8a-b5d8-6e2fd5e08c28@microchip.com/T/#u
> 
> Why this link here?

That was the original discussion and at the time the sama7g5 datasheet
mentioned a thing missing in the sam9x60 datasheet.  So that
discussion was the only reference for why this change is needed for
sam9x60.  Will drop the line in v4 then.

Greets
Alex

> 
> > Signed-off-by: Alexander Dahl <ada@thorsis.com>
> > ---
> > 
> > Notes:
> >      v3:
> >      - Removed clock-names (led to confusion, and not used by the driver anyways)
> >      - Removed redundant example
> >      v2:
> >      - new patch, not present in v1
> > 
> >   .../devicetree/bindings/nvmem/microchip,sama7g5-otpc.yaml | 8 ++++++++
> >   1 file changed, 8 insertions(+)
> > 
> > diff --git a/Documentation/devicetree/bindings/nvmem/microchip,sama7g5-otpc.yaml b/Documentation/devicetree/bindings/nvmem/microchip,sama7g5-otpc.yaml
> > index 9a7aaf64eef32..847dfb67c6b72 100644
> > --- a/Documentation/devicetree/bindings/nvmem/microchip,sama7g5-otpc.yaml
> > +++ b/Documentation/devicetree/bindings/nvmem/microchip,sama7g5-otpc.yaml
> > @@ -29,6 +29,11 @@ properties:
> >     reg:
> >       maxItems: 1
> > +  clocks:
> > +    items:
> > +      - description: main rc oscillator
> > +      - description: otpc peripheral clock
> > +
> >   required:
> >     - compatible
> >     - reg
> > @@ -37,6 +42,8 @@ unevaluatedProperties: false
> >   examples:
> >     - |
> > +    #include <dt-bindings/clock/at91.h>
> > +    #include <dt-bindings/clock/microchip,sama7g5-pmc.h>
> >       #include <dt-bindings/nvmem/microchip,sama7g5-otpc.h>
> >       otpc: efuse@e8c00000 {
> > @@ -44,6 +51,7 @@ examples:
> >           reg = <0xe8c00000 0xec>;
> >           #address-cells = <1>;
> >           #size-cells = <1>;
> > +        clocks = <&pmc PMC_TYPE_CORE SAMA7G5_PMC_MAIN_RC>, <&pmc PMC_TYPE_PERIPHERAL 67>;
> >           temperature_calib: calib@1 {
> >               reg = <OTP_PKT(1) 76>;
> 


  parent reply	other threads:[~2026-02-20  9:58 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-20 14:37 [PATCH v3 00/19] Microchip OTPC driver on SAM9X60 exposing UIDxR as additional nvmem device Alexander Dahl
2026-01-20 14:37 ` [PATCH v3 01/19] MAINTAINERS: Add sam9/sama to (AT91) SoC support Alexander Dahl
2026-01-20 14:37 ` [PATCH v3 02/19] dt-bindings: clock: at91: Split up per SoC partially Alexander Dahl
2026-01-22 16:46   ` Rob Herring (Arm)
2026-01-31 15:43   ` Claudiu Beznea
2026-01-20 14:37 ` [PATCH v3 03/19] dt-bindings: clock: at91: Allow referencing main rc oscillator in DT Alexander Dahl
2026-01-31 15:44   ` Claudiu Beznea
2026-02-09  8:08     ` Alexander Dahl
2026-03-08 16:43       ` Claudiu Beznea
2026-01-20 14:37 ` [PATCH v3 04/19] clk: at91: Use new PMC bindings Alexander Dahl
2026-01-31 15:44   ` Claudiu Beznea
2026-01-20 14:37 ` [PATCH v3 05/19] clk: at91: sama7d65: Use highest PMC definition as max index Alexander Dahl
2026-01-31 15:45   ` Claudiu Beznea
2026-01-20 14:37 ` [PATCH v3 06/19] clk: at91: Allow enabling main_rc_osc through DT Alexander Dahl
2026-01-31 15:45   ` Claudiu Beznea
2026-01-20 14:37 ` [PATCH v3 07/19] clk: at91: Add peripheral id for OTPC Alexander Dahl
2026-01-31 15:45   ` Claudiu Beznea
2026-01-20 15:44 ` Alexander Dahl
2026-01-20 15:44   ` [PATCH v3 08/19] dt-bindings: nvmem: microchip-otpc: Add compatible for SAM9X60 Alexander Dahl
2026-01-20 15:44   ` [PATCH v3 09/19] dt-bindings: nvmem: microchip-otpc: Add required clocks Alexander Dahl
2026-01-20 16:30     ` Rob Herring (Arm)
2026-01-31 15:47     ` Claudiu Beznea
2026-01-31 15:51       ` Claudiu Beznea
2026-02-20  9:58       ` Alexander Dahl [this message]
2026-03-08 16:42         ` Claudiu Beznea
2026-03-08 16:45           ` Claudiu Beznea
2026-01-20 15:44   ` [PATCH v3 10/19] nvmem: microchip-otpc: Avoid reading a write-only register Alexander Dahl
2026-01-31 15:58     ` Claudiu Beznea
2026-01-20 15:44   ` [PATCH v3 11/19] nvmem: microchip-otpc: Fix swapped 'sleep' and 'timeout' parameters Alexander Dahl
2026-01-31 16:00     ` Claudiu Beznea
2026-01-20 15:44   ` [PATCH v3 12/19] nvmem: microchip-otpc: Add SAM9X60 support Alexander Dahl
2026-01-31 15:53     ` Claudiu Beznea
2026-01-20 15:44   ` [PATCH v3 13/19] nvmem: microchip-otpc: Enable necessary clocks Alexander Dahl
2026-01-31 16:03     ` Claudiu Beznea
2026-01-20 15:44   ` [PATCH v3 14/19] nvmem: microchip-otpc: Expose UID registers as 2nd nvmem device Alexander Dahl
2026-01-31 16:11     ` Claudiu Beznea
2026-02-20 10:38       ` Alexander Dahl
2026-03-08 16:40         ` Claudiu Beznea
2026-01-20 15:44   ` [PATCH v3 15/19] ARM: dts: microchip: Use new PMC bindings Alexander Dahl
2026-01-20 15:44   ` [PATCH v3 16/19] ARM: dts: microchip: sama7g5: Add OTPC clocks Alexander Dahl
2026-01-20 15:44   ` [PATCH v3 17/19] ARM: dts: microchip: sam9x60: Add OTPC node Alexander Dahl
2026-01-20 15:44   ` [PATCH v3 18/19] ARM: dts: microchip: sam9x60_curiosity: Enable OTP Controller Alexander Dahl
2026-01-20 15:44   ` [PATCH v3 19/19] dt-bindings: clock: at91: Remove old PMC definitions Alexander Dahl
2026-01-22 16:47     ` Rob Herring (Arm)

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=20260220-bloomers-runny-e69ab1966b9c@thorsis.com \
    --to=ada@thorsis.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolas.ferre@microchip.com \
    --cc=robh@kernel.org \
    --cc=ryan.wanner@microchip.com \
    --cc=srini@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