From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Rob Herring <robh@kernel.org>, Fabio Estevam <festevam@denx.de>,
linux-arm-kernel@lists.infradead.org, robh+dt@kernel.org,
devicetree@vger.kernel.org, linux-imx@nxp.com,
conor+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
shawnguo@kernel.org
Subject: Re: [PATCH 1/8] dt-bindings: input: fsl,scu-key: Document wakeup-source
Date: Sun, 29 Oct 2023 01:51:06 +0000 [thread overview]
Message-ID: <ZT26iscyHBkpEGlw@google.com> (raw)
In-Reply-To: <CAOMZO5Adr+au1em1cAR3E_irErXM3qd2FPiG0DJiU-Hskwgekg@mail.gmail.com>
Hi Fabio,
On Wed, Oct 25, 2023 at 05:07:39PM -0300, Fabio Estevam wrote:
> Hi Dmitry,
>
> On Thu, Sep 28, 2023 at 1:48 PM Rob Herring <robh@kernel.org> wrote:
> >
> >
> > On Tue, 26 Sep 2023 09:29:50 -0300, Fabio Estevam wrote:
> > > From: Fabio Estevam <festevam@denx.de>
> > >
> > > The SCU Key controller can be used as a system wakeup source.
> > >
> > > Document the 'wakeup-source' property.
> > >
> > > This fixes the following schema warning:
> > >
> > > system-controller: keys: 'wakeup-source' does not match any of the regexes: 'pinctrl-[0-9]+'
> > > from schema $id: http://devicetree.org/schemas/firmware/fsl,scu.yaml#
> > >
> > > Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> > > Signed-off-by: Fabio Estevam <festevam@denx.de>
> > > ---
> > > Documentation/devicetree/bindings/input/fsl,scu-key.yaml | 2 ++
> > > 1 file changed, 2 insertions(+)
> > >
> >
> > Acked-by: Rob Herring <robh@kernel.org>
>
> Could you please take this one?
Applied, thank you.
--
Dmitry
prev parent reply other threads:[~2023-10-29 1:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 12:29 [PATCH 1/8] dt-bindings: input: fsl,scu-key: Document wakeup-source Fabio Estevam
2023-09-26 12:29 ` [PATCH 2/8] dt-bindings: power: fsl,scu-pd: Document imx8dl Fabio Estevam
2023-09-27 15:08 ` Conor Dooley
2023-09-26 12:29 ` [PATCH 3/8] arm64: dts: imx8dxl: Pass fsl,imx8dl-scu-pd Fabio Estevam
2023-10-10 1:05 ` Shawn Guo
2023-09-26 12:29 ` [PATCH 4/8] arm64: dts: imx8dxl: Remove wakeup-irq Fabio Estevam
2023-09-26 12:29 ` [PATCH 5/8] dt-bindings: thermal: fsl,scu-thermal: Document imx8dl Fabio Estevam
2023-09-27 15:09 ` Conor Dooley
2023-09-28 13:32 ` Daniel Lezcano
2023-09-28 13:33 ` Fabio Estevam
2023-09-28 13:44 ` Daniel Lezcano
2023-09-26 12:29 ` [PATCH 6/8] arm64: dts: imx8dxl: Pass fsl,imx8dxl-sc-thermal Fabio Estevam
2023-09-26 12:29 ` [PATCH 7/8] dt-bindings: watchdog: fsl,scu-wdt: Document imx8dl Fabio Estevam
2023-09-27 15:09 ` Conor Dooley
2023-09-26 12:29 ` [PATCH 8/8] arm64: dts: imx8dxl: Pass fsl,imx8dxl-sc-wdt Fabio Estevam
2023-09-28 16:47 ` [PATCH 1/8] dt-bindings: input: fsl,scu-key: Document wakeup-source Rob Herring
2023-10-25 20:07 ` Fabio Estevam
2023-10-29 1:51 ` Dmitry Torokhov [this message]
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=ZT26iscyHBkpEGlw@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@denx.de \
--cc=festevam@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=shawnguo@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).