devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Benoît Cousson" <bcousson@baylibre.com>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Tero Kristo" <kristo@kernel.org>,
	"Michael Turquette" <mturquette@baylibre.com>,
	"Stephen Boyd" <sboyd@kernel.org>
Cc: Andreas Kemnade <andreas@kemnade.info>,
	linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
	linux-clk@vger.kernel.org
Subject: [PATCH 0/4] Use reg instead of ti,bit-shift for clksel
Date: Tue, 13 Feb 2024 12:56:40 +0200	[thread overview]
Message-ID: <20240213105730.5287-1-tony@atomide.com> (raw)

Hi all,

This series updates the clksel clocks to use the standard reg property
instead of ti,bit-shift.

I'd like to apply these before we make further use of the clksel clocks
to reduce the dtb check warnings.

Regards,

Tony

Tony Lindgren (4):
  clk: ti: Handle possible address in the node name
  clk: ti: Improve clksel clock bit parsing for reg property
  ARM: dts: am3: Update clksel clocks to use reg instead of ti,bit-shift
  ARM: dts: omap3: Update clksel clocks to use reg instead of
    ti,bit-shift

 arch/arm/boot/dts/ti/omap/am33xx-clocks.dtsi  |  39 +-
 arch/arm/boot/dts/ti/omap/am35xx-clocks.dtsi  |  18 +-
 .../boot/dts/ti/omap/omap3430es1-clocks.dtsi  |  52 +-
 .../dts/ti/omap/omap34xx-omap36xx-clocks.dtsi |  86 +--
 ...map36xx-am35xx-omap3430es2plus-clocks.dtsi |  28 +-
 .../arm/boot/dts/ti/omap/omap36xx-clocks.dtsi |   7 +-
 .../omap/omap36xx-omap3430es2plus-clocks.dtsi |  46 +-
 .../arm/boot/dts/ti/omap/omap3xxx-clocks.dtsi | 510 +++++++++---------
 drivers/clk/ti/apll.c                         |  11 +-
 drivers/clk/ti/clk.c                          |  71 ++-
 drivers/clk/ti/clock.h                        |   1 +
 drivers/clk/ti/divider.c                      |   5 +-
 drivers/clk/ti/gate.c                         |   9 +-
 drivers/clk/ti/interface.c                    |   4 +-
 drivers/clk/ti/mux.c                          |   6 +-
 include/linux/clk/ti.h                        |   3 +
 16 files changed, 491 insertions(+), 405 deletions(-)

-- 
2.43.1

             reply	other threads:[~2024-02-13 10:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13 10:56 Tony Lindgren [this message]
2024-02-13 10:56 ` [PATCH 1/4] clk: ti: Handle possible address in the node name Tony Lindgren
2024-02-22  5:11   ` Stephen Boyd
2024-09-02 14:03   ` Geert Uytterhoeven
2024-09-05  9:54     ` Geert Uytterhoeven
2024-02-13 10:56 ` [PATCH 2/4] clk: ti: Improve clksel clock bit parsing for reg property Tony Lindgren
2024-02-22  5:11   ` Stephen Boyd
2024-02-13 10:56 ` [PATCH 3/4] ARM: dts: am3: Update clksel clocks to use reg instead of ti,bit-shift Tony Lindgren
2024-02-13 10:56 ` [PATCH 4/4] ARM: dts: omap3: " Tony Lindgren
2024-02-13 23:11 ` [PATCH 0/4] Use reg instead of ti,bit-shift for clksel Andreas Kemnade
2024-02-14  5:40   ` Tony Lindgren
2024-02-29  7:06     ` Tony Lindgren
2024-03-02 19:18       ` Andreas Kemnade
2024-03-08  9:00         ` 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=20240213105730.5287-1-tony@atomide.com \
    --to=tony@atomide.com \
    --cc=andreas@kemnade.info \
    --cc=bcousson@baylibre.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kristo@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@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;
as well as URLs for NNTP newsgroup(s).