mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
To: Luca Ceresoli <luca.ceresoli@bootlin.com>,
	Christian Hewitt <christianshewitt@gmail.com>
Cc: Andrzej Hajda <andrzej.hajda@intel.com>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Robert Foss <rfoss@kernel.org>,
	Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
	Jonas Karlman <jonas@kwiboo.se>,
	Jernej Skrabec <jernej.skrabec@gmail.com>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
	Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
	Detlev Casanova <detlev.casanova@collabora.com>,
	Douglas Anderson <dianders@chromium.org>,
	Andy Yan <andy.yan@rock-chips.com>,
	Sugar Zhang <sugar.zhang@rock-chips.com>,
	Heiko Stuebner <heiko@sntech.de>,
	dri-devel@lists.freedesktop.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] drm/bridge: dw-hdmi-qp: fix multi-channel audio output
Date: Wed, 18 Mar 2026 20:12:35 +0200	[thread overview]
Message-ID: <0895dfa0-9527-41b1-b991-a2bd6e0c549b@collabora.com> (raw)
In-Reply-To: <DH58MAETGDMM.2QS6VJDQ7UXIV@bootlin.com>

Hi Luca,

On 3/17/26 7:35 PM, Luca Ceresoli wrote:
> Hello Christian, Cristian, Jonas,
> 
> On Tue Mar 17, 2026 at 5:49 PM CET, Christian Hewitt wrote:
>>> On 17 Mar 2026, at 8:16 pm, Luca Ceresoli <luca.ceresoli@bootlin.com> wrote:
>>>
>>> Hello Christian,
>>>
>>> On Sat Feb 28, 2026 at 12:28 PM CET, Christian Hewitt wrote:
>>>> From: Jonas Karlman <jonas@kwiboo.se>
>>>>
>>>> Channel Allocation (PB4) and Level Shift Information (PB5) are
>>>> configured with values from PB1 and PB2 due to the wrong offset
>>>> being used. This results in missing audio channels or incorrect
>>>> speaker placement when playing multi-channel audio.
>>>>
>>>> Use the correct offset to fix multi-channel audio output.
>>>>
>>>> Fixes: fd0141d1a8a2 ("drm/bridge: synopsys: Add audio support for dw-hdmi-qp")
>>>> Reported-by: Christian Hewitt <christianshewitt@gmail.com>
>>>> Signed-off-by: Jonas Karlman <jonas@kwiboo.se>
>>>> Signed-off-by: Christian Hewitt <christianshewitt@gmail.com>
>>>> Reviewed-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
>>>
>>> While applying this patch to drm-mics-fixes, checkpatch complains:
>>>
>>>  -:14: WARNING:BAD_REPORTED_BY_LINK: Reported-by: should be immediately followed by Closes: with a URL to the report
>>>
>>> You can send v3 with the link, or just reply with the link and I'll take
>>> care of adding it to the commit message.
>>
>> Apologies, it looks like use of Reported-by was tightened since I last
>> used it, and there’s no official report anywhere I can link to (it was
>> all done in private channels) so better to just drop it from the v2 patch
>> if that’s possible? - if not I can send a v3 without it.
> 
> Thanks for the quick feedback.
> 
> I applied keeping the commit message as is. In lack of a public discussion
> I guess the 'Reported-by' is somewhat informative anyway. I read the
> checkpatch as a general suggestion, not a hard rule.
> 
> So now this patch is on drm-misc-fixes, but drm-misc-fixes and
> drm-misc-next are now conflicting because of other changes by Cristian
> Ciocaltea applied in the meanwhile to drm-misc-next, and particularly
> commit 3ea699b56d31 ("drm/bridge: dw-hdmi-qp: Rework Audio InfoFrame
> handler").
> 
> Cristian, Christian (heh), Jonas, could you please check whether the code
> on drm-misc-next has or not the bug that is fixed here? And if it still
> has, send a fix based on current drm-misc-next?

The conflicting commit in drm-misc-next (i.e. 3ea699b56d31) implicitly resolves
this audio related issue as well, hence there is no need for any further action.

Regards,
Cristian

  reply	other threads:[~2026-03-18 18:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-28 11:28 Christian Hewitt
2026-03-17 16:16 ` Luca Ceresoli
2026-03-17 16:49   ` Christian Hewitt
2026-03-17 17:35     ` Luca Ceresoli
2026-03-18 18:12       ` Cristian Ciocaltea [this message]
2026-03-18 21:52         ` Luca Ceresoli
2026-03-17 17:29 ` Luca Ceresoli

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=0895dfa0-9527-41b1-b991-a2bd6e0c549b@collabora.com \
    --to=cristian.ciocaltea@collabora.com \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=airlied@gmail.com \
    --cc=andrzej.hajda@intel.com \
    --cc=andy.yan@rock-chips.com \
    --cc=christianshewitt@gmail.com \
    --cc=detlev.casanova@collabora.com \
    --cc=dianders@chromium.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=heiko@sntech.de \
    --cc=jernej.skrabec@gmail.com \
    --cc=jonas@kwiboo.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=luca.ceresoli@bootlin.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=rfoss@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=sugar.zhang@rock-chips.com \
    --cc=tzimmermann@suse.de \
    /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®