From: Robin Murphy <robin.murphy@arm.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: will@kernel.org, mark.rutland@arm.com, suzuki.poulose@arm.com,
bwicaksono@nvidia.com, ilkka@os.amperecomputing.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH v2 3/4] perf/arm_cspmu: Clean up ACPI dependency
Date: Mon, 3 Jul 2023 11:56:18 +0100 [thread overview]
Message-ID: <a195f4b7-283a-1929-de72-c6c5319d2203@arm.com> (raw)
In-Reply-To: <CAMuHMdU7kiGni_T1mRU7EC-8sQn8EjhND1-POc2h2V4V8Oeuqg@mail.gmail.com>
Hi Geert,
On 2023-07-03 10:21, Geert Uytterhoeven wrote:
> Hi Robin,
>
> On Mon, Jun 5, 2023 at 7:05 PM Robin Murphy <robin.murphy@arm.com> wrote:
>> Build-wise, the ACPI dependency consists of only a couple of things
>> which could probably stand being factored out into ACPI helpers anyway.
>> However for the immediate concern of working towards Devicetree support
>> here, it's easy enough to make a few tweaks to contain the affected code
>> locally, such that we can relax the Kconfig dependency.
>>
>> Reviewed-and-Tested-by: Suzuki K Poulose <suzuki.poulose@arm.com>
>> Reviewed-by: Ilkka Koskinen <ilkka@os.amperecomputing.com>
>> Signed-off-by: Robin Murphy <robin.murphy@arm.com>
>
> Thanks for your patch, which is now commit f9bd34e3753ea8f1
> ("perf/arm_cspmu: Clean up ACPI dependency") upstream.
>
>> --- a/drivers/perf/arm_cspmu/Kconfig
>> +++ b/drivers/perf/arm_cspmu/Kconfig
>> @@ -4,8 +4,7 @@
>>
>> config ARM_CORESIGHT_PMU_ARCH_SYSTEM_PMU
>> tristate "ARM Coresight Architecture PMU"
>> - depends on ARM64 && ACPI
>> - depends on ACPI_APMT || COMPILE_TEST
>> + depends on ARM64 || COMPILE_TEST
>
> From looking at the code, the "arm-cs-arch-pmu" platform device can
> be instantiated only through ACPI. So I think it is a bit premature to
> relax the dependency, and expose this question to people configuring
> an ARM64 kernel without ACPI/APMT support.
>
> Am I missing something?
As was mentioned in the original cover letter on v1, these patches were
actually the bottom half of a branch adding DT support - the DT parts
are still untested and not quite complete (there's a property I don't
need for the thing I'm looking at, but still deserves to be hooked up in
general), but it seemed worth landing these prep patches since they
impact what Besar and Ilkka are also working on in parallel.
At this point, the kconfig could indeed be "depends on (ARM64 &&
ACPI_APMT) || COMPILE_TEST". I can't recall why I didn't change that
when splitting these patches out for posting - I may have decided the
impact was negligible (i.e. even with DT support, it's still going to be
a driver most people won't care about anyway), or the visibility vs.
functional dependency aspect may have just slipped my mind entirely.
You're welcome to make that change for now if you'd like to.
(I'm not sure how soon I'll be posting the follow-up DT patches, since
I'm dependent on other people to provide testing and feedback, and
haven't heard any news yet)
Thanks,
Robin.
> Thanks!
>
>> help
>> Provides support for performance monitoring unit (PMU) devices
>> based on ARM CoreSight PMU architecture. Note that this PMU
>
> Gr{oetje,eeting}s,
>
> Geert
>
next prev parent reply other threads:[~2023-07-03 10:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 17:01 [PATCH v2 0/4] perf/arm_cspmu: Fixes and cleanups Robin Murphy
2023-06-05 17:01 ` [PATCH v2 1/4] perf/arm_cspmu: Fix event attribute type Robin Murphy
2023-06-05 17:01 ` [PATCH v2 2/4] ACPI/APMT: Don't register invalid resource Robin Murphy
2023-06-07 14:21 ` Lorenzo Pieralisi
2023-06-05 17:01 ` [PATCH v2 3/4] perf/arm_cspmu: Clean up ACPI dependency Robin Murphy
2023-07-03 9:21 ` Geert Uytterhoeven
2023-07-03 10:56 ` Robin Murphy [this message]
2023-06-05 17:01 ` [PATCH v2 4/4] perf/arm_cspmu: Decouple APMT dependency Robin Murphy
2023-06-05 20:29 ` Ilkka Koskinen
2023-06-09 11:16 ` [PATCH v2 0/4] perf/arm_cspmu: Fixes and cleanups Will Deacon
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=a195f4b7-283a-1929-de72-c6c5319d2203@arm.com \
--to=robin.murphy@arm.com \
--cc=bwicaksono@nvidia.com \
--cc=geert@linux-m68k.org \
--cc=ilkka@os.amperecomputing.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=will@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
all inboxes | Powered by JetHome®