* [PATCH 1/3] leds: cr0014114: silent no spi_device_id warning
@ 2022-09-05 15:26 Wei Yongjun
2022-09-05 15:26 ` [PATCH 2/3] leds: el15203000: " Wei Yongjun
` (2 more replies)
0 siblings, 3 replies; 5+ messages in thread
From: Wei Yongjun @ 2022-09-05 15:26 UTC (permalink / raw)
To: Pavel Machek, Oleh Kravchenko; +Cc: Wei Yongjun, linux-leds, linux-kernel
From: Wei Yongjun <weiyongjun1@huawei.com>
Add spi_device_id entries to silent following SPI warning:
SPI driver leds_cr0014114 has no spi_device_id for crane,cr0014114
Signed-off-by: Wei Yongjun <weiyongjun1@huawei.com>
---
drivers/leds/leds-cr0014114.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/drivers/leds/leds-cr0014114.c b/drivers/leds/leds-cr0014114.c
index c87686bd7c18..095455163246 100644
--- a/drivers/leds/leds-cr0014114.c
+++ b/drivers/leds/leds-cr0014114.c
@@ -281,9 +281,16 @@ static const struct of_device_id cr0014114_dt_ids[] = {
MODULE_DEVICE_TABLE(of, cr0014114_dt_ids);
+static const struct spi_device_id cr0014114_spi_ids[] = {
+ { "cr0014114" },
+ { },
+};
+MODULE_DEVICE_TABLE(spi, cr0014114_spi_ids);
+
static struct spi_driver cr0014114_driver = {
.probe = cr0014114_probe,
.remove = cr0014114_remove,
+ .id_table = cr0014114_spi_ids,
.driver = {
.name = KBUILD_MODNAME,
.of_match_table = cr0014114_dt_ids,
--
2.34.1
^ permalink raw reply related [flat|nested] 5+ messages in thread
* [PATCH 2/3] leds: el15203000: silent no spi_device_id warning
2022-09-05 15:26 [PATCH 1/3] leds: cr0014114: silent no spi_device_id warning Wei Yongjun
@ 2022-09-05 15:26 ` Wei Yongjun
2022-09-05 20:53 ` Oleh Kravchenko
2022-09-05 15:26 ` [PATCH 3/3] leds: spi-byte: " Wei Yongjun
2022-09-05 20:53 ` [PATCH 1/3] leds: cr0014114: " Oleh Kravchenko
2 siblings, 1 reply; 5+ messages in thread
From: Wei Yongjun @ 2022-09-05 15:26 UTC (permalink / raw)
To: Pavel Machek, Oleh Kravchenko; +Cc: Wei Yongjun, linux-leds, linux-kernel
From: Wei Yongjun <weiyongjun1@huawei.com>
Add spi_device_id entries to silent following SPI warning:
SPI driver leds_el15203000 has no spi_device_id for crane,el15203000
Signed-off-by: Wei Yongjun <weiyongjun1@huawei.com>
---
drivers/leds/leds-el15203000.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/drivers/leds/leds-el15203000.c b/drivers/leds/leds-el15203000.c
index 7e7b617bcd56..e24b4399176e 100644
--- a/drivers/leds/leds-el15203000.c
+++ b/drivers/leds/leds-el15203000.c
@@ -329,9 +329,16 @@ static const struct of_device_id el15203000_dt_ids[] = {
MODULE_DEVICE_TABLE(of, el15203000_dt_ids);
+static const struct spi_device_id el15203000_spi_ids[] = {
+ { "el15203000" },
+ { },
+};
+MODULE_DEVICE_TABLE(spi, el15203000_spi_ids);
+
static struct spi_driver el15203000_driver = {
.probe = el15203000_probe,
.remove = el15203000_remove,
+ .id_table = el15203000_spi_ids,
.driver = {
.name = KBUILD_MODNAME,
.of_match_table = el15203000_dt_ids,
--
2.34.1
^ permalink raw reply related [flat|nested] 5+ messages in thread
* [PATCH 3/3] leds: spi-byte: silent no spi_device_id warning
2022-09-05 15:26 [PATCH 1/3] leds: cr0014114: silent no spi_device_id warning Wei Yongjun
2022-09-05 15:26 ` [PATCH 2/3] leds: el15203000: " Wei Yongjun
@ 2022-09-05 15:26 ` Wei Yongjun
2022-09-05 20:53 ` [PATCH 1/3] leds: cr0014114: " Oleh Kravchenko
2 siblings, 0 replies; 5+ messages in thread
From: Wei Yongjun @ 2022-09-05 15:26 UTC (permalink / raw)
To: Pavel Machek, Lee Jones, Ulf Hansson, Christian Mauderer
Cc: Wei Yongjun, linux-leds, linux-kernel
From: Wei Yongjun <weiyongjun1@huawei.com>
Add spi_device_id entries to silent following SPI warning:
SPI driver leds_spi_byte has no spi_device_id for ubnt,acb-spi-led
Signed-off-by: Wei Yongjun <weiyongjun1@huawei.com>
---
drivers/leds/leds-spi-byte.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/drivers/leds/leds-spi-byte.c b/drivers/leds/leds-spi-byte.c
index 2bc5c99daf51..9d23dc9e7639 100644
--- a/drivers/leds/leds-spi-byte.c
+++ b/drivers/leds/leds-spi-byte.c
@@ -137,9 +137,16 @@ static void spi_byte_remove(struct spi_device *spi)
mutex_destroy(&led->mutex);
}
+static const struct spi_device_id spi_byte_spi_ids[] = {
+ { "acb-spi-led", (kernel_ulong_t)&ubnt_acb_spi_led_cdef },
+ { },
+};
+MODULE_DEVICE_TABLE(spi, spi_byte_spi_ids);
+
static struct spi_driver spi_byte_driver = {
.probe = spi_byte_probe,
.remove = spi_byte_remove,
+ .id_table = spi_byte_spi_ids,
.driver = {
.name = KBUILD_MODNAME,
.of_match_table = spi_byte_dt_ids,
--
2.34.1
^ permalink raw reply related [flat|nested] 5+ messages in thread
* Re: [PATCH 1/3] leds: cr0014114: silent no spi_device_id warning
2022-09-05 15:26 [PATCH 1/3] leds: cr0014114: silent no spi_device_id warning Wei Yongjun
2022-09-05 15:26 ` [PATCH 2/3] leds: el15203000: " Wei Yongjun
2022-09-05 15:26 ` [PATCH 3/3] leds: spi-byte: " Wei Yongjun
@ 2022-09-05 20:53 ` Oleh Kravchenko
2 siblings, 0 replies; 5+ messages in thread
From: Oleh Kravchenko @ 2022-09-05 20:53 UTC (permalink / raw)
To: Wei Yongjun, Pavel Machek; +Cc: Wei Yongjun, linux-leds, linux-kernel
Acked-by: Oleh Kravchenko <oleg@kaa.org.ua>
05.09.22 18:26, Wei Yongjun пише:
> From: Wei Yongjun <weiyongjun1@huawei.com>
>
> Add spi_device_id entries to silent following SPI warning:
>
> SPI driver leds_cr0014114 has no spi_device_id for crane,cr0014114
>
> Signed-off-by: Wei Yongjun <weiyongjun1@huawei.com>
> ---
> drivers/leds/leds-cr0014114.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/leds/leds-cr0014114.c b/drivers/leds/leds-cr0014114.c
> index c87686bd7c18..095455163246 100644
> --- a/drivers/leds/leds-cr0014114.c
> +++ b/drivers/leds/leds-cr0014114.c
> @@ -281,9 +281,16 @@ static const struct of_device_id cr0014114_dt_ids[] = {
>
> MODULE_DEVICE_TABLE(of, cr0014114_dt_ids);
>
> +static const struct spi_device_id cr0014114_spi_ids[] = {
> + { "cr0014114" },
> + { },
> +};
> +MODULE_DEVICE_TABLE(spi, cr0014114_spi_ids);
> +
> static struct spi_driver cr0014114_driver = {
> .probe = cr0014114_probe,
> .remove = cr0014114_remove,
> + .id_table = cr0014114_spi_ids,
> .driver = {
> .name = KBUILD_MODNAME,
> .of_match_table = cr0014114_dt_ids,
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH 2/3] leds: el15203000: silent no spi_device_id warning
2022-09-05 15:26 ` [PATCH 2/3] leds: el15203000: " Wei Yongjun
@ 2022-09-05 20:53 ` Oleh Kravchenko
0 siblings, 0 replies; 5+ messages in thread
From: Oleh Kravchenko @ 2022-09-05 20:53 UTC (permalink / raw)
To: Wei Yongjun, Pavel Machek; +Cc: Wei Yongjun, linux-leds, linux-kernel
Acked-by: Oleh Kravchenko <oleg@kaa.org.ua>
05.09.22 18:26, Wei Yongjun пише:
> From: Wei Yongjun <weiyongjun1@huawei.com>
>
> Add spi_device_id entries to silent following SPI warning:
>
> SPI driver leds_el15203000 has no spi_device_id for crane,el15203000
>
> Signed-off-by: Wei Yongjun <weiyongjun1@huawei.com>
> ---
> drivers/leds/leds-el15203000.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/leds/leds-el15203000.c b/drivers/leds/leds-el15203000.c
> index 7e7b617bcd56..e24b4399176e 100644
> --- a/drivers/leds/leds-el15203000.c
> +++ b/drivers/leds/leds-el15203000.c
> @@ -329,9 +329,16 @@ static const struct of_device_id el15203000_dt_ids[] = {
>
> MODULE_DEVICE_TABLE(of, el15203000_dt_ids);
>
> +static const struct spi_device_id el15203000_spi_ids[] = {
> + { "el15203000" },
> + { },
> +};
> +MODULE_DEVICE_TABLE(spi, el15203000_spi_ids);
> +
> static struct spi_driver el15203000_driver = {
> .probe = el15203000_probe,
> .remove = el15203000_remove,
> + .id_table = el15203000_spi_ids,
> .driver = {
> .name = KBUILD_MODNAME,
> .of_match_table = el15203000_dt_ids,
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2022-09-05 21:01 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-09-05 15:26 [PATCH 1/3] leds: cr0014114: silent no spi_device_id warning Wei Yongjun
2022-09-05 15:26 ` [PATCH 2/3] leds: el15203000: " Wei Yongjun
2022-09-05 20:53 ` Oleh Kravchenko
2022-09-05 15:26 ` [PATCH 3/3] leds: spi-byte: " Wei Yongjun
2022-09-05 20:53 ` [PATCH 1/3] leds: cr0014114: " Oleh Kravchenko
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).