From: Judith Mendez <jm@ti.com>
To: Conor Dooley <conor@kernel.org>
Cc: Srinivas Kandagatla <srini@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Kunihiko Hayashi <hayashi.kunihiko@socionext.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/3] dt-bindings: nvmem: uniphier-efuse: Add ti,am62p-efuse compatible
Date: Thu, 10 Sep 2026 09:32:12 -0500 [thread overview]
Message-ID: <0110ed3d-64da-4678-ab17-3a42a9274a95@ti.com> (raw)
In-Reply-To: <aqEuyLac2OGkSYX7@squawk>
Hi Conor,
On 9/9/26 05:02, Conor Dooley wrote:
> On Tue, Sep 08, 2026 at 03:28:47PM -0500, Judith Mendez wrote:
>> Hi Conor,
>>
>> On 9/3/26 13:00, Conor Dooley wrote:
>>> On Wed, Sep 02, 2026 at 05:27:57PM -0500, Judith Mendez wrote:
>>>> Add ti,am62p-efuse as a compatible string to the uniphier-efuse binding.
>>>> The uniphier-efuse driver can be used to read AM62P efuse registers as
>>>> well for GP_SW silicon revision detection.
>>>>
>>>> Signed-off-by: Judith Mendez <jm@ti.com>
>>>
>>> Why is a fallback compatible not suitable here?
>>> Either it is, and you should add one, or you need to explain in hte
>>> commit message why it is not.
>>
>> Do you mean the following? :
>>
>> compatible:
>> oneOf:
>> - const: socionext,uniphier-efuse
>> - items:
>> - const: ti,am62p-efuse
>> - const: socionext,uniphier-efuse
>
> Correct.
Ok, will implement. thanks.
~ Judith
next prev parent reply other threads:[~2026-09-10 14:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 22:27 [PATCH v2 0/3] Support AM62P silicon revision detection via uniphier-efuse Judith Mendez
2026-09-02 22:27 ` [PATCH v2 1/3] dt-bindings: nvmem: uniphier-efuse: Add ti,am62p-efuse compatible Judith Mendez
2026-09-02 22:34 ` sashiko-bot
2026-09-03 18:00 ` Conor Dooley
2026-09-08 20:28 ` Judith Mendez
2026-09-09 10:02 ` Conor Dooley
2026-09-10 14:32 ` Judith Mendez [this message]
2026-09-02 22:27 ` [PATCH v2 2/3] nvmem: uniphier-efuse: Enable for K3 SoCs Judith Mendez
2026-09-02 22:38 ` sashiko-bot
2026-09-02 22:27 ` [PATCH v2 3/3] nvmem: uniphier-efuse: Add ti,am62p-efuse compatible Judith Mendez
2026-09-02 22:34 ` sashiko-bot
2026-09-03 10:06 ` [PATCH v2 0/3] Support AM62P silicon revision detection via uniphier-efuse Kunihiko Hayashi
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=0110ed3d-64da-4678-ab17-3a42a9274a95@ti.com \
--to=jm@ti.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hayashi.kunihiko@socionext.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=robh@kernel.org \
--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