From: <Dharma.B@microchip.com>
To: <claudiu.beznea@tuxon.dev>, <Manikandan.M@microchip.com>,
<andrzej.hajda@intel.com>, <neil.armstrong@linaro.org>,
<rfoss@kernel.org>, <Laurent.pinchart@ideasonboard.com>,
<jonas@kwiboo.se>, <jernej.skrabec@gmail.com>,
<maarten.lankhorst@linux.intel.com>, <mripard@kernel.org>,
<tzimmermann@suse.de>, <airlied@gmail.com>, <daniel@ffwll.ch>,
<Hari.PrasathGE@microchip.com>
Cc: <dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] drm/bridge: microchip-lvds: Revert clk_prepare_enable() in case of failure
Date: Mon, 2 Sep 2024 08:25:36 +0000 [thread overview]
Message-ID: <b1975bac-34ac-4463-a8a6-0b510752bb7d@microchip.com> (raw)
In-Reply-To: <0dac055e-9d31-43ff-8584-57565f53e761@tuxon.dev>
Hi Claudiu,
On 02/09/24 1:48 pm, claudiu beznea wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> On 02.09.2024 07:39, Dharma.B@microchip.com wrote:
>> On 27/08/24 9:42 pm, Claudiu Beznea wrote:
>>> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>>>
>>> In case pm_runtime_get_sync() fails the clock remains enabled. Disable
>>> it to save power on this failure scenario.
>>>
>>> Fixes: 179b0769fc5f ("drm/bridge: add lvds controller support for sam9x7")
>>> Signed-off-by: Claudiu Beznea <claudiu.beznea@tuxon.dev>
>> Reviewed-and-tested-by: Dharma Balasubiramani <dharma.b@microchip.com>
>
> This tag is not valid, AFAIK. You should use 2 different tags: Reviewed-by,
> Tested-by
Okay, I don't know how these got in
linux$ git log | grep Reviewed-and-tested-by
Reviewed-and-tested-by: Jiadong Zhu <Jiadong.Zhu@amd.com>
Reviewed-and-tested-by: Jiadong Zhu <Jiadong.Zhu@amd.com>
Reviewed-and-tested-by: Raghavendra K T <raghavendra.kt@amd.com>
Reviewed-and-tested-by: K Prateek Nayak <kprateek.nayak@amd.com>
Reviewed-and-tested-by: Athira Rajeev <atrajeev@linux.vnet.ibm.com>
Reviewed-and-tested-by: Athira Rajeev <atrajeev@linux.vnet.ibm.com>
Reviewed-and-tested-by: Athira Rajeev <atrajeev@linux.vnet.ibm.com>
Reviewed-and-tested-by: Madadi Vineeth Reddy <vineethr@linux.ibm.com>
Reviewed-and-tested-by: Jan Karcher <jaka@linux.ibm.com>
Reviewed-and-tested-by: Jan Karcher <jaka@linux.ibm.com>
Reviewed-and-tested-by: Jan Karcher <jaka@linux.ibm.com>
Reviewed-and-tested-by: Jan Karcher <jaka@linux.ibm.com>
Reviewed-and-tested-by: Jan Karcher <jaka@linux.ibm.com>
Reviewed-and-tested-by: Jan Karcher <jaka@linux.ibm.com>
Reviewed-and-tested-by: Jan Karcher <jaka@linux.ibm.com>
Reviewed-and-tested-by: Jan Karcher <jaka@linux.ibm.com>
Reviewed-and-tested-by: Jan Karcher <jaka@linux.ibm.com>
Reviewed-and-tested-by: Jan Karcher <jaka@linux.ibm.com>
Reviewed-and-tested-by: Jan Karcher <jaka@linux.ibm.com>
Reviewed-and-tested-by: Chen Yu <yu.c.chen@intel.com>
Reviewed-and-tested-by: Haibo Chen <haibo.chen@nxp.com>
Reviewed-and-tested-by: Jingbo Xu <jefflexu@linux.alibaba.com>
Reviewed-and-tested-by: Xiongwei Song <xiongwei.song@windriver.com>
Reviewed-and-tested-by: Xiongwei Song <xiongwei.song@windriver.com>
Reviewed-and-tested-by: Mathieu Desnoyers
<mathieu.desnoyers@efficios.com>
Reviewed-and-tested-by: Geliang Tang <geliang@kernel.org>
Reviewed-and-tested-by: Geliang Tang <geliang@kernel.org>
Reviewed-and-tested-by: Davidlohr Bueso <dave@stgolabs.net>
Reviewed-and-tested-by: Jiadong Zhu <Jiadong.Zhu@amd.com>
Reviewed-and-tested-by: Wenjia Zhang <wenjia@linux.ibm.com>
Reviewed-and-tested-by: Wenjia Zhang <wenjia@linux.ibm.com>
:
:
:
>
>>> ---
>>> drivers/gpu/drm/bridge/microchip-lvds.c | 1 +
>>> 1 file changed, 1 insertion(+)
>>>
>>> diff --git a/drivers/gpu/drm/bridge/microchip-lvds.c b/drivers/gpu/drm/bridge/microchip-lvds.c
>>> index b8313dad6072..027292ab0197 100644
>>> --- a/drivers/gpu/drm/bridge/microchip-lvds.c
>>> +++ b/drivers/gpu/drm/bridge/microchip-lvds.c
>>> @@ -125,6 +125,7 @@ static void mchp_lvds_enable(struct drm_bridge *bridge)
>>>
>>> ret = pm_runtime_get_sync(lvds->dev);
>>> if (ret < 0) {
>>> + clk_disable_unprepare(lvds->pclk);
>>> dev_err(lvds->dev, "failed to get pm runtime: %d\n", ret);
>>> return;
>>> }
>>> --
>>> 2.39.2
>>>
>>
>>
--
With Best Regards,
Dharma B.
next prev parent reply other threads:[~2024-09-02 8:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 16:12 [PATCH 0/3] drm/bridge: microchip-lvds: Cleanups Claudiu Beznea
2024-08-27 16:12 ` [PATCH 1/3] drm/bridge: microchip-lvds: Revert clk_prepare_enable() in case of failure Claudiu Beznea
2024-09-02 4:39 ` Dharma.B
2024-09-02 8:18 ` claudiu beznea
2024-09-02 8:25 ` Dharma.B [this message]
2024-09-02 8:35 ` Dharma.B
2024-08-27 16:12 ` [PATCH 2/3] drm/bridge: microchip-lvds: Drop unused headers Claudiu Beznea
2024-08-31 8:18 ` kernel test robot
2024-09-01 7:28 ` kernel test robot
2024-08-27 16:12 ` [PATCH 3/3] drm/bridge: microchip-lvds: Use devm_platform_ioremap_resource() Claudiu Beznea
2024-09-02 4:39 ` Dharma.B
2024-09-02 8:35 ` Dharma.B
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=b1975bac-34ac-4463-a8a6-0b510752bb7d@microchip.com \
--to=dharma.b@microchip.com \
--cc=Hari.PrasathGE@microchip.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=Manikandan.M@microchip.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--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=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