[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <74a45dff-a0ea-9d05-36e4-e5d6822dfcec@loongson.cn>
Date: Wed, 21 Jun 2023 22:03:14 +0800
From: Sui Jingfeng <suijingfeng@...ngson.cn>
To: Lucas Stach <l.stach@...gutronix.de>,
Sui Jingfeng <18949883232@....com>,
Russell King <linux+etnaviv@...linux.org.uk>,
Christian Gmeiner <christian.gmeiner@...il.com>,
David Airlie <airlied@...il.com>,
Daniel Vetter <daniel@...ll.ch>
Cc: Bjorn Helgaas <bhelgaas@...gle.com>,
Philipp Zabel <p.zabel@...gutronix.de>,
linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org,
etnaviv@...ts.freedesktop.org
Subject: Re: [PATCH v10 03/11] drm/etnaviv: Add dedicated functions to create
and destroy platform device
Hi,
On 2023/6/21 18:23, Lucas Stach wrote:
> That's right, but all you do with those indirections through the
> parameter list is move which of the functions is non-pure, in your case
> it's etnaviv_init/etnaviv_exit,
But there is a difference, etnaviv_init() and etnaviv_exit() is
impossible to be shared
there are only get called once when the module is loaded.
They can never be reused anymore, except here.
And etnaviv_init() and etnaviv_exit() don't have a choice.
But for etnaviv_create_platform_device() function,
there is a possibility to be reused in the future.
> with the indirection dropped it's
> etnaviv_create_platform_device/etnaviv_destroy_platform_device.
--
Jingfeng
Powered by blists - more mailing lists