[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <23e80ead-1b52-4db8-af61-44f622458f97@kernel.org>
Date: Mon, 8 Jul 2024 09:33:45 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Liu Ying <victor.liu@....com>, dri-devel@...ts.freedesktop.org,
imx@...ts.linux.dev, linux-arm-kernel@...ts.infradead.org,
kernel@...gutronix.de, devicetree@...r.kernel.org
Cc: LKML <linux-kernel@...r.kernel.org>, Conor Dooley <conor+dt@...nel.org>,
Daniel Vetter <daniel@...ll.ch>, David Airlie <airlied@...il.com>,
Fabio Estevam <festevam@...il.com>, Krzysztof Kozlowski
<krzk+dt@...nel.org>, Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>, Philipp Zabel <p.zabel@...gutronix.de>,
Rob Herring <robh@...nel.org>, Sascha Hauer <s.hauer@...gutronix.de>,
Shawn Guo <shawnguo@...nel.org>, Thomas Gleixner <tglx@...utronix.de>,
Thomas Zimmermann <tzimmermann@...e.de>
Subject: Re: [09/10] drm/imx: Add i.MX8qxp Display Controller KMS
On 08/07/2024 09:09, Markus Elfring wrote:
>>> Under which circumstances would you become interested to apply a statement
>>> like “guard(spinlock_irqsave)(&crtc->dev->event_lock);”?
>>
>> I just follow the kerneldoc of drm_crtc_send_vblank_event() to
>> hold event lock like many other drivers do.
>
> Please take another look at software design possibilities to benefit more
> from further applications of scope-based resource management.
<form letter>
Feel free to ignore all comments from Markus, regardless whether the
suggestion is reasonable or not. This person is banned from LKML and
several maintainers ignore Markus' feedback, because it is just a waste
of time.
</form letter>
Best regards,
Krzysztof
Powered by blists - more mailing lists