diff options
author | Uwe Kleine-König <u.kleine-koenig@pengutronix.de> | 2023-11-05 00:15:04 +0300 |
---|---|---|
committer | Sebastian Reichel <sebastian.reichel@collabora.com> | 2023-11-16 01:15:38 +0300 |
commit | 12389c657b623da34ba9b30306e13919d0b42f3a (patch) | |
tree | 1571366ce452185f08f20409e48f303b6226d031 /crypto/des_generic.c | |
parent | 099806de68b75a0fe114376b1ee162fdff572ecc (diff) | |
download | linux-12389c657b623da34ba9b30306e13919d0b42f3a.tar.xz |
power: reset: at91-reset: Stop using module_platform_driver_probe()
On today's platforms the benefit of platform_driver_probe() isn't that
relevant any more. It allows to drop some code after booting (or module
loading) for .probe() and discard the .remove() function completely if
the driver is built-in. This typically saves a few 100k.
The downside of platform_driver_probe() is that the driver cannot be
bound and unbound at runtime which is ancient and so slightly
complicates testing. There are also thoughts to deprecate
platform_driver_probe() because it adds some complexity in the driver
core for little gain. Also many drivers don't use it correctly. This
driver for example misses to mark the driver struct with __ref which is
needed to suppress a (W=1) modpost warning.
Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Reviewed-by: Claudiu Beznea <claudiu.beznea@tuxon.dev>
Link: https://lore.kernel.org/r/20231104211501.3676352-18-u.kleine-koenig@pengutronix.de
Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com>
Diffstat (limited to 'crypto/des_generic.c')
0 files changed, 0 insertions, 0 deletions