From: Josua Mayer <josua@solid-run.com>
To: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, 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>
Cc: 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, devicetree@vger.kernel.org,
linux-renesas-soc@vger.kernel.org,
Josua Mayer <josua@solid-run.com>
Subject: [PATCH RFC 0/2] regulator: raa215300: add support for configurable 32kHz clock output
Date: Sat, 02 May 2026 18:07:03 +0200 [thread overview]
Message-ID: <20260502-raa215300-clkout-v1-0-fd1c2a240963@solid-run.com> (raw)
Add driver support and extend bindings for Renesas RAA215300 PMIC 32kHz
clock output feature on pin MPIO2.
Signed-off-by: Josua Mayer <josua@solid-run.com>
---
Josua Mayer (2):
regulator: dt-bindings: raa215300: add clock output
regulator: raa215300: add support for configurable 32kHz clock output
.../bindings/regulator/renesas,raa215300.yaml | 6 +
drivers/regulator/raa215300.c | 132 +++++++++++++++++++++
2 files changed, 138 insertions(+)
---
base-commit: 254f49634ee16a731174d2ae34bc50bd5f45e731
change-id: 20260502-raa215300-clkout-c3ed84024888
Best regards,
--
Josua Mayer <josua@solid-run.com>
next reply other threads:[~2026-05-02 16:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-02 16:07 Josua Mayer [this message]
2026-05-02 16:07 ` [PATCH RFC 1/2] regulator: dt-bindings: raa215300: add clock output Josua Mayer
2026-05-03 0:57 ` Mark Brown
2026-05-03 14:32 ` Josua Mayer
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=20260502-raa215300-clkout-v1-0-fd1c2a240963@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