From: Danilo Krummrich <dakr@kernel.org>
To: Dave Airlie <airlied@gmail.com>
Cc: dri-devel@lists.freedesktop.org, nouveau@lists.freedesktop.org,
Luis Chamberlain <mcgrof@kernel.org>,
Russ Weight <russ.weight@linux.dev>
Subject: Re: [PATCH] drm/nouveau: select FW caching
Date: Fri, 14 Feb 2025 14:05:31 +0100 [thread overview]
Message-ID: <Z68_m1iHYN_7a_hH@cassiopeiae> (raw)
In-Reply-To: <20250207012531.621369-1-airlied@gmail.com>
(+ Luis, Russ)
On Fri, Feb 07, 2025 at 11:25:31AM +1000, Dave Airlie wrote:
> From: Dave Airlie <airlied@redhat.com>
>
> nouveau tries to load some firmware during suspend that it loaded earlier, but with
> fw caching disabled it hangs suspend, so just rely on FW cache enabling instead of
> working around it in the driver.
>
> Fixes: 176fdcbddfd2 ("drm/nouveau/gsp/r535: add support for booting GSP-RM")
> Signed-off-by: Dave Airlie <airlied@redhat.com>
> ---
> drivers/gpu/drm/nouveau/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/nouveau/Kconfig b/drivers/gpu/drm/nouveau/Kconfig
> index ce840300578d8..1050a4617fc15 100644
> --- a/drivers/gpu/drm/nouveau/Kconfig
> +++ b/drivers/gpu/drm/nouveau/Kconfig
> @@ -4,6 +4,7 @@ config DRM_NOUVEAU
> depends on DRM && PCI && MMU
> select IOMMU_API
> select FW_LOADER
> + select FW_CACHE if PM_SLEEP
CONFIG_FW_CACHE was added, as the Kconfig says, it "can prevent suspend on many
platforms".
@Luis, Russ: I assume this mostly means embedded platforms?
I wonder if we should not insist on FW_CACHE if NOUVEAU_PLATFORM_DRIVER, or even
only force FW_CACHE if DRM_NOUVEAU_GSP_DEFAULT?
next prev parent reply other threads:[~2025-02-14 13:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 1:25 [PATCH] drm/nouveau: select FW caching Dave Airlie
2025-02-14 13:05 ` Danilo Krummrich [this message]
2025-02-14 13:10 ` Danilo Krummrich
2025-02-18 14:28 ` Luis Chamberlain
2025-02-18 17:24 ` Danilo Krummrich
2025-02-18 21:39 ` Luis Chamberlain
2025-02-19 1:52 ` Dave Airlie
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=Z68_m1iHYN_7a_hH@cassiopeiae \
--to=dakr@kernel.org \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=mcgrof@kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=russ.weight@linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.