mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <Dharma.B@microchip.com>
To: <laurent.pinchart@ideasonboard.com>
Cc: <Manikandan.M@microchip.com>, <andrzej.hajda@intel.com>,
	<neil.armstrong@linaro.org>, <rfoss@kernel.org>,
	<jonas@kwiboo.se>, <jernej.skrabec@gmail.com>,
	<maarten.lankhorst@linux.intel.com>, <mripard@kernel.org>,
	<tzimmermann@suse.de>, <airlied@gmail.com>, <simona@ffwll.ch>,
	<dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 1/3] drm/bridge: microchip-lvds: drop unused drm_panel
Date: Tue, 24 Jun 2025 10:53:07 +0000	[thread overview]
Message-ID: <9f7fe1a6-77bd-4dba-9d83-2a9d0625baec@microchip.com> (raw)
In-Reply-To: <20250624105034.GI15951@pendragon.ideasonboard.com>

On 24/06/25 4:20 pm, Laurent Pinchart wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> On Tue, Jun 24, 2025 at 10:46:26AM +0000, Dharma.B@microchip.com wrote:
>> On 24/06/25 4:12 pm, Laurent Pinchart wrote:
>>> On Tue, Jun 24, 2025 at 02:54:14PM +0530, Dharma Balasubiramani wrote:
>>>> Drop the drm_panel field of the mchp_lvds struct as it is unused.
>>>>
>>>> Signed-off-by: Dharma Balasubiramani <dharma.b@microchip.com>
>>>> ---
>>>>    drivers/gpu/drm/bridge/microchip-lvds.c | 7 -------
>>>>    1 file changed, 7 deletions(-)
>>>>
>>>> diff --git a/drivers/gpu/drm/bridge/microchip-lvds.c b/drivers/gpu/drm/bridge/microchip-lvds.c
>>>> index 9f4ff82bc6b4..42751124b868 100644
>>>> --- a/drivers/gpu/drm/bridge/microchip-lvds.c
>>>> +++ b/drivers/gpu/drm/bridge/microchip-lvds.c
>>>> @@ -23,7 +23,6 @@
>>>>    #include <drm/drm_atomic_helper.h>
>>>>    #include <drm/drm_bridge.h>
>>>>    #include <drm/drm_of.h>
>>>> -#include <drm/drm_panel.h>
>>>>    #include <drm/drm_print.h>
>>>>    #include <drm/drm_probe_helper.h>
>>>>    #include <drm/drm_simple_kms_helper.h>
>>>> @@ -56,7 +55,6 @@ struct mchp_lvds {
>>>>         struct device *dev;
>>>>         void __iomem *regs;
>>>>         struct clk *pclk;
>>>> -     struct drm_panel *panel;
>>>>         struct drm_bridge bridge;
>>>>         struct drm_bridge *panel_bridge;
>>>>    };
>>>> @@ -179,13 +177,8 @@ static int mchp_lvds_probe(struct platform_device *pdev)
>>>>                         "can't find port point, please init lvds panel port!\n");
>>>>                 return -ENODEV;
>>>>         }
>>>
>>> The above code seems unneeded now, I think you can drop it too.
>>
>> Yes, I considered removing it as well. However, I was wondering if it
>> might still be valuable to return early when the endpoint isn't found,
>> to clearly indicate that the panel port is missing.
> 
> That error is covered by the devm_drm_of_get_bridge() call below, so I
> think you can drop the code above.

Sure, I will drop the device node "port" as well.

> 
>>>> -
>>>> -     lvds->panel = of_drm_find_panel(port);
>>>>         of_node_put(port);
>>>>
>>>> -     if (IS_ERR(lvds->panel))
>>>> -             return -EPROBE_DEFER;
>>>> -
>>>>         lvds->panel_bridge = devm_drm_of_get_bridge(dev, dev->of_node, 1, 0);
>>>>
>>>>         if (IS_ERR(lvds->panel_bridge))
> 
> --
> Regards,
> 
> Laurent Pinchart


-- 
With Best Regards,
Dharma B.

  reply	other threads:[~2025-06-24 10:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-24  9:24 [PATCH v4 0/3] drm/bridge: microchip-lvds: clean up and fix bus formats Dharma Balasubiramani
2025-06-24  9:24 ` [PATCH v4 1/3] drm/bridge: microchip-lvds: drop unused drm_panel Dharma Balasubiramani
2025-06-24 10:42   ` Laurent Pinchart
2025-06-24 10:46     ` Dharma.B
2025-06-24 10:50       ` Laurent Pinchart
2025-06-24 10:53         ` Dharma.B [this message]
2025-06-24  9:24 ` [PATCH v4 2/3] drm/bridge: microchip-lvds: switch to use atomic variants Dharma Balasubiramani
2025-06-24 11:02   ` Maxime Ripard
2025-06-25  3:42     ` Dharma.B
2025-06-24  9:24 ` [PATCH v4 3/3] drm/bridge: microchip-lvds: fix bus format mismatch with VESA displays Dharma Balasubiramani

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=9f7fe1a6-77bd-4dba-9d83-2a9d0625baec@microchip.com \
    --to=dharma.b@microchip.com \
    --cc=Manikandan.M@microchip.com \
    --cc=airlied@gmail.com \
    --cc=andrzej.hajda@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jernej.skrabec@gmail.com \
    --cc=jonas@kwiboo.se \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=rfoss@kernel.org \
    --cc=simona@ffwll.ch \
    --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®