From: <Dharma.B@microchip.com>
To: <mripard@kernel.org>
Cc: <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>,
<tzimmermann@suse.de>, <airlied@gmail.com>, <simona@ffwll.ch>,
<dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 2/4] drm/bridge: microchip-lvds: migrate to atomic bridge ops
Date: Wed, 25 Jun 2025 08:26:21 +0000 [thread overview]
Message-ID: <f5f68503-9f52-4a60-8e2e-fe1164e447cb@microchip.com> (raw)
In-Reply-To: <20250625-fuzzy-expert-mackerel-6edb0a@houat>
On 25/06/25 12:24 pm, Maxime Ripard wrote:
> On Wed, Jun 25, 2025 at 10:26:10AM +0530, Dharma Balasubiramani wrote:
>> Replace legacy .enable and .disable callbacks with their atomic
>> counterparts .atomic_enable and .atomic_disable.
>>
>> Also, add turn off the serialiser inside atomic_disable().
>>
>> Signed-off-by: Dharma Balasubiramani <dharma.b@microchip.com>
>
> As a rule of thumb, if you have "Also, do X" in your commit log, you
> need a separate patch.
>
> And you need to explain why turning off the serialiser inside
> atomic_disable() is needed. It might make sense to you, it's not really
> obvious to me from that patch, and it will definitely not be to someone
> trying to identify fixes and doing backports.
I initially introduced the turning off the serialiser to avoid having an
empty disable() hook. Now that you've clarified it's perfectly fine to
sleep in these contexts, I no longer see the need for the split. I'll
drop both atomic_pre_enable(), atomic_post_disable() and turning off the
serialiser as well and just keep just atomic_enable() and atomic_disable().
Thanks.
>
> Maxime
--
With Best Regards,
Dharma B.
next prev parent reply other threads:[~2025-06-25 8:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 4:56 [PATCH v5 0/4] drm/bridge: microchip-lvds: clean up and fix bus formats Dharma Balasubiramani
2025-06-25 4:56 ` [PATCH v5 1/4] drm/bridge: microchip-lvds: Remove unused drm_panel and redundant port node lookup Dharma Balasubiramani
2025-06-25 6:52 ` Maxime Ripard
2025-06-25 4:56 ` [PATCH v5 2/4] drm/bridge: microchip-lvds: migrate to atomic bridge ops Dharma Balasubiramani
2025-06-25 6:54 ` Maxime Ripard
2025-06-25 8:26 ` Dharma.B [this message]
2025-06-25 4:56 ` [PATCH v5 3/4] drm/bridge: microchip-lvds: add atomic pre_enable() and post_disable() Dharma Balasubiramani
2025-06-25 6:57 ` Maxime Ripard
2025-06-25 4:56 ` [PATCH v5 4/4] drm/bridge: microchip-lvds: fix bus format mismatch with VESA displays Dharma Balasubiramani
2025-06-25 6:57 ` Maxime Ripard
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=f5f68503-9f52-4a60-8e2e-fe1164e447cb@microchip.com \
--to=dharma.b@microchip.com \
--cc=Laurent.pinchart@ideasonboard.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=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®