From: Krzysztof Kozlowski <krzk@kernel.org>
To: Shawn Guo <shawnguo@kernel.org>
Cc: Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>,
Rob Herring <robh+dt@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
Stefan Agner <stefan@agner.ch>, Anson Huang <Anson.Huang@nxp.com>,
linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: watchdog: fsl-imx: document i.MX compatibles
Date: Thu, 29 Oct 2020 17:13:10 +0100 [thread overview]
Message-ID: <20201029161310.GA29346@kozik-lap> (raw)
In-Reply-To: <20201029143508.GO28755@dragon>
On Thu, Oct 29, 2020 at 10:35:09PM +0800, Shawn Guo wrote:
> On Sat, Sep 26, 2020 at 06:23:00PM +0200, Krzysztof Kozlowski wrote:
> > Document all ARMv5, ARMv6 and ARMv7 i.MX compatibles used in DTSes (even
> > though driver binds only to fsl,imx21-wdt) to fix dtbs_check warnings
> > like:
> >
> > arch/arm/boot/dts/imx53-qsb.dt.yaml: gpio@53fe0000: compatible:
> > ['fsl,imx53-gpio', 'fsl,imx35-gpio'] is not valid under any of the given schemas
> >
> > Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
> > ---
> > .../devicetree/bindings/watchdog/fsl-imx-wdt.yaml | 14 ++++++++++++++
> > 1 file changed, 14 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/watchdog/fsl-imx-wdt.yaml b/Documentation/devicetree/bindings/watchdog/fsl-imx-wdt.yaml
> > index 991b4e33486e..a06e70f44fd0 100644
> > --- a/Documentation/devicetree/bindings/watchdog/fsl-imx-wdt.yaml
> > +++ b/Documentation/devicetree/bindings/watchdog/fsl-imx-wdt.yaml
> > @@ -18,10 +18,24 @@ properties:
> > - const: fsl,imx21-wdt
> > - items:
> > - enum:
> > + - fsl,imx25-wdt
> > + - fsl,imx27-wdt
> > + - fsl,imx31-wdt
> > + - fsl,imx35-wdt
> > + - fsl,imx50-wdt
> > + - fsl,imx51-wdt
> > + - fsl,imx53-wdt
> > + - fsl,imx6q-wdt
> > + - fsl,imx6sl-wdt
> > + - fsl,imx6sll-wdt
> > + - fsl,imx6sx-wdt
> > + - fsl,imx6ul-wdt
> > + - fsl,imx7d-wdt
> > - fsl,imx8mm-wdt
> > - fsl,imx8mn-wdt
> > - fsl,imx8mp-wdt
> > - fsl,imx8mq-wdt
>
> Could you add the following two as well?
>
> - fsl,ls1012a-wdt
> - fsl,ls1043a-wdt
I focused in these patches on i.MX but I can fix the Layerscape as well.
Best regards,
Krzysztof
prev parent reply other threads:[~2020-10-29 16:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-26 16:23 [PATCH 1/3] dt-bindings: watchdog: fsl-imx: document i.MX compatibles Krzysztof Kozlowski
2020-09-26 16:23 ` [PATCH 2/3] ARM: dts: imx: align watchdog node name with dtschema Krzysztof Kozlowski
2020-10-29 14:38 ` Shawn Guo
2020-09-26 16:23 ` [PATCH 3/3] ARM: dts: vf: " Krzysztof Kozlowski
2020-10-29 14:39 ` Shawn Guo
2020-09-29 19:13 ` [PATCH 1/3] dt-bindings: watchdog: fsl-imx: document i.MX compatibles Rob Herring
2020-10-29 14:35 ` Shawn Guo
2020-10-29 16:13 ` Krzysztof Kozlowski [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=20201029161310.GA29346@kozik-lap \
--to=krzk@kernel.org \
--cc=Anson.Huang@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=stefan@agner.ch \
--cc=wim@linux-watchdog.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).