From: Neil Armstrong <neil.armstrong@linaro.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Stefan Agner <stefan@agner.ch>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Sam Ravnborg <sam@ravnborg.org>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
Sasha Levin <sashal@kernel.org>,
linux-amlogic@lists.infradead.org
Subject: Re: [PATCH 5.15 247/779] drm/meson: encoder_hdmi: switch to bridge DRM_BRIDGE_ATTACH_NO_CONNECTOR
Date: Fri, 23 Sep 2022 11:30:21 +0200 [thread overview]
Message-ID: <b9aa1178-5848-70fd-2dc1-9f36d845985e@linaro.org> (raw)
In-Reply-To: <Yy154kHD7PPtj05W@kroah.com>
Hi,
On 23/09/2022 11:18, Greg Kroah-Hartman wrote:
> On Fri, Sep 23, 2022 at 11:12:02AM +0200, Neil Armstrong wrote:
>> Hi Greg,
>>
>> On 13/09/2022 13:22, Greg Kroah-Hartman wrote:
>>> On Mon, Sep 12, 2022 at 08:48:24PM +0200, Stefan Agner wrote:
>>>> On 2022-09-12 18:08, Stefan Agner wrote:
>>>>> On 2022-08-15 19:58, Greg Kroah-Hartman wrote:
>>>>>> From: Neil Armstrong <narmstrong@baylibre.com>
>>>>>>
>>>>>> [ Upstream commit 0af5e0b41110e2da872030395231ab19c45be931 ]
>>>>>>
>>>>>> This implements the necessary change to no more use the embedded
>>>>>> connector in dw-hdmi and use the dedicated bridge connector driver
>>>>>> by passing DRM_BRIDGE_ATTACH_NO_CONNECTOR to the bridge attach call.
>>>>>>
>>>>>> The necessary connector properties are added to handle the same
>>>>>> functionalities as the embedded dw-hdmi connector, i.e. the HDR
>>>>>> metadata, the CEC notifier & other flags.
>>>>>>
>>>>>> The dw-hdmi output_port is set to 1 in order to look for a connector
>>>>>> next bridge in order to get DRM_BRIDGE_ATTACH_NO_CONNECTOR working.
>>>>>
>>>>> HDMI on ODROID-N2+ was working with v5.15.60, and stopped working with
>>>>> v5.15.61. Reverting this commit (and two dependent refcount leak) to be
>>>>> the culprit. Reverting just the refcount leaks is not enough to get HDMI
>>>>> working, so I assume it is this commit.
>>>>>
>>>>> I haven't investigated much beyond that, maybe its simple a case of a
>>>>> missing kernel configuration? DRM_DISPLAY_CONNECTOR is compiled, and the
>>>>> module display_connector is loaded, so that part seemed to have worked.
>>>>>
>>>>> Any ideas welcome.
>>>>>
>>>>> FWIW, I track the issue in the HAOS tracker at
>>>>> https://github.com/home-assistant/operating-system/issues/2120.
>>>>
>>>> It seems that backporting commit 7cd70656d128 ("drm/bridge:
>>>> display-connector: implement bus fmts callbacks") fixes the problem
>>>> without reverting this commit.
>>>>
>>>> @Greg, can we backport this commit as well?
>>>
>>> sure, now queued up, thanks.
>>
>> Backport of 7cd70656d128 ("drm/bridge: display-connector: implement bus fmts callbacks") is still missing in 5.15-stable.
>
> I see it in the 5.15.68 release as commit 590b4f10e3a4.
>
> What am I missing?
Nothing, must be tired, was looking git log in the wrong path...
>
> confused,
Sorry for the noise,
Neil
>
> greg k-h
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2022-09-23 9:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220815180337.130757997@linuxfoundation.org>
[not found] ` <20220815180347.894058731@linuxfoundation.org>
[not found] ` <892a917454bd0bbfe8a4d34a5170fe50@agner.ch>
[not found] ` <685b64f60375b69c5c790286f1386be3@agner.ch>
[not found] ` <YyBoACiWvW1UnfQA@kroah.com>
2022-09-23 9:12 ` [PATCH 5.15 247/779] drm/meson: encoder_hdmi: switch to bridge DRM_BRIDGE_ATTACH_NO_CONNECTOR Neil Armstrong
2022-09-23 9:18 ` Greg Kroah-Hartman
2022-09-23 9:30 ` Neil Armstrong [this message]
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=b9aa1178-5848-70fd-2dc1-9f36d845985e@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=sam@ravnborg.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=stefan@agner.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;
as well as URLs for NNTP newsgroup(s).