From: Nishanth Menon <nm@ti.com>
To: Roger Quadros <rogerq@kernel.org>
Cc: <ssantosh@kernel.org>, <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] ARM: dts: keystone-k2*-evm: Fix mdio and dss node status
Date: Fri, 20 Aug 2021 12:30:32 -0500 [thread overview]
Message-ID: <20210820173032.45st33x5435tmfyx@fragrance> (raw)
In-Reply-To: <20210820095341.5619-1-rogerq@kernel.org>
On 12:53-20210820, Roger Quadros wrote:
> Hi Santosh,
>
> This series fixes mdio and dss status nodes from "ok" to "okay"
>
> As per Device Tree core schema [1], status parameter of nodes can be either
> "okay" or "disabled".
>
> U-boot Driver Model does not recognize status="ok" either and treats
> the node as disabled.
>
> [1] https://github.com/devicetree-org/dt-schema/blob/master/schemas/dt-core.yaml#L36
Wondering if it is better to refer to the device tree specification
itself rather than the schema implementation of the specification..
https://github.com/devicetree-org/devicetree-specification/releases/tag/v0.3
for example.
>
> cheers,
> -roger
>
> Roger Quadros (2):
> ARM: dts: keystone-k2*-evm: Fix mdio node status to "okay"
> ARM: dts: keystone-k2g-evm: Fix dss node status to "okay"
>
> arch/arm/boot/dts/keystone-k2e-evm.dts | 2 +-
> arch/arm/boot/dts/keystone-k2g-evm.dts | 2 +-
> arch/arm/boot/dts/keystone-k2hk-evm.dts | 2 +-
> arch/arm/boot/dts/keystone-k2l-evm.dts | 2 +-
> 4 files changed, 4 insertions(+), 4 deletions(-)
>
> --
> 2.17.1
>
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
prev parent reply other threads:[~2021-08-20 17:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-20 9:53 [PATCH 0/2] ARM: dts: keystone-k2*-evm: Fix mdio and dss node status Roger Quadros
2021-08-20 9:53 ` [PATCH 1/2] ARM: dts: keystone-k2*-evm: Fix mdio node status to "okay" Roger Quadros
2021-08-20 9:53 ` [PATCH 2/2] ARM: dts: keystone-k2g-evm: Fix dss " Roger Quadros
2021-08-20 17:30 ` Nishanth Menon [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=20210820173032.45st33x5435tmfyx@fragrance \
--to=nm@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rogerq@kernel.org \
--cc=ssantosh@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).