dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Maxime Ripard" <mripard@kernel.org>
To: "Maíra Canal" <mcanal@igalia.com>
Cc: dri-devel@lists.freedesktop.org, kernel-dev@igalia.com,
	"Dave Stevenson" <dave.stevenson@raspberrypi.com>,
	"David Airlie" <airlied@gmail.com>,
	"Maxime Ripard" <mripard@kernel.org>,
	"Raspberry Pi Kernel Maintenance" <kernel-list@raspberrypi.com>,
	"Simona Vetter" <simona@ffwll.ch>
Subject: Re: [PATCH 1/2] drm/vc4: hdmi: Move packet RAM enable to PM runtime
Date: Mon, 12 Oct 2026 07:33:37 +0000	[thread overview]
Message-ID: <8469e2d49da7e9257f59925b69cc9d7d@kernel.org> (raw)
In-Reply-To: <20261002-vc4-hdmi-packet-ram-fix-v1-1-3d73148096c9@igalia.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 421 bytes --]

On Fri, 2 Oct 2026 10:36:43 -0300, Maíra Canal wrote:
> From: Dave Stevenson <dave.stevenson@raspberrypi.com>
> 
> Audio can be triggered by the HPD handler and start up before video has
> been restored, calling vc4_hdmi_write_infoframe() for the audio infoframe.
> vc4_hdmi_write_infoframe() needs Packet RAM to be on to store the
> 
> [ ... ]

Acked-by: Maxime Ripard <mripard@kernel.org>

Thanks!
Maxime

  reply	other threads:[~2026-10-12  7:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-02 13:36 [PATCH 0/2] drm/vc4: VC4 HDMI Runtime PM fixes for Packet RAM Maíra Canal
2026-10-02 13:36 ` [PATCH 1/2] drm/vc4: hdmi: Move packet RAM enable to PM runtime Maíra Canal
2026-10-12  7:33   ` Maxime Ripard [this message]
2026-10-02 13:36 ` [PATCH 2/2] drm/vc4: hdmi: Remove unused packet_ram_enabled flag Maíra Canal
2026-10-12 11:33 ` [PATCH 0/2] drm/vc4: VC4 HDMI Runtime PM fixes for Packet RAM Maíra Canal

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=8469e2d49da7e9257f59925b69cc9d7d@kernel.org \
    --to=mripard@kernel.org \
    --cc=airlied@gmail.com \
    --cc=dave.stevenson@raspberrypi.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kernel-dev@igalia.com \
    --cc=kernel-list@raspberrypi.com \
    --cc=mcanal@igalia.com \
    --cc=simona@ffwll.ch \
    /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