From: Nishanth Menon <nm@ti.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>
Cc: <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Tero Kristo <kristo@kernel.org>, Nishanth Menon <nm@ti.com>,
<vaishnav.a@ti.com>, <afd@ti.com>, <u-kumar1@ti.com>
Subject: [PATCH 0/3] arm64: dts: ti: k3-j7200: Fixes for various dtbs_checks warnings
Date: Mon, 24 Apr 2023 12:36:20 -0500 [thread overview]
Message-ID: <20230424173623.477577-1-nm@ti.com> (raw)
Hi,
Few fixups for j7200 dtbs_check warnings.
Bootlog: https://gist.github.com/nmenon/6a37fca2f05633b7153e661d2516deab
NOTE: lets see the discussion summary of [1] to see where to take this
series, but, I will put it out here in the list for discussion anyways.
[1] https://lore.kernel.org/all/76da0b98-3274-b047-db11-ecabc117ae11@ti.com/
Nishanth Menon (3):
arm64: dts: ti: k3-j7200-mcu-wakeup: Remove 0x unit address prefix
from nodename
arm64: dts: ti: k3-j7200-mcu-wakeup: Switch mcu_syscon to
ti,j721e-system-controller
arm64: dts: ti: k3-j7200-mcu-wakeup: Split fss node up
.../boot/dts/ti/k3-j7200-mcu-wakeup.dtsi | 29 ++++++++++++-------
1 file changed, 19 insertions(+), 10 deletions(-)
--
2.40.0
next reply other threads:[~2023-04-24 17:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 17:36 Nishanth Menon [this message]
2023-04-24 17:36 ` [PATCH 1/3] arm64: dts: ti: k3-j7200-mcu-wakeup: Remove 0x unit address prefix from nodename Nishanth Menon
2023-04-24 17:36 ` [PATCH 2/3] arm64: dts: ti: k3-j7200-mcu-wakeup: Switch mcu_syscon to ti,j721e-system-controller Nishanth Menon
2023-04-24 17:36 ` [PATCH 3/3] arm64: dts: ti: k3-j7200-mcu-wakeup: Split fss node up Nishanth Menon
2023-04-24 18:34 ` Kumar, Udit
2023-04-24 18:55 ` Andrew Davis
2023-04-25 12:27 ` Nishanth Menon
2023-06-06 16:16 ` [PATCH 0/3] arm64: dts: ti: k3-j7200: Fixes for various dtbs_checks warnings Nishanth Menon
2023-06-15 13:40 ` (subset) " 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=20230424173623.477577-1-nm@ti.com \
--to=nm@ti.com \
--cc=afd@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=u-kumar1@ti.com \
--cc=vaishnav.a@ti.com \
--cc=vigneshr@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox