From: Grygorii Strashko <grygorii.strashko@ti.com>
To: Roger Quadros <rogerq@kernel.org>, <ssantosh@kernel.org>
Cc: <nm@ti.com>, <lokeshvutla@ti.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] ARM: dts: keystone-k2*-evm: Fix mdio node status to "okay"
Date: Thu, 2 Sep 2021 14:21:10 +0300 [thread overview]
Message-ID: <0f54033a-cbb3-6e00-edf7-946c4a5be3f8@ti.com> (raw)
In-Reply-To: <20210824105858.19496-2-rogerq@kernel.org>
On 24/08/2021 13:58, Roger Quadros wrote:
> As per Device Tree Specification [1], the status parameter of nodes can
> be "okay", "disabled", etc. "ok" is not a valid parameter.
>
> U-boot Driver Model does not recognize status="ok" either and treats
> the node as disabled.
>
> [1] https://github.com/devicetree-org/devicetree-specification/releases/tag/v0.3
>
> Cc: Grygorii Strashko <grygorii.strashko@ti.com>
> Signed-off-by: Roger Quadros <rogerq@kernel.org>
> ---
> arch/arm/boot/dts/keystone-k2e-evm.dts | 2 +-
> arch/arm/boot/dts/keystone-k2hk-evm.dts | 2 +-
> arch/arm/boot/dts/keystone-k2l-evm.dts | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
Thank you.
Reviewed-by: Grygorii Strashko <grygorii.strashko@ti.com>
--
Best regards,
grygorii
next prev parent reply other threads:[~2021-09-02 11:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-24 10:58 [PATCH v2 0/2] ARM: dts: keystone-k2*-evm: Fix mdio and dss node status Roger Quadros
2021-08-24 10:58 ` [PATCH v2 1/2] ARM: dts: keystone-k2*-evm: Fix mdio node status to "okay" Roger Quadros
2021-09-02 11:21 ` Grygorii Strashko [this message]
2021-08-24 10:58 ` [PATCH v2 2/2] ARM: dts: keystone-k2g-evm: Fix dss " Roger Quadros
2021-08-24 11:05 ` [PATCH v2 0/2] ARM: dts: keystone-k2*-evm: Fix mdio and dss node status Roger Quadros
2021-08-25 16:17 ` Nishanth Menon
2021-10-25 7:38 ` Roger Quadros
2021-09-14 12:31 ` Roger Quadros
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=0f54033a-cbb3-6e00-edf7-946c4a5be3f8@ti.com \
--to=grygorii.strashko@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=nm@ti.com \
--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
all inboxes | Powered by JetHome®