From: Pavel Machek <pavel@denx.de>
To: biju.das.jz@bp.renesas.com
Cc: "nobuhiro.iwamatsu.x90@mail.toshiba"
<nobuhiro.iwamatsu.x90@mail.toshiba>,
"biju.das.au" <biju.das.au@gmail.com>,
"cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: Re: [cip-dev] [PATCH 6.12.y-cip 4/5] arm64: dts: renesas: r9a09g047e57-smarc: Add gpio keys
Date: Mon, 29 Dec 2025 21:57:50 +0100 [thread overview]
Message-ID: <aVLrTt0DmgE2fubv@duo.ucw.cz> (raw)
In-Reply-To: <TY3PR01MB1134650A811981E9B7EBCC1CD86B2A@TY3PR01MB11346.jpnprd01.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1452 bytes --]
Hi!
> > > From: Biju Das <biju.das.jz@bp.renesas.com>
> > >
> > > [ Upstram commit 9e95446b0cf93a91bc3b3b64c6d423f4024a6ff0 ]
> > >
> > > RZ/G3E SMARC EVK has 3 user buttons called USER_SW1, USER_SW2 and
> > > USER_SW3 and SLEEP button with NMI support. Add a DT node in device
> > > tree to instantiate the gpio-keys driver for these buttons.
> > >
> > > The system can enter into STR state by pressing the sleep button and
> > > wakeup from STR is done by pressing power button. The USER_SW{1,2,3}
> > > configured as wakeup-source, so it can wakeup the system during s2idle.
> > >
> > > Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
> > > Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
> > > Link:
> > > https://lore.kernel.org/20250702092755.70847-1-biju.das.jz@bp.renesas.
> > > com
> > > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> > > [Biju: Squashed the commit 3e5df910b592d4 ("arm64: dts: renesas:
> > > r9a09g047e57-smarc: Fix gpio key's pin control node"]
> >
> > Why did you need to squash the commit?
>
> Previously Pavel mentioned to squash fixes patches like this
> So that cip-kenel have clean functional patch.
I'm not sure if I would request the squash here; I guess both options
would be okay here.
Best regards,
Pavel
--
In cooperation with DENX Software Engineering GmbH, HRB 165235 Munich,
Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2025-12-29 20:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 12:29 [PATCH 6.12.y-cip 0/5] Add gpio keys/sleep button support for RZ/G3E Biju
2025-12-19 12:29 ` [PATCH 6.12.y-cip 1/5] pinctrl: renesas: rzg2l: Validate pins before setting mux function Biju
2025-12-19 12:29 ` [PATCH 6.12.y-cip 2/5] pinctrl: renesas: rzg2l: Add suspend/resume support for Schmitt control registers Biju
2025-12-19 12:29 ` [PATCH 6.12.y-cip 3/5] pinctrl: renesas: rzg2l: Drop unnecessary pin configurations Biju
2025-12-19 12:29 ` [PATCH 6.12.y-cip 4/5] arm64: dts: renesas: r9a09g047e57-smarc: Add gpio keys Biju
2025-12-24 5:17 ` nobuhiro.iwamatsu.x90
2025-12-24 9:30 ` Biju Das
2025-12-24 21:19 ` nobuhiro.iwamatsu.x90
2025-12-29 20:57 ` Pavel Machek [this message]
2025-12-29 21:12 ` Pavel Machek
2025-12-31 10:06 ` Biju Das
2025-12-19 12:29 ` [PATCH 6.12.y-cip 5/5] arm64: dts: renesas: r9a09g047e57-smarc: Use Schmitt input for NMI function Biju
2025-12-29 21:13 ` [PATCH 6.12.y-cip 0/5] Add gpio keys/sleep button support for RZ/G3E Pavel Machek
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=aVLrTt0DmgE2fubv@duo.ucw.cz \
--to=pavel@denx.de \
--cc=biju.das.au@gmail.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=cip-dev@lists.cip-project.org \
--cc=nobuhiro.iwamatsu.x90@mail.toshiba \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.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