From: Rob Herring <robh@kernel.org>
To: Andrew Lunn <andrew@lunn.ch>,
Gregory Clement <gregory.clement@bootlin.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org
Subject: [PATCH 0/3] clk: Fix/cleanup mvebu CPU DT node accesses
Date: Mon, 27 Mar 2023 13:43:17 -0500 [thread overview]
Message-ID: <20230327-mvebu-clk-fixes-v1-0-438de1026efd@kernel.org> (raw)
This is a couple of fixes and clean-ups to use preferred CPU accessors
rather than directly parsing DT "reg" properties. It's part of a larger
effort to remove open coded parsing of "reg". The existing code is
fragile depending on the CPU architecture details and is wrong for
arm64 (though the dts files are also wrong).
Compile tested only.
Signed-off-by: Rob Herring <robh@kernel.org>
---
Rob Herring (3):
MAINTAINERS: Add Marvell mvebu clock drivers
clk: mvebu: Use of_get_cpu_hwid() to read CPU ID
clk: mvebu: Iterate over possible CPUs instead of DT CPU nodes
MAINTAINERS | 1 +
drivers/clk/mvebu/ap-cpu-clk.c | 16 ++++++++--------
drivers/clk/mvebu/clk-cpu.c | 14 +++-----------
3 files changed, 12 insertions(+), 19 deletions(-)
---
base-commit: fe15c26ee26efa11741a7b632e9f23b01aca4cc6
change-id: 20230327-mvebu-clk-fixes-f4a1365fa0b7
Best regards,
--
Rob Herring <robh@kernel.org>
next reply other threads:[~2023-03-27 18:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 18:43 Rob Herring [this message]
2023-03-27 18:43 ` [PATCH 1/3] MAINTAINERS: Add Marvell mvebu clock drivers Rob Herring
2023-03-27 21:17 ` Andrew Lunn
2023-03-27 18:43 ` [PATCH 2/3] clk: mvebu: Use of_get_cpu_hwid() to read CPU ID Rob Herring
2023-04-10 23:36 ` Stephen Boyd
2023-04-11 14:04 ` Rob Herring
2023-03-27 18:43 ` [PATCH 3/3] clk: mvebu: Iterate over possible CPUs instead of DT CPU nodes Rob Herring
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=20230327-mvebu-clk-fixes-v1-0-438de1026efd@kernel.org \
--to=robh@kernel.org \
--cc=andrew@lunn.ch \
--cc=gregory.clement@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=sebastian.hesselbarth@gmail.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