From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
Suzuki K Poulose <suzuki.poulose@arm.com>
Subject: Re: [PATCH] coresight: Add explicit architecture dependency
Date: Thu, 24 Oct 2019 11:37:44 -0600 [thread overview]
Message-ID: <20191024173744.GA5806@xps15> (raw)
In-Reply-To: <20191024120420.48893-1-broonie@kernel.org>
On Thu, Oct 24, 2019 at 01:04:20PM +0100, Mark Brown wrote:
> Coresight hardware is only likely to appear on Arm systems and currently
> the core code has Arm-specific barrier operations in it so can't be
> built anywhere else so add an explicit dependency saying so. This will
> make no practical difference currently due to the way subsystems are
> referenced, the subsystem is only pulled in on arm and arm64, so mainly
> serves as documentation in case someone wants to increase build
> coverage.
>
> Signed-off-by: Mark Brown <broonie@kernel.org>
> ---
> drivers/hwtracing/coresight/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/hwtracing/coresight/Kconfig b/drivers/hwtracing/coresight/Kconfig
> index 7a9f5fb08330..6ff30e25af55 100644
> --- a/drivers/hwtracing/coresight/Kconfig
> +++ b/drivers/hwtracing/coresight/Kconfig
> @@ -4,6 +4,7 @@
> #
> menuconfig CORESIGHT
> bool "CoreSight Tracing Support"
> + depends on ARM || ARM64
Very true - applied.
Thanks,
Mathieu
> depends on OF || ACPI
> select ARM_AMBA
> select PERF_EVENTS
> --
> 2.20.1
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-10-24 17:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 12:04 [PATCH] coresight: Add explicit architecture dependency Mark Brown
2019-10-24 17:37 ` Mathieu Poirier [this message]
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=20191024173744.GA5806@xps15 \
--to=mathieu.poirier@linaro.org \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=suzuki.poulose@arm.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