From: "Rob Herring (Arm)" <robh@kernel.org>
To: Konrad Dybcio <konradybcio@kernel.org>
Cc: Conor Dooley <conor+dt@kernel.org>,
linux-kernel@vger.kernel.org,
Srinivas Kandagatla <srini@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
devicetree@vger.kernel.org,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Subject: Re: [PATCH] dt-bindings: nvmem: consumer: Make 'nvmem' an array of one-item entries
Date: Wed, 10 Jun 2026 14:28:47 -0500 [thread overview]
Message-ID: <178111967044.674793.5974554745587773283.robh@kernel.org> (raw)
In-Reply-To: <20260610-topic-nvmem_schema_warning_fix-v1-1-4029becf13f9@oss.qualcomm.com>
On Wed, 10 Jun 2026 14:52:42 +0200, Konrad Dybcio wrote:
> From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
>
> 'nvmem' unlike 'nvmem-cells', consumes references to just a single
> phandle with no arguments (i.e. with 0 cells).
>
> Constrain the schema to enforce that, so that the number of such
> single-item entries can then be regulated by IP block-specific YAMLs.
>
> Suggested-by: Rob Herring <robh@kernel.org>
> Signed-off-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
> ---
> qcom/qcs6490-rb3gen2.dtb: pmic@2 (qcom,pm8350c): pwm:nvmem: [[397, 398]] is too short
> from schema $id: http://devicetree.org/schemas/mfd/qcom,spmi-pmic.yaml
> qcom/qcs6490-rb3gen2.dtb: pwm (qcom,pm8350c-pwm): nvmem: [[397, 398]] is too short
> from schema $id: http://devicetree.org/schemas/leds/leds-qcom-lpg.yaml
> ---
> Documentation/devicetree/bindings/nvmem/nvmem-consumer.yaml | 2 ++
> 1 file changed, 2 insertions(+)
>
Given we're close to the merge window I applied so it goes into 7.2.
Rob
next prev parent reply other threads:[~2026-06-10 19:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 12:52 [PATCH] dt-bindings: nvmem: consumer: Make 'nvmem' an array of one-item entries Konrad Dybcio
2026-06-10 19:28 ` Rob Herring (Arm) [this message]
2026-06-11 7:41 ` Konrad Dybcio
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=178111967044.674793.5974554745587773283.robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.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