From: <Ludovic.Desroches@microchip.com>
To: <dmitry.baryshkov@oss.qualcomm.com>
Cc: <neil.armstrong@linaro.org>, <jesszhan0024@gmail.com>,
<maarten.lankhorst@linux.intel.com>, <mripard@kernel.org>,
<tzimmermann@suse.de>, <airlied@gmail.com>, <simona@ffwll.ch>,
<asrivats@redhat.com>, <luca.ceresoli@bootlin.com>,
<dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>,
<stable@vger.kernel.org>
Subject: Re: [PATCH REGRESSION] drm/panel: simple: restore connector_type fallback
Date: Wed, 26 Nov 2025 07:27:17 +0000 [thread overview]
Message-ID: <3fc2574a-be4c-4273-82b5-317d822b3767@microchip.com> (raw)
In-Reply-To: <4am5nvb4ldzvvaavkdu2o36viltoxxyxwybrmj3h35wtdhfcpa@53t4zahc3y6c>
On 11/21/25 23:52, Dmitry Baryshkov wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> On Fri, Nov 21, 2025 at 02:20:48PM +0100, Ludovic Desroches wrote:
>> The switch from devm_kzalloc() + drm_panel_init() to
>> devm_drm_panel_alloc() introduced a regression.
>>
>> Several panel descriptors do not set connector_type. For those panels,
>> panel_simple_probe() used to compute a connector type (currently DPI as a
>> fallback) and pass that value to drm_panel_init(). After the conversion
>> to devm_drm_panel_alloc(), the call unconditionally used
>> desc->connector_type instead, ignoring the computed fallback and
>> potentially passing DRM_MODE_CONNECTOR_Unknown, which
>> drm_panel_bridge_add() does not allow.
>>
>> Move the connector_type validation / fallback logic before the
>> devm_drm_panel_alloc() call and pass the computed connector_type to
>> devm_drm_panel_alloc(), so panels without an explicit connector_type
>> once again get the DPI default.
>>
>> Signed-off-by: Ludovic Desroches <ludovic.desroches@microchip.com>
>> Fixes: de04bb0089a9 ("drm/panel/panel-simple: Use the new allocation in place of devm_kzalloc()")
>> ---
>> Hi,
>>
>> I am not sure whether this regression has already been reported or
>> addressed. If it has, please feel free to drop this patch.
>
> Would it be better to fix those panels instead? In the end, the panel
> usually has only one bus.
I don’t have a strong opinion on this point. I don’t know if there are
any historical reasons behind all this.
Regards,
Ludovic
>
>> ---
>> drivers/gpu/drm/panel/panel-simple.c | 86 ++++++++++++++++++------------------
>> 1 file changed, 43 insertions(+), 43 deletions(-)
>
> --
> With best wishes
> Dmitry
next prev parent reply other threads:[~2025-11-26 7:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 13:20 Ludovic Desroches
2025-11-21 15:12 ` Maxime Ripard
2025-11-21 22:52 ` Dmitry Baryshkov
2025-11-26 7:27 ` Ludovic.Desroches [this message]
2025-11-22 20:26 ` kernel test robot
2025-11-26 8:16 ` Neil Armstrong
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=3fc2574a-be4c-4273-82b5-317d822b3767@microchip.com \
--to=ludovic.desroches@microchip.com \
--cc=airlied@gmail.com \
--cc=asrivats@redhat.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jesszhan0024@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=simona@ffwll.ch \
--cc=stable@vger.kernel.org \
--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®