[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f10ee1ce-5362-4dc9-8e61-726db9c27d64@microchip.com>
Date: Wed, 18 Jun 2025 03:50:11 +0000
From: <Dharma.B@...rochip.com>
To: <laurent.pinchart@...asonboard.com>, <asrivats@...hat.com>
CC: <dri-devel@...ts.freedesktop.org>, <Manikandan.M@...rochip.com>,
<neil.armstrong@...aro.org>, <rfoss@...nel.org>, <jonas@...boo.se>,
<jernej.skrabec@...il.com>, <maarten.lankhorst@...ux.intel.com>,
<mripard@...nel.org>, <tzimmermann@...e.de>, <airlied@...il.com>,
<simona@...ll.ch>, <linux-kernel@...r.kernel.org>
Subject: Re: bridge/microchip_lvds panel usage
Hi Laurent & Anusha,
On 18/06/25 5:06 am, Laurent Pinchart wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> On Tue, Jun 17, 2025 at 10:36:34AM -0500, Anusha Srivatsa wrote:
>> Hey folks,
>>
>> Can someone please explain why the driver looks for a panel here:
>> https://elixir.bootlin.com/linux/v6.14.11/source/drivers/gpu/drm/bridge/
>> microchip-lvds.c#L182 and doesnt use it or set it up anywhere?
>>
>> I bumped into this while working on converting of_drm_find_panel() callers and
>> the lvds->panel usage in this driver felt off. Am I missing something?
>
> That doesn't seem needed.
Currently the LVDS controller driver is hardcoded to map LVDS lanes to
the JEIDA format.
In order to support the other format "VESA", we need this to query the
panel driver and set the appropriate format accordingly.
"drm_panel_get_modes(lvds->panel, connector)"
We'll be submitting the patch upstream shortly.
>
> By the way, please use plain text when posting to kernel mailing lists.
>
> --
> Regards,
>
> Laurent Pinchart
--
With Best Regards,
Dharma B.
Powered by blists - more mailing lists