[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5bb059a0-b94c-44cd-b18f-4e2a79a6e8a3@web.de>
Date: Mon, 8 Jul 2024 09:09:46 +0200
From: Markus Elfring <Markus.Elfring@....de>
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
>> 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.
Regards,
Markus
Powered by blists - more mailing lists