From: Thomas Zimmermann <tzimmermann@suse.de>
To: Maxime Ripard <maxime@cerno.tech>, Tian Tao <tiantao6@hisilicon.com>
Cc: maarten.lankhorst@linux.intel.com, airlied@linux.ie,
daniel@ffwll.ch, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] drm: Add the new api to install irq
Date: Tue, 3 Nov 2020 11:10:27 +0100 [thread overview]
Message-ID: <f89640fb-6994-76dc-7862-a3b26b67dc24@suse.de> (raw)
In-Reply-To: <20201103095205.ywabphbc2xbop6ae@gilmour.lan>
[-- Attachment #1.1.1: Type: text/plain, Size: 2086 bytes --]
Hi
Am 03.11.20 um 10:52 schrieb Maxime Ripard:
> On Tue, Nov 03, 2020 at 10:10:41AM +0800, Tian Tao wrote:
>> Add new api devm_drm_irq_install() to register interrupts,
>> no need to call drm_irq_uninstall() when the drm module is removed.
>>
>> v2:
>> fixed the wrong parameter.
>>
>> Signed-off-by: Tian Tao <tiantao6@hisilicon.com>
>> ---
>> drivers/gpu/drm/drm_drv.c | 23 +++++++++++++++++++++++
>> include/drm/drm_drv.h | 3 ++-
>> 2 files changed, 25 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/drm_drv.c b/drivers/gpu/drm/drm_drv.c
>> index cd162d4..0fe5243 100644
>> --- a/drivers/gpu/drm/drm_drv.c
>> +++ b/drivers/gpu/drm/drm_drv.c
>> @@ -39,6 +39,7 @@
>> #include <drm/drm_color_mgmt.h>
>> #include <drm/drm_drv.h>
>> #include <drm/drm_file.h>
>> +#include <drm/drm_irq.h>
>> #include <drm/drm_managed.h>
>> #include <drm/drm_mode_object.h>
>> #include <drm/drm_print.h>
>> @@ -678,6 +679,28 @@ static int devm_drm_dev_init(struct device *parent,
>> return ret;
>> }
>>
>> +static void devm_drm_dev_irq_uninstall(void *data)
>> +{
>> + drm_irq_uninstall(data);
>> +}
>> +
>> +int devm_drm_irq_install(struct device *parent,
>> + struct drm_device *dev, int irq)
>> +{
>> + int ret;
>> +
>> + ret = drm_irq_install(dev, irq);
>> + if (ret)
>> + return ret;
>> +
>> + ret = devm_add_action(parent, devm_drm_dev_irq_uninstall, dev);
>> + if (ret)
>> + devm_drm_dev_irq_uninstall(dev);
>> +
>> + return ret;
>> +}
>> +EXPORT_SYMBOL(devm_drm_irq_install);
>> +
>
> Shouldn't we tie the IRQ to the drm device (so with drmm_add_action)
> instead of tying it to the underlying device?
If the HW device goes away, there won't be any more interrupts. So it's
similar to devm_ functions for I/O memory. Why would you use the drmm_
interface?
Best regards
Thomas
>
> Maxime
>>
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Felix Imendörffer
[-- Attachment #1.1.2: OpenPGP_0x680DC11D530B7A23.asc --]
[-- Type: application/pgp-keys, Size: 4259 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2020-11-03 10:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 2:10 Tian Tao
2020-11-03 7:56 ` Thomas Zimmermann
2020-11-03 8:57 ` tiantao (H)
2020-11-03 9:04 ` Thomas Zimmermann
2020-11-03 9:36 ` Sam Ravnborg
2020-11-03 9:52 ` Maxime Ripard
2020-11-03 10:10 ` Thomas Zimmermann [this message]
2020-11-03 10:38 ` Maxime Ripard
2020-11-03 10:55 ` Daniel Vetter
2020-11-03 11:25 ` Thomas Zimmermann
2020-11-03 11:46 ` Daniel Vetter
2020-11-03 11:25 ` Maxime Ripard
2020-11-04 9:37 ` Daniel Vetter
2020-11-03 10:23 ` Daniel Vetter
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=f89640fb-6994-76dc-7862-a3b26b67dc24@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=maxime@cerno.tech \
--cc=tiantao6@hisilicon.com \
/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®