All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: linux-omap@vger.kernel.org
Cc: "Benoît Cousson" <bcousson@baylibre.com>, devicetree@vger.kernel.org
Subject: [PATCH 00/19] Clean-up for lots of omap dtb warnings
Date: Fri, 29 Apr 2022 10:05:54 +0300	[thread overview]
Message-ID: <20220429070613.62360-1-tony@atomide.com> (raw)

Hi,

With the recent omap clock driver changes, we can clean-up lots of make
dbs warnings. We get lots of warnings for make W=1 dtbs for
unique_unit_address, and make W=2 dtbs for node_name_chars_strict.

A lot of these come from omap3 because of large amount of SoC variants
and boards. This series reduces the warnings for omaps by over 80k
warnings.

Regards,

Tony


Tony Lindgren (19):
  ARM: dts: Group omap3 CONTROL_DEVCONF0 clocks
  ARM: dts: Group omap3 CONTROL_DEVCONF1 clocks
  ARM: dts: Group omap3 CM_FCLKEN1_CORE clocks
  ARM: dts: Group omap3 crypto accelerator clocks
  ARM: dts: Group omap3 CM_ICLKEN1_CORE clocks
  ARM: dts: Group omap3 CM_ICLKEN3_CORE clocks
  ARM: dts: Group omap3 CM_CLKSEL_CORE clocks
  ARM: dts: Group omap3 CM_FCLKEN_WKUP clocks
  ARM: dts: Group omap3 CM_ICLKEN_WKUP clocks
  ARM: dts: Group omap3 CM_CLKSEL_WKUP clocks
  ARM: dts: Group omap3 CM_CLKSEL1_PLL clocks
  ARM: dts: Group omap3 CM_CLKOUT_CTRL clocks
  ARM: dts: Group omap3 CM_FCLKEN_DSS clocks
  ARM: dts: Group omap3 CM_CLKSEL_DSS clocks
  ARM: dts: Group omap3 CM_FCLKEN_CAM clocks
  ARM: dts: Group omap3 CM_FCLKEN_PER clocks
  ARM: dts: Group omap3 CM_ICLKEN_PER clocks
  ARM: dts: Group omap3 CM_CLKSEL_PER clocks
  ARM: dts: Group omap3 CM_CLKSEL1_EMU clocks

 arch/arm/boot/dts/am35xx-clocks.dtsi          |   52 +-
 arch/arm/boot/dts/omap3430es1-clocks.dtsi     |  184 +-
 .../boot/dts/omap34xx-omap36xx-clocks.dtsi    |  275 ++-
 ...map36xx-am35xx-omap3430es2plus-clocks.dtsi |   79 +-
 arch/arm/boot/dts/omap36xx-clocks.dtsi        |   17 +-
 .../dts/omap36xx-omap3430es2plus-clocks.dtsi  |  136 +-
 arch/arm/boot/dts/omap3xxx-clocks.dtsi        | 2044 +++++++++--------
 7 files changed, 1540 insertions(+), 1247 deletions(-)

-- 
2.35.2

             reply	other threads:[~2022-04-29  7:06 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-29  7:05 Tony Lindgren [this message]
2022-04-29  7:05 ` [PATCH 01/19] ARM: dts: Group omap3 CONTROL_DEVCONF0 clocks Tony Lindgren
2022-04-29  7:05 ` [PATCH 02/19] ARM: dts: Group omap3 CONTROL_DEVCONF1 clocks Tony Lindgren
2022-04-29  7:05 ` [PATCH 03/19] ARM: dts: Group omap3 CM_FCLKEN1_CORE clocks Tony Lindgren
2022-04-29  7:05 ` [PATCH 04/19] ARM: dts: Group omap3 crypto accelerator clocks Tony Lindgren
2022-04-29  7:05 ` [PATCH 05/19] ARM: dts: Group omap3 CM_ICLKEN1_CORE clocks Tony Lindgren
2022-04-29  7:06 ` [PATCH 06/19] ARM: dts: Group omap3 CM_ICLKEN3_CORE clocks Tony Lindgren
2022-04-29  7:06 ` [PATCH 07/19] ARM: dts: Group omap3 CM_CLKSEL_CORE clocks Tony Lindgren
2022-04-29  7:06 ` [PATCH 08/19] ARM: dts: Group omap3 CM_FCLKEN_WKUP clocks Tony Lindgren
2022-04-29  7:06 ` [PATCH 09/19] ARM: dts: Group omap3 CM_ICLKEN_WKUP clocks Tony Lindgren
2022-04-29  7:06 ` [PATCH 10/19] ARM: dts: Group omap3 CM_CLKSEL_WKUP clocks Tony Lindgren
2022-04-29  7:06 ` [PATCH 11/19] ARM: dts: Group omap3 CM_CLKSEL1_PLL clocks Tony Lindgren
2022-04-29  7:06 ` [PATCH 12/19] ARM: dts: Group omap3 CM_CLKOUT_CTRL clocks Tony Lindgren
2022-04-29  7:06 ` [PATCH 13/19] ARM: dts: Group omap3 CM_FCLKEN_DSS clocks Tony Lindgren
2022-04-29  7:06 ` [PATCH 14/19] ARM: dts: Group omap3 CM_CLKSEL_DSS clocks Tony Lindgren
2022-04-29  7:06 ` [PATCH 15/19] ARM: dts: Group omap3 CM_FCLKEN_CAM clocks Tony Lindgren
2022-04-29  7:06 ` [PATCH 16/19] ARM: dts: Group omap3 CM_FCLKEN_PER clocks Tony Lindgren
2022-04-29  7:06 ` [PATCH 17/19] ARM: dts: Group omap3 CM_ICLKEN_PER clocks Tony Lindgren
2022-04-29  7:06 ` [PATCH 18/19] ARM: dts: Group omap3 CM_CLKSEL_PER clocks Tony Lindgren
2022-04-29  7:06 ` [PATCH 19/19] ARM: dts: Group omap3 CM_CLKSEL1_EMU clocks 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=20220429070613.62360-1-tony@atomide.com \
    --to=tony@atomide.com \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-omap@vger.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 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.