From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Tim Harvey <tharvey@gateworks.com>
Cc: Device Tree Mailing List <devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>,
Shawn Guo <shawnguo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>
Subject: Re: [PATCH 2/2] arm64: dts: imx: Add i.MX8M Plus Gateworks gw7400 dts support
Date: Sat, 9 Apr 2022 12:42:53 +0200 [thread overview]
Message-ID: <7dc8b66d-0569-183a-554c-4a0d273bbf0b@linaro.org> (raw)
In-Reply-To: <CAJ+vNU1D5GowKH97mpS+zT97XTavbKfijt6P8KEHN8-DD+gtYA@mail.gmail.com>
On 08/04/2022 17:52, Tim Harvey wrote:
>>> + pps {
>>> + compatible = "pps-gpio";
>>> + pinctrl-names = "default";
>>> + pinctrl-0 = <&pinctrl_pps>;
>>> + gpios = <&gpio1 12 GPIO_ACTIVE_HIGH>;
>>> + status = "okay";
>>
>> No need for status.
>
> ok. What is the best way to know if a binding uses status or not?
>
> Documentation/devicetree/bindings/net/fsl,fec.yaml for example does
> not mention it uses status, yet it does.
status is not part of binding at all. All nodes have by default
status=okay, just the DTSI disables many of them. Therefore you need to
add status=okay only to these which are explicitly disabled.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-04-09 10:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 21:04 [PATCH 1/2] dt-bindings: arm: Add i.MX8M Plus Gateworks GW74xx board Tim Harvey
2022-04-07 21:04 ` [PATCH 2/2] arm64: dts: imx: Add i.MX8M Plus Gateworks gw7400 dts support Tim Harvey
2022-04-08 7:13 ` Krzysztof Kozlowski
2022-04-08 15:52 ` Tim Harvey
2022-04-09 10:42 ` Krzysztof Kozlowski [this message]
2022-04-08 7:07 ` [PATCH 1/2] dt-bindings: arm: Add i.MX8M Plus Gateworks GW74xx board Krzysztof Kozlowski
2022-04-08 15:45 ` Tim Harvey
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=7dc8b66d-0569-183a-554c-4a0d273bbf0b@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=tharvey@gateworks.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;
as well as URLs for NNTP newsgroup(s).