From: "Rob Herring (Arm)" <robh@kernel.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Kevin Hilman <khilman@kernel.org>, Andrew Lunn <andrew@lunn.ch>,
Gregory Clement <gregory.clement@bootlin.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Nishanth Menon <nm@ti.com>, Stephen Boyd <sboyd@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/6] cpufreq: Enable COMPILE_TEST on Arm drivers
Date: Tue, 06 Aug 2024 07:58:21 -0600 [thread overview]
Message-ID: <20240806-dt-api-cleanups-v1-0-459e2c840e7d@kernel.org> (raw)
This series enables building CPUFreq Arm based drivers on multiple
architectures when COMPILE_TEST is enabled.
The drivers for x86 and powerpc appear to be dependent on the
respective arch code, so those can't be similarly enabled for
COMPILE_TEST.
I've built this on arm32, arm64, powerpc, and x86 allmodconfig. It's
been built by 0-day and I fixed a couple of issues from that. I imagine
a few more might crop up when this is added to linux-next.
Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
---
Rob Herring (Arm) (6):
cpufreq: qcom: Add explicit io.h include for readl/writel_relaxed
cpufreq: omap: Drop asm includes
cpufreq: armada-8k: Avoid excessive stack usage
opp: ti: Drop unnecessary of_match_ptr()
cpufreq: Enable COMPILE_TEST on Arm drivers
cpufreq: Drop CONFIG_ARM and CONFIG_ARM64 dependency on Arm drivers
drivers/cpufreq/Kconfig | 2 --
drivers/cpufreq/Kconfig.arm | 50 ++++++++++++++++++++++---------------
drivers/cpufreq/armada-8k-cpufreq.c | 2 +-
drivers/cpufreq/omap-cpufreq.c | 3 ---
drivers/cpufreq/qcom-cpufreq-hw.c | 1 +
drivers/opp/ti-opp-supply.c | 2 +-
6 files changed, 33 insertions(+), 27 deletions(-)
---
base-commit: 8400291e289ee6b2bf9779ff1c83a291501f017b
change-id: 20240805-dt-api-cleanups-d63eb4f53423
Best regards,
--
Rob Herring (Arm) <robh@kernel.org>
next reply other threads:[~2024-08-06 13:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-06 13:58 Rob Herring (Arm) [this message]
2024-08-06 13:58 ` [PATCH 1/6] cpufreq: qcom: Add explicit io.h include for readl/writel_relaxed Rob Herring (Arm)
2024-08-06 13:58 ` [PATCH 2/6] cpufreq: omap: Drop asm includes Rob Herring (Arm)
2024-08-06 16:00 ` Kevin Hilman
2024-08-08 10:46 ` Dhruva Gole
2024-08-06 13:58 ` [PATCH 3/6] cpufreq: armada-8k: Avoid excessive stack usage Rob Herring (Arm)
2024-08-06 13:58 ` [PATCH 4/6] opp: ti: Drop unnecessary of_match_ptr() Rob Herring (Arm)
2024-08-08 10:48 ` Dhruva Gole
2024-08-06 13:58 ` [PATCH 5/6] cpufreq: Enable COMPILE_TEST on Arm drivers Rob Herring (Arm)
2024-08-06 13:58 ` [PATCH 6/6] cpufreq: Drop CONFIG_ARM and CONFIG_ARM64 dependency " Rob Herring (Arm)
2024-08-08 3:29 ` [PATCH 0/6] cpufreq: Enable COMPILE_TEST " Viresh Kumar
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=20240806-dt-api-cleanups-v1-0-459e2c840e7d@kernel.org \
--to=robh@kernel.org \
--cc=andrew@lunn.ch \
--cc=gregory.clement@bootlin.com \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=rafael@kernel.org \
--cc=sboyd@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=viresh.kumar@linaro.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