All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: jani.nikula@linux.intel.com, joonas.lahtinen@linux.intel.com,
	tvrtko.ursulin@linux.intel.com, ville.syrjala@linux.intel.com,
	imre.deak@intel.com, tejas.upadhyay@intel.com,
	jouni.hogander@intel.com, javierm@redhat.com, airlied@gmail.com,
	daniel@ffwll.ch, lucas.demarchi@intel.com, ogabbay@kernel.org,
	thomas.hellstrom@linux.intel.com,
	intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v7 1/6] drm/client: Export drm_client_dev_unregister()
Date: Mon, 8 Apr 2024 14:07:04 +0200	[thread overview]
Message-ID: <67100444-2ea0-42c2-a6ba-d1444ded5c3f@suse.de> (raw)
In-Reply-To: <ZeszikpTbZuYTav8@intel.com>

Hi

Am 08.03.24 um 16:49 schrieb Rodrigo Vivi:
> On Fri, Mar 01, 2024 at 02:42:54PM +0100, Thomas Zimmermann wrote:
>> Export drm_client_dev_unregister() for use by the i915 driver. The
>> driver does not use drm_dev_unregister(),
> Perhaps we should make i915 to call for the drm_dev_unregister since it calls
> for drm_dev_register?

Not that I disagree, but this appears to be a separate change unrelated 
to fbdev support.

Best regards
Thomas

>
>> so it has to clean up the
>> in-kernel DRM clients by itself.
>>
>> Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
>> ---
>>   drivers/gpu/drm/drm_client.c | 13 +++++++++++++
>>   1 file changed, 13 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/drm_client.c b/drivers/gpu/drm/drm_client.c
>> index 9403b3f576f7b..3d4f8b77d0789 100644
>> --- a/drivers/gpu/drm/drm_client.c
>> +++ b/drivers/gpu/drm/drm_client.c
>> @@ -172,6 +172,18 @@ void drm_client_release(struct drm_client_dev *client)
>>   }
>>   EXPORT_SYMBOL(drm_client_release);
>>   
>> +/**
>> + * drm_client_dev_unregister - Unregister clients
>> + * @dev: DRM device
>> + *
>> + * This function releases all clients by calling each client's
>> + * &drm_client_funcs.unregister callback. The callback function
>> + * is responsibe for releaseing all resources including the client
>> + * itself.
>> + *
>> + * The helper drm_dev_unregister() calls this function. Drivers
>> + * that use it don't need to call this function themselves.
>> + */
>>   void drm_client_dev_unregister(struct drm_device *dev)
>>   {
>>   	struct drm_client_dev *client, *tmp;
>> @@ -191,6 +203,7 @@ void drm_client_dev_unregister(struct drm_device *dev)
>>   	}
>>   	mutex_unlock(&dev->clientlist_mutex);
>>   }
>> +EXPORT_SYMBOL(drm_client_dev_unregister);
>>   
>>   /**
>>    * drm_client_dev_hotplug - Send hotplug event to clients
>> -- 
>> 2.43.2
>>

-- 
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nuernberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nuernberg)


  reply	other threads:[~2024-04-08 12:07 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-01 13:42 [PATCH v7 0/6] drm/i915: Convert fbdev to DRM client Thomas Zimmermann
2024-03-01 13:42 ` [PATCH v7 1/6] drm/client: Export drm_client_dev_unregister() Thomas Zimmermann
2024-03-08 15:49   ` Rodrigo Vivi
2024-04-08 12:07     ` Thomas Zimmermann [this message]
2024-03-01 13:42 ` [PATCH v7 2/6] drm/i915: Unregister in-kernel clients Thomas Zimmermann
2024-03-05 16:06   ` Rodrigo Vivi
2024-03-05 16:25     ` Jani Nikula
2024-03-06 15:11       ` Thomas Zimmermann
2024-03-08 15:28         ` Rodrigo Vivi
2024-03-01 13:42 ` [PATCH v7 3/6] drm/i915: Move fbdev functions Thomas Zimmermann
2024-03-01 13:42 ` [PATCH v7 4/6] drm/i915: Initialize fbdev DRM client with callback functions Thomas Zimmermann
2024-04-05  8:59   ` Hogander, Jouni
2024-03-01 13:42 ` [PATCH v7 5/6] drm/i915: Implement fbdev client callbacks Thomas Zimmermann
2024-04-05  8:31   ` Hogander, Jouni
2024-03-01 13:42 ` [PATCH v7 6/6] drm/i915: Implement fbdev emulation as in-kernel client Thomas Zimmermann
2024-04-05  8:34   ` Hogander, Jouni
2024-04-05  8:59     ` Thomas Zimmermann
2024-04-05  9:04       ` Hogander, Jouni
2024-04-08  7:41         ` Thomas Zimmermann
2024-04-08 12:27     ` Thomas Zimmermann
2024-03-01 13:49 ` ✓ CI.Patch_applied: success for drm/i915: Convert fbdev to DRM client Patchwork
2024-03-01 13:50 ` ✓ CI.checkpatch: " Patchwork
2024-03-01 13:51 ` ✓ CI.KUnit: " Patchwork
2024-03-01 14:02 ` ✓ CI.Build: " Patchwork
2024-03-01 14:03 ` ✓ CI.Hooks: " Patchwork
2024-03-01 14:04 ` ✗ CI.checksparse: warning " Patchwork
2024-03-01 14:22 ` ✓ CI.BAT: success " Patchwork
2024-03-01 17:27 ` ✗ Fi.CI.SPARSE: warning for drm/i915: Convert fbdev to DRM client (rev7) Patchwork
2024-03-01 17:42 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-03-06 16:42   ` Thomas Zimmermann

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=67100444-2ea0-42c2-a6ba-d1444ded5c3f@suse.de \
    --to=tzimmermann@suse.de \
    --cc=airlied@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=imre.deak@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=javierm@redhat.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=jouni.hogander@intel.com \
    --cc=lucas.demarchi@intel.com \
    --cc=ogabbay@kernel.org \
    --cc=rodrigo.vivi@intel.com \
    --cc=tejas.upadhyay@intel.com \
    --cc=thomas.hellstrom@linux.intel.com \
    --cc=tvrtko.ursulin@linux.intel.com \
    --cc=ville.syrjala@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.