The largest infoframe we create is the DRM (Dynamic Range Mastering)
infoframe which is 26 bytes + a 4 byte header, for a total of 30
bytes.
With HDMI_MAX_INFOFRAME_SIZE set to 29 bytes, as it is now, we
allocate too little space to pack a DRM infoframe in
write_device_infoframe(), leading to an ENOSPC return from
hdmi_infoframe_pack(), and never calling the connector's
write_infoframe() vfunc.
Instead of having HDMI_MAX_INFOFRAME_SIZE defined in two places,
replace HDMI_MAX_INFOFRAME_SIZE with HDMI_INFOFRAME_SIZE(MAX) and make
MAX 27 bytes - which is defined by the HDMI specification to be the
largest infoframe payload.
Fixes: f378b77227bc ("drm/connector: hdmi: Add Infoframes generation")
Fixes: c602e4959a0c ("drm/connector: hdmi: Create Infoframe DebugFS entries")
Signed-off-by: Derek Foreman <redacted>
---
drivers/gpu/drm/display/drm_hdmi_state_helper.c | 4 +---
drivers/gpu/drm/drm_debugfs.c | 4 +---
include/linux/hdmi.h | 9 +++++++++
3 files changed, 11 insertions(+), 6 deletions(-)
On Tue, 27 Aug 2024 11:39:04 -0500, Derek Foreman wrote:
The largest infoframe we create is the DRM (Dynamic Range Mastering)
infoframe which is 26 bytes + a 4 byte header, for a total of 30
bytes.
With HDMI_MAX_INFOFRAME_SIZE set to 29 bytes, as it is now, we
[ ... ]
Acked-by: Maxime Ripard <mripard@kernel.org>
Thanks!
Maxime
From: Jani Nikula <jani.nikula@linux.intel.com> Date: 2024-08-28 08:31:27
On Tue, 27 Aug 2024, Derek Foreman [off-list ref] wrote:
The largest infoframe we create is the DRM (Dynamic Range Mastering)
infoframe which is 26 bytes + a 4 byte header, for a total of 30
bytes.
With HDMI_MAX_INFOFRAME_SIZE set to 29 bytes, as it is now, we
allocate too little space to pack a DRM infoframe in
write_device_infoframe(), leading to an ENOSPC return from
hdmi_infoframe_pack(), and never calling the connector's
write_infoframe() vfunc.
Instead of having HDMI_MAX_INFOFRAME_SIZE defined in two places,
replace HDMI_MAX_INFOFRAME_SIZE with HDMI_INFOFRAME_SIZE(MAX) and make
MAX 27 bytes - which is defined by the HDMI specification to be the
largest infoframe payload.
Fixes: f378b77227bc ("drm/connector: hdmi: Add Infoframes generation")
Fixes: c602e4959a0c ("drm/connector: hdmi: Create Infoframe DebugFS entries")
Superfluous blank line. Can be fixed while applying.
Reviewed-by: Jani Nikula <redacted>
Gentle ping - is there anything more I need to do before this can land?
Thanks,
Derek
On 2024-08-28 03:31, Jani Nikula wrote:
On Tue, 27 Aug 2024, Derek Foreman [off-list ref] wrote:
quoted
The largest infoframe we create is the DRM (Dynamic Range Mastering)
infoframe which is 26 bytes + a 4 byte header, for a total of 30
bytes.
With HDMI_MAX_INFOFRAME_SIZE set to 29 bytes, as it is now, we
allocate too little space to pack a DRM infoframe in
write_device_infoframe(), leading to an ENOSPC return from
hdmi_infoframe_pack(), and never calling the connector's
write_infoframe() vfunc.
Instead of having HDMI_MAX_INFOFRAME_SIZE defined in two places,
replace HDMI_MAX_INFOFRAME_SIZE with HDMI_INFOFRAME_SIZE(MAX) and make
MAX 27 bytes - which is defined by the HDMI specification to be the
largest infoframe payload.
Fixes: f378b77227bc ("drm/connector: hdmi: Add Infoframes generation")
Fixes: c602e4959a0c ("drm/connector: hdmi: Create Infoframe DebugFS entries")
Superfluous blank line. Can be fixed while applying.
Reviewed-by: Jani Nikula <redacted>
From: Jani Nikula <jani.nikula@linux.intel.com> Date: 2024-09-17 08:12:55
On Mon, 16 Sep 2024, Derek Foreman [off-list ref] wrote:
Gentle ping - is there anything more I need to do before this can land?
I don't think so. FWIW, I bounced this to intel-gfx and got passing CI
results too.
Cc: drm-misc maintainers. Just wondering where to merge this. It's a fix
to commits in v6.11. Are you still planning on a drm-misc-next-fixes
pull request for v6.12-rc1? That would be the quickest way to get this
upstream.
BR,
Jani.
Thanks,
Derek
On 2024-08-28 03:31, Jani Nikula wrote:
quoted
On Tue, 27 Aug 2024, Derek Foreman [off-list ref] wrote:
quoted
The largest infoframe we create is the DRM (Dynamic Range Mastering)
infoframe which is 26 bytes + a 4 byte header, for a total of 30
bytes.
With HDMI_MAX_INFOFRAME_SIZE set to 29 bytes, as it is now, we
allocate too little space to pack a DRM infoframe in
write_device_infoframe(), leading to an ENOSPC return from
hdmi_infoframe_pack(), and never calling the connector's
write_infoframe() vfunc.
Instead of having HDMI_MAX_INFOFRAME_SIZE defined in two places,
replace HDMI_MAX_INFOFRAME_SIZE with HDMI_INFOFRAME_SIZE(MAX) and make
MAX 27 bytes - which is defined by the HDMI specification to be the
largest infoframe payload.
Fixes: f378b77227bc ("drm/connector: hdmi: Add Infoframes generation")
Fixes: c602e4959a0c ("drm/connector: hdmi: Create Infoframe DebugFS entries")
Superfluous blank line. Can be fixed while applying.
Reviewed-by: Jani Nikula <redacted>
From: Maxime Ripard <mripard@kernel.org> Date: 2024-09-24 14:13:14
On Tue, 27 Aug 2024 11:39:04 -0500, Derek Foreman wrote:
The largest infoframe we create is the DRM (Dynamic Range Mastering)
infoframe which is 26 bytes + a 4 byte header, for a total of 30
bytes.
With HDMI_MAX_INFOFRAME_SIZE set to 29 bytes, as it is now, we
allocate too little space to pack a DRM infoframe in
write_device_infoframe(), leading to an ENOSPC return from
hdmi_infoframe_pack(), and never calling the connector's
write_infoframe() vfunc.
[...]
Applied to misc/kernel.git (drm-misc-fixes).
Thanks!
Maxime
On Tue, Sep 24, 2024 at 04:13:08PM GMT, Maxime Ripard wrote:
On Tue, 27 Aug 2024 11:39:04 -0500, Derek Foreman wrote:
quoted
The largest infoframe we create is the DRM (Dynamic Range Mastering)
infoframe which is 26 bytes + a 4 byte header, for a total of 30
bytes.
With HDMI_MAX_INFOFRAME_SIZE set to 29 bytes, as it is now, we
allocate too little space to pack a DRM infoframe in
write_device_infoframe(), leading to an ENOSPC return from
hdmi_infoframe_pack(), and never calling the connector's
write_infoframe() vfunc.
[...]
Applied to misc/kernel.git (drm-misc-fixes).
With an empty line between Fixes and the rest of the tags :-(