From: Tony Lindgren <tony@atomide.com>
To: Nishanth Menon <nm@ti.com>
Cc: Roger Quadros <rogerq@ti.com>, Keerthy <j-keerthy@ti.com>,
Jyri Sarha <jsarha@ti.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
Lokesh Vutla <lokeshvutla@ti.com>,
Rob Herring <robh+dt@kernel.org>, Tero Kristo <t-kristo@ti.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 2/5] arm64: dts: ti: k3-j721e*: Cleanup disabled nodes at SoC dtsi level
Date: Thu, 12 Nov 2020 16:19:06 +0200 [thread overview]
Message-ID: <20201112141906.GS26857@atomide.com> (raw)
In-Reply-To: <20201112014929.25227-3-nm@ti.com>
* Nishanth Menon <nm@ti.com> [201112 01:49]:
> The device tree standard states that when the status property is
> not present under a node, the okay value is assumed. There are many
> reasons for doing the same, the number of strings in the device
> tree, default power management functionality, etc. are a few of the
> reasons.
Reviewed-by: Tony Lindgren <tony@atomide.com>
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Nishanth Menon <nm@ti.com>
Cc: Tero Kristo <t-kristo@ti.com>,
devicetree@vger.kernel.org, Lokesh Vutla <lokeshvutla@ti.com>,
Keerthy <j-keerthy@ti.com>,
linux-kernel@vger.kernel.org, Jyri Sarha <jsarha@ti.com>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
Rob Herring <robh+dt@kernel.org>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
linux-arm-kernel@lists.infradead.org,
Roger Quadros <rogerq@ti.com>
Subject: Re: [PATCH V2 2/5] arm64: dts: ti: k3-j721e*: Cleanup disabled nodes at SoC dtsi level
Date: Thu, 12 Nov 2020 16:19:06 +0200 [thread overview]
Message-ID: <20201112141906.GS26857@atomide.com> (raw)
In-Reply-To: <20201112014929.25227-3-nm@ti.com>
* Nishanth Menon <nm@ti.com> [201112 01:49]:
> The device tree standard states that when the status property is
> not present under a node, the okay value is assumed. There are many
> reasons for doing the same, the number of strings in the device
> tree, default power management functionality, etc. are a few of the
> reasons.
Reviewed-by: Tony Lindgren <tony@atomide.com>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-11-12 14:19 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 1:49 [PATCH V2 0/5] arm64: dts: ti: Cleanup mix of "okay" and "disabled" usage Nishanth Menon
2020-11-12 1:49 ` Nishanth Menon
2020-11-12 1:49 ` [PATCH V2 1/5] arm64: dts: ti: k3-am65*: Cleanup disabled nodes at SoC dtsi level Nishanth Menon
2020-11-12 1:49 ` Nishanth Menon
2020-11-12 14:17 ` Tony Lindgren
2020-11-12 14:17 ` Tony Lindgren
2020-11-12 14:18 ` Tony Lindgren
2020-11-12 14:18 ` Tony Lindgren
2020-11-12 1:49 ` [PATCH V2 2/5] arm64: dts: ti: k3-j721e*: " Nishanth Menon
2020-11-12 1:49 ` Nishanth Menon
2020-11-12 14:19 ` Tony Lindgren [this message]
2020-11-12 14:19 ` Tony Lindgren
2020-11-12 1:49 ` [PATCH V2 3/5] arm64: dts: ti: am65/j721e: Fix up un-necessary status set to "okay" for crypto Nishanth Menon
2020-11-12 1:49 ` Nishanth Menon
2020-11-12 13:34 ` Tero Kristo
2020-11-12 13:34 ` Tero Kristo
2020-11-12 14:19 ` Tony Lindgren
2020-11-12 14:19 ` Tony Lindgren
2020-11-12 1:49 ` [PATCH V2 4/5] arm64: dts: ti: k3-am654-base-board: Fix up un-necessary status set to "okay" for USB Nishanth Menon
2020-11-12 1:49 ` Nishanth Menon
2020-11-12 13:01 ` Roger Quadros
2020-11-12 13:01 ` Roger Quadros
2020-11-12 14:19 ` Tony Lindgren
2020-11-12 14:19 ` Tony Lindgren
2020-11-12 1:49 ` [PATCH V2 5/5] arm64: dts: ti: am65/j721e/j7200: Mark firmware used uart as "reserved" Nishanth Menon
2020-11-12 1:49 ` Nishanth Menon
2020-11-12 14:24 ` Tony Lindgren
2020-11-12 14:24 ` Tony Lindgren
2020-11-12 15:56 ` Vignesh Raghavendra
2020-11-12 15:56 ` Vignesh Raghavendra
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=20201112141906.GS26857@atomide.com \
--to=tony@atomide.com \
--cc=devicetree@vger.kernel.org \
--cc=j-keerthy@ti.com \
--cc=jsarha@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=nm@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=robh+dt@kernel.org \
--cc=rogerq@ti.com \
--cc=t-kristo@ti.com \
--cc=tomi.valkeinen@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.