From: Grygorii Strashko <grygorii.strashko@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-omap@vger.kernel.org>,
<devicetree@vger.kernel.org>, Rob Herring <robh+dt@kernel.org>,
Grygorii Strashko <grygorii.strashko@ti.com>
Subject: [PATCH 0/3] ARM: dts: ti: fix ti,no-reset-on-init usage
Date: Sat, 22 May 2021 01:24:08 +0300 [thread overview]
Message-ID: <20210521222411.17547-1-grygorii.strashko@ti.com> (raw)
The ti,no-reset-on-init flag need to be at the interconnect target module
level for the modules that have it defined.
The ti-sysc driver handles this case, but produces warning, not a critical
issue.
Grygorii Strashko (3):
ARM: dts: am57xx-cl-som-am57x: fix ti,no-reset-on-init flag for gpios
ARM: dts: am437x-gp-evm: fix ti,no-reset-on-init flag for gpios
ARM: dts: am335x: fix ti,no-reset-on-init flag for gpios
arch/arm/boot/dts/am335x-baltos.dtsi | 4 ++--
arch/arm/boot/dts/am335x-evmsk.dts | 2 +-
arch/arm/boot/dts/am335x-moxa-uc-2100-common.dtsi | 2 +-
arch/arm/boot/dts/am335x-moxa-uc-8100-common.dtsi | 2 +-
arch/arm/boot/dts/am33xx-l4.dtsi | 2 +-
arch/arm/boot/dts/am437x-gp-evm.dts | 5 ++++-
arch/arm/boot/dts/am437x-l4.dtsi | 2 +-
arch/arm/boot/dts/am57xx-cl-som-am57x.dts | 5 ++---
arch/arm/boot/dts/dra7-l4.dtsi | 4 ++--
9 files changed, 15 insertions(+), 13 deletions(-)
--
2.17.1
next reply other threads:[~2021-05-21 22:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 22:24 Grygorii Strashko [this message]
2021-05-21 22:24 ` [PATCH 1/3] ARM: dts: am57xx-cl-som-am57x: fix ti,no-reset-on-init flag for gpios Grygorii Strashko
2021-05-21 22:24 ` [PATCH 2/3] ARM: dts: am437x-gp-evm: " Grygorii Strashko
2021-05-21 22:24 ` [PATCH 3/3] ARM: dts: am335x: " Grygorii Strashko
2021-05-27 12:07 ` [PATCH 0/3] ARM: dts: ti: fix ti,no-reset-on-init usage Tony Lindgren
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=20210521222411.17547-1-grygorii.strashko@ti.com \
--to=grygorii.strashko@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).