From: Josua Mayer <josua@solid-run.com>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
Biju Das <biju.das.jz@bp.renesas.com>,
Jon Nettleton <jon@solid-run.com>,
Mikhail Anikin <mikhail.anikin@solid-run.com>,
Yazan Shhady <yazan.shhady@solid-run.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH RFC 1/2] regulator: dt-bindings: raa215300: add clock output
Date: Sun, 3 May 2026 14:32:58 +0000 [thread overview]
Message-ID: <af16a88b-ba5f-485b-991d-0ea1ec2f928e@solid-run.com> (raw)
In-Reply-To: <afadhRD4b94rrNZ-@sirena.co.uk>
Am 03.05.26 um 02:57 schrieb Mark Brown:
> On Sat, May 02, 2026 at 06:07:04PM +0200, Josua Mayer wrote:
>
>> + "#clock-cells":
>> + const: 0
>> +
>> + clock-output-names:
>> + maxItems: 1
>> +
>> clocks:
>> description: |
>> The clocks are optional. The RTC is disabled, if no clocks are
> Should there be a requirement for an input clock if a clock output is
> specified?
The input clock is same as for RTC, so I suppose yes.
In that case, which property should the dependency be based on?
#clock-cells ?
clock-output-names?
clock-output-names is optional, so I think #clock-cells is the only option.
Is it important to model this dependency?
Or is it sufficient that driver returns an error when clock is missing?
next prev parent reply other threads:[~2026-05-03 14:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-02 16:07 [PATCH RFC 0/2] regulator: raa215300: add support for configurable 32kHz clock output Josua Mayer
2026-05-02 16:07 ` [PATCH RFC 1/2] regulator: dt-bindings: raa215300: add " Josua Mayer
2026-05-03 0:57 ` Mark Brown
2026-05-03 14:32 ` Josua Mayer [this message]
2026-05-04 8:56 ` Geert Uytterhoeven
2026-05-02 16:07 ` [PATCH RFC 2/2] regulator: raa215300: add support for configurable 32kHz " Josua Mayer
2026-05-03 0:57 ` Mark Brown
2026-05-03 14:49 ` Josua Mayer
2026-05-03 15:13 ` Josua Mayer
2026-05-03 9:24 ` [PATCH RFC 0/2] " Biju Das
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=af16a88b-ba5f-485b-991d-0ea1ec2f928e@solid-run.com \
--to=josua@solid-run.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=jon@solid-run.com \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mikhail.anikin@solid-run.com \
--cc=robh@kernel.org \
--cc=yazan.shhady@solid-run.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