From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Biju Das <biju.das.au@gmail.com>
Subject: Re: [PATCH v2 1/2] arm64: dts: renesas: rzg2ul-smarc: Enable PMIC and built-in RTC, GPIO and ONKEY
Date: Tue, 27 Feb 2024 15:16:50 +0100 [thread overview]
Message-ID: <CAMuHMdXarkL=pVH+4vutNf_g2MX=Y25YM1bFLHJjOE2OQAd+qA@mail.gmail.com> (raw)
In-Reply-To: <20240226194715.427597-2-biju.das.jz@bp.renesas.com>
Hi Biju,
On Mon, Feb 26, 2024 at 8:47 PM Biju Das <biju.das.jz@bp.renesas.com> wrote:
> Enable PMIC DA9062 and the built-in RTC, GPIO and ONKEY modules on the
> RZ/{G2UL,Five} SMARC EVK development boards.
>
> Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
> ---
> v1->v2:
> * Dropped disabled status from gpio and onkey nodes.
> * Added gpio hog nodes.
Thanks for the update!
> --- a/arch/arm64/boot/dts/renesas/rzg2ul-smarc.dtsi
> +++ b/arch/arm64/boot/dts/renesas/rzg2ul-smarc.dtsi
> @@ -5,6 +5,7 @@
> * Copyright (C) 2022 Renesas Electronics Corp.
> */
>
> +#include <dt-bindings/gpio/gpio.h>
Yep, we need this...
> #include "rzg2ul-smarc-pinfunction.dtsi"
> #include "rz-smarc-common.dtsi"
>
> @@ -23,6 +24,63 @@ &cpu_dai {
> &i2c0 {
> clock-frequency = <400000>;
>
> + da9062: pmic@58 {
> + compatible = "dlg,da9062";
> + reg = <0x58>;
> + gpio-controller;
> + #gpio-cells = <2>;
> +
> + gpio {
> + compatible = "dlg,da9062-gpio";
> + };
> +
> + onkey {
> + compatible = "dlg,da9062-onkey";
> + };
> +
> + pmic-good-hog {
> + gpio-hog;
> + gpios = <4 0>;
... so this can be replaced by <4 GPIO_ACTIVE_HIGH> ;-)
> + output-high;
> + line-name = "PMIC_PGOOD";
> + };
Same for the other gpios.
Anyway, LGTM
Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
i.e. will queue in renesas-devel for v6.10, with s/0/GPIO_ACTIVE_HIGH/.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2024-02-27 14:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 19:47 [PATCH v2 0/2] Enable DA9062 PMIC and built-in RTC, GPIO and ONKEY Biju Das
2024-02-26 19:47 ` [PATCH v2 1/2] arm64: dts: renesas: rzg2ul-smarc: Enable " Biju Das
2024-02-27 14:16 ` Geert Uytterhoeven [this message]
2024-02-26 19:47 ` [PATCH v2 2/2] arm64: dts: renesas: rzg2ul-smarc: [DO NOT APPLY] Add PMIC IRQ property Biju Das
2024-02-26 19:50 ` [PATCH v2 0/2] Enable DA9062 PMIC and built-in RTC, GPIO and ONKEY Geert Uytterhoeven
2024-02-26 19:57 ` 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='CAMuHMdXarkL=pVH+4vutNf_g2MX=Y25YM1bFLHJjOE2OQAd+qA@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=biju.das.au@gmail.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).