From: Steven Price <steven.price@arm.com>
To: Arnd Bergmann <arnd@kernel.org>, Rob Herring <robh@kernel.org>,
Tomeu Vizoso <tomeu.vizoso@collabora.com>
Cc: "Arnd Bergmann" <arnd@arndb.de>,
"Alyssa Rosenzweig" <alyssa.rosenzweig@collabora.com>,
"David Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Adrián Larumbe" <adrian.larumbe@collabora.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
"Robin Murphy" <robin.murphy@arm.com>
Subject: Re: [PATCH] drm/panfrost: fix GENERIC_ATOMIC64 dependency
Date: Wed, 18 Jan 2023 11:09:14 +0000 [thread overview]
Message-ID: <18260f9c-2e2e-1210-7203-ac3b79f7da2a@arm.com> (raw)
In-Reply-To: <20230117164456.1591901-1-arnd@kernel.org>
On 17/01/2023 16:44, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> On ARMv5 and earlier, a randconfig build can still run into
>
> WARNING: unmet direct dependencies detected for IOMMU_IO_PGTABLE_LPAE
> Depends on [n]: IOMMU_SUPPORT [=y] && (ARM [=y] || ARM64 || COMPILE_TEST [=y]) && !GENERIC_ATOMIC64 [=y]
> Selected by [y]:
> - DRM_PANFROST [=y] && HAS_IOMEM [=y] && DRM [=y] && (ARM [=y] || ARM64 || COMPILE_TEST [=y] && !GENERIC_ATOMIC64 [=y]) && MMU [=y]
>
> Rework the dependencies to always require a working cmpxchg64.
>
> Fixes: db594ba3fcf9 ("drm/panfrost: depend on !GENERIC_ATOMIC64 when using COMPILE_TEST")
Looking at db594ba3fcf9 - it states:
> Since panfrost has a 'select' on IOMMU_IO_PGTABLE_LPAE we must depend on
> the same set of flags. Otherwise IOMMU_IO_PGTABLE_LPAE will be forced on
> even though it cannot build (no support for cmpxchg64).
And at the time the dependencies on IOMMU_IO_PGTABLE_LPAE were exactly
these.
However d286a58bc8f4 ("iommu: Tidy up io-pgtable dependencies")
(currently in the iommu tree) changed the depends to split the
!GENERIC_ATOMIC64 out. So we could argue that really that's the commit
that should be blamed in the fixes line.
However there's no harm in this being backported further than it
strictly needs to be, and it's clearly better having the
!GENERIC_ATOMIC64 split out. So I'll merge this to drm-misc-fixes.
Reviewed-by: Steven Price <steven.price@arm.com>
Thanks!
Steve
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
> drivers/gpu/drm/panfrost/Kconfig | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/panfrost/Kconfig b/drivers/gpu/drm/panfrost/Kconfig
> index 079600328be1..e6403a9d66ad 100644
> --- a/drivers/gpu/drm/panfrost/Kconfig
> +++ b/drivers/gpu/drm/panfrost/Kconfig
> @@ -3,7 +3,8 @@
> config DRM_PANFROST
> tristate "Panfrost (DRM support for ARM Mali Midgard/Bifrost GPUs)"
> depends on DRM
> - depends on ARM || ARM64 || (COMPILE_TEST && !GENERIC_ATOMIC64)
> + depends on ARM || ARM64 || COMPILE_TEST
> + depends on !GENERIC_ATOMIC64 # for IOMMU_IO_PGTABLE_LPAE
> depends on MMU
> select DRM_SCHED
> select IOMMU_SUPPORT
next prev parent reply other threads:[~2023-01-18 11:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 16:44 Arnd Bergmann
2023-01-18 11:09 ` Steven Price [this message]
2023-01-18 11:19 ` Robin Murphy
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=18260f9c-2e2e-1210-7203-ac3b79f7da2a@arm.com \
--to=steven.price@arm.com \
--cc=adrian.larumbe@collabora.com \
--cc=airlied@gmail.com \
--cc=alyssa.rosenzweig@collabora.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--cc=tomeu.vizoso@collabora.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
all inboxes | Powered by JetHome®