[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <fa0d29dc-126c-42fe-8020-3785557bdce2@collabora.com>
Date: Wed, 28 Jan 2026 14:54:58 +0200
From: Cristian Ciocaltea <cristian.ciocaltea@...labora.com>
To: Daniel Stone <daniel@...ishbar.org>
Cc: Andrzej Hajda <andrzej.hajda@...el.com>,
Neil Armstrong <neil.armstrong@...aro.org>, Robert Foss <rfoss@...nel.org>,
Laurent Pinchart <Laurent.pinchart@...asonboard.com>,
Jonas Karlman <jonas@...boo.se>, Jernej Skrabec <jernej.skrabec@...il.com>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>, Thomas Zimmermann <tzimmermann@...e.de>,
David Airlie <airlied@...il.com>, Simona Vetter <simona@...ll.ch>,
kernel@...labora.com, dri-devel@...ts.freedesktop.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/5] drm/bridge: dw-hdmi-qp: Provide HDMI Vendor Specific
InfoFrame
Hi Daniel,
On 1/28/26 2:11 PM, Daniel Stone wrote:
> Hi Cristian,
>
> On Sun, 25 Jan 2026 at 00:23, Cristian Ciocaltea
> <cristian.ciocaltea@...labora.com> wrote:
>> + /* VSI packet body */
>> + for (i = 0; i < len - 3; i += 4)
>> + dw_hdmi_qp_write_pkt(hdmi, buffer + 3, i, min(len - i - 3, 4),
>> + PKT_VSI_CONTENTS1 + i);
>
> Given that this for loop occurs in all the users (other than when len
> < 4 where it's not required), why not move it into the
> dw_hdmi_qp_write_pkt() helper itself, such that the calls for each
> infoframe could be dw_hdmi_qp_write_pkt(hdmi, buffer + 3, len,
> PKT_VSI_CONTENTS1 /* base reg, incremented by helper */)?
Yeah, initially planned to keep the helper simple and allow more flexibility in
the callbacks. Probably now it makes sense to also write the packet header via
the helper, not just the body, since this is also handled similarly in all
cases.
Thanks,
Cristian
Powered by blists - more mailing lists