From: Thomas Zimmermann <tzimmermann@suse.de>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: airlied@linux.ie, maarten.lankhorst@linux.intel.com,
mripard@kernel.org, virtualization@lists.linux-foundation.org,
noralf@tronnes.org, dri-devel@lists.freedesktop.org,
daniel@ffwll.ch, alexander.deucher@amd.com,
spice-devel@lists.freedesktop.org, sam@ravnborg.org,
emil.velikov@collabora.com
Subject: Re: [PATCH 2/6] drm: Add drm_simple_encoder_{init,create}()
Date: Fri, 7 Feb 2020 11:50:24 +0100 [thread overview]
Message-ID: <cd78b79f-ff4e-9c8e-4d87-ce717a717559@suse.de> (raw)
In-Reply-To: <20200207103333.rxebukm4hukavlq5@sirius.home.kraxel.org>
[-- Attachment #1.1.1: Type: text/plain, Size: 1780 bytes --]
Hi Gerd
Am 07.02.20 um 11:33 schrieb Gerd Hoffmann:
>> +static const struct drm_encoder_funcs drm_simple_encoder_funcs_cleanup = {
>> + .destroy = drm_encoder_cleanup,
>> +};
>> +
>> +/**
>> + * drm_simple_encoder_init - Init a preallocated encoder
>> + * @dev: drm device
>> + * @funcs: callbacks for this encoder
>> + * @encoder_type: user visible type of the encoder
>> + * @name: printf style format string for the encoder name, or NULL
>> + * for default name
>> + *
>> + * Initialises a preallocated encoder that has no further functionality. The
>> + * encoder will be released automatically.
>> + *
>> + * Returns:
>> + * Zero on success, error code on failure.
>> + */
>> +int drm_simple_encoder_init(struct drm_device *dev,
>> + struct drm_encoder *encoder,
>> + int encoder_type, const char *name, ...)
>
> How about using
>
> #define drm_simple_encoder_init(dev, type, name, ...) \
> drm_encoder_init(dev, drm_simple_encoder_funcs_cleanup, type, name, __VA_ARGS__)
>
> instead ?
I'd prefer a function call for aesthetic reasons and for not having to
export the drm_simple_encoder_funcs_cleanup. drm_simple_encoder_create()
is also a function and probably cannot be turned into a macro. So having
a function for drm_simple_encoder_init seems consequent.
I guess you want to save a few lines in the implementation of
drm_simple_encoder_init() (?) If so, I'd rather try to share more
internal code among the various init and create functions.
Best regards
Thomas
>
> cheers,
> Gerd
>
--
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.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 183 bytes --]
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2020-02-07 10:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 8:41 [PATCH 0/6] drm: Provide a simple encoder Thomas Zimmermann
2020-02-07 8:41 ` [PATCH 1/6] drm: Move initialization of encoder into an internal function Thomas Zimmermann
2020-02-07 8:41 ` [PATCH 2/6] drm: Add drm_simple_encoder_{init,create}() Thomas Zimmermann
2020-02-07 10:33 ` Gerd Hoffmann
2020-02-07 10:50 ` Thomas Zimmermann [this message]
2020-02-07 12:31 ` Gerd Hoffmann
2020-02-07 13:37 ` Daniel Vetter
2020-02-07 14:00 ` Ville Syrjälä
2020-02-07 14:02 ` Thomas Zimmermann
2020-02-07 16:26 ` Daniel Vetter
2020-02-07 14:36 ` Noralf Trønnes
2020-02-07 16:25 ` Daniel Vetter
2020-02-10 10:28 ` kbuild test robot
2020-02-07 8:41 ` [PATCH 3/6] drm/ast: Use simple encoder Thomas Zimmermann
2020-02-07 8:41 ` [PATCH 4/6] drm/mgag200: " Thomas Zimmermann
2020-02-07 8:41 ` [PATCH 5/6] drm/qxl: " Thomas Zimmermann
2020-02-10 9:08 ` kbuild test robot
2020-02-07 8:41 ` [PATCH 6/6] drm/simple-pipe: " 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=cd78b79f-ff4e-9c8e-4d87-ce717a717559@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.velikov@collabora.com \
--cc=kraxel@redhat.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=noralf@tronnes.org \
--cc=sam@ravnborg.org \
--cc=spice-devel@lists.freedesktop.org \
--cc=virtualization@lists.linux-foundation.org \
/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