Instead of hardcoding the input name to the driver name
('gpio-keys-polled'), allow the passing a name via platform data
('name' field was already present), but default to old behaviour
in case of NULL.
Even though the general tendency is moving from pdata structs,
towards oftree/acpi/fwnode, pdat
Dmitry Torokhov wrote:
sorry for the late reply - lost your mail by broken filter :(
(just picked it out now of the archive ...)
> > Instead of hardcoding the input name to the driver name
('gpio-keys-polled'),
> > allow the passing a name via platform data ('name' field was already
present),
>
Instead of hardcoding the input name to the driver name
('gpio-keys-polled'), allow the passing a name via platform data
('name' field was already present), but default to old behaviour
in case of NULL.
Signed-off-by: Enrico Weigelt, metux IT consult
---
drivers/input/keyboard/gpio_keys_polled.c
Hi Enrico,
On Thu, Feb 07, 2019 at 06:05:31PM +0100, Enrico Weigelt, metux IT consult
wrote:
> Instead of hardcoding the input name to the driver name ('gpio-keys-polled'),
> allow the passing a name via platform data ('name' field was already present),
> but default to old behaviour in case of N
Instead of hardcoding the input name to the driver name ('gpio-keys-polled'),
allow the passing a name via platform data ('name' field was already present),
but default to old behaviour in case of NULL.
Signed-off-by: Enrico Weigelt, metux IT consult
---
drivers/input/keyboard/gpio_keys_polled.c
Instead of hardcoding the input name to the driver name ('gpio-keys-polled'),
allow the passing a name via platform data ('name' field was already present),
but default to old behaviour in case of NULL.
Signed-off-by: Enrico Weigelt, metux IT consult
---
drivers/input/keyboard/gpio_keys_polled.c
6 matches
Mail list logo