From: Shawn Guo <shawnguo@kernel.org>
To: "Michal Vokáč" <michal.vokac@ysoft.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 5/6] ARM: dts: imx6dl-yapp43: Add support for new HW revision of the IOTA board
Date: Tue, 14 Mar 2023 08:42:01 +0800 [thread overview]
Message-ID: <20230314004201.GS143566@dragon> (raw)
In-Reply-To: <6a942ff5-4bf4-ae23-fe78-900d1965e821@ysoft.com>
On Mon, Mar 13, 2023 at 05:42:21PM +0100, Michal Vokáč wrote:
> > > + eeprom@57 {
> > > + compatible = "atmel,24c128";
> > > + reg = <0x57>;
> > > + pagesize = <64>;
> > > + status = "okay";
> >
> > The "okay" status is only needed to flip a "disabled" one.
>
> OK, I will remove the status "okay" from all device nodes defined
> by this dtsi that should be enabled by default.
>
> I assume that using status "okay" (or "disabled") for referenced
> nodes coming from included SoC dtsi files is fine even if these
> nodes already have the required status at the moment.
Yeah, that would be fine.
Shawn
> Otherwise I see no guarantee that the node will have my required
> status in the future as well. The status in the included files
> may be changed by someone else for whatever reason.
next prev parent reply other threads:[~2023-03-14 0:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 15:48 [PATCH 0/6] Add support for new boards in the imx6dl-yapp4 family Michal Vokáč
2023-02-10 15:48 ` [PATCH 1/6] dt-bindings: arm: fsl: Fix copy-paste error in comment Michal Vokáč
2023-02-11 11:45 ` Krzysztof Kozlowski
2023-03-13 8:27 ` Shawn Guo
2023-02-10 15:48 ` [PATCH 2/6] ARM: dts: imx6dl-yapp4: Change LED channel names according to dt-binding Michal Vokáč
2023-03-13 8:28 ` Shawn Guo
2023-03-13 8:48 ` Krzysztof Kozlowski
2023-03-13 10:57 ` Michal Vokáč
2023-02-10 15:48 ` [PATCH 3/6] ARM: dts: imx6dl-yapp4: Use reset-gpios property name Michal Vokáč
2023-03-13 8:29 ` Shawn Guo
2023-02-10 15:48 ` [PATCH 4/6] dt-bindings: arm: fsl: Add Y Soft IOTA Phoenix, Lynx, Pegasus and Pegasus+ Michal Vokáč
2023-02-11 11:45 ` Krzysztof Kozlowski
2023-02-10 15:48 ` [PATCH 5/6] ARM: dts: imx6dl-yapp43: Add support for new HW revision of the IOTA board Michal Vokáč
2023-03-13 8:23 ` Shawn Guo
2023-03-13 16:42 ` Michal Vokáč
2023-03-14 0:42 ` Shawn Guo [this message]
2023-02-10 15:48 ` [PATCH 6/6] MAINTAINERS: Add Michal Vokáč as yapp4 boards maintainer Michal Vokáč
2023-02-11 11:46 ` Krzysztof Kozlowski
2023-02-13 9:08 ` Michal Vokáč
2023-02-13 9:18 ` Krzysztof Kozlowski
2023-02-13 9:50 ` Michal Vokáč
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=20230314004201.GS143566@dragon \
--to=shawnguo@kernel.org \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.vokac@ysoft.com \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
/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).