From: Stanislav Jakubek <stano.jakubek@gmail.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Lee Jones <lee@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Orson Zhai <orsonzhai@gmail.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Chunyan Zhang <zhang.lyra@gmail.com>,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>, Pavel Machek <pavel@ucw.cz>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Sebastian Reichel <sre@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
devicetree@vger.kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org,
linux-pm@vger.kernel.org, linux-rtc@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: mfd: sprd,sc2731: convert to YAML
Date: Wed, 30 Oct 2024 09:14:24 +0100 [thread overview]
Message-ID: <ZyHq4FJ0ubQVGREo@standask-GA-A55M-S2HP> (raw)
In-Reply-To: <7db6431e-1892-463e-9c74-cd466ae3ca32@kernel.org>
On Wed, Oct 30, 2024 at 08:48:25AM +0100, Krzysztof Kozlowski wrote:
> On 30/10/2024 08:42, Stanislav Jakubek wrote:
> >>
> >>> +
> >>> + '#address-cells':
> >>> + const: 1
> >>> +
> >>> + '#interrupt-cells':
> >>> + const: 1
> >>> +
> >>> + '#size-cells':
> >>> + const: 0
> >>> +
> >>> + regulators:
> >>> + type: object
> >>> + $ref: /schemas/regulator/sprd,sc2731-regulator.yaml#
> >>> +
> >>> +patternProperties:
> >>> + "^adc@[0-9a-f]+$":
> >>> + type: object
> >>> + $ref: /schemas/iio/adc/sprd,sc2720-adc.yaml#
> >>> +
> >>> + "^charger@[0-9a-f]+$":
> >>> + type: object
> >>> + $ref: /schemas/power/supply/sc2731-charger.yaml#
> >>> +
> >>> + "^efuse@[0-9a-f]+$":
> >>> + type: object
> >>> + $ref: /schemas/nvmem/sprd,sc2731-efuse.yaml#
> >>
> >> I don't think this was merged. You still have dependency.
> >
> > This is in next-20241029, which this patch is based on.
>
> Try what I wrote below and see if this works...
I assume you meant the MFD maintainers' tree here.
Yes, that tree doesn't have the nvmem patch this depends on.
Would the approach with listing the compatibles and additionalProperties:
true be considered a temporary workaround?
If so, should I split this into 2 patches?
- 1st patch with the nvmem workaround above
- 2nd with adding the nvmem $ref back (which would get merged later)
Regards,
Stanislav
>
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2024-10-30 8:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 19:02 Stanislav Jakubek
2024-10-30 6:43 ` Krzysztof Kozlowski
2024-10-30 7:42 ` Stanislav Jakubek
2024-10-30 7:48 ` Krzysztof Kozlowski
2024-10-30 8:14 ` Stanislav Jakubek [this message]
2024-10-31 9:50 ` Krzysztof Kozlowski
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=ZyHq4FJ0ubQVGREo@standask-GA-A55M-S2HP \
--to=stano.jakubek@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=lars@metafoo.de \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=orsonzhai@gmail.com \
--cc=pavel@ucw.cz \
--cc=robh@kernel.org \
--cc=sre@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=zhang.lyra@gmail.com \
/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®