From: Heiner Kallweit <hkallweit1@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
DRI Development <dri-devel@lists.freedesktop.org>,
Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
linux-staging@lists.linux.dev
Subject: Re: [PATCH] staging: fbtft: add spi_device_id table
Date: Tue, 30 Nov 2021 21:22:50 +0100 [thread overview]
Message-ID: <8597bdf2-c383-43b5-6205-f78c90b4957a@gmail.com> (raw)
In-Reply-To: <CAMuHMdU_90XdFZM6kVA78XUX+7+Jm1WqjBmBN7irVOY3k-Gcfg@mail.gmail.com>
On 30.11.2021 09:16, Geert Uytterhoeven wrote:
> Hi Heiner,
>
> On Mon, Nov 29, 2021 at 10:12 PM Heiner Kallweit <hkallweit1@gmail.com> wrote:
>> After 5fa6863ba692 ("spi: Check we have a spi_device_id for each DT
>> compatible") we need the following to make the SPI core happy.
>>
>> Works for me with a SH1106-based OLED display.
>>
>> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
>
> Thanks for your patch!
>
>> --- a/drivers/staging/fbtft/fbtft.h
>> +++ b/drivers/staging/fbtft/fbtft.h
>> @@ -307,12 +307,19 @@ static const struct of_device_id dt_ids[] = { \
>> \
>> MODULE_DEVICE_TABLE(of, dt_ids); \
>> \
>> +static const struct spi_device_id spi_ids[] = { \
>> + { .name = _compatible }, \
>
> Shouldn't this be the part of _compatible after the "<vendor>," prefix?
>
You're right. I was fooled by a new bug in SPI core that made the warning
suddenly disappear:
https://patchwork.kernel.org/project/spi-devel-general/patch/44b2ad71-dc4b-801c-237f-9c233f675c0d@gmail.com/
>> + {}, \
>> +}; \
>> + \
>> +MODULE_DEVICE_TABLE(spi, spi_ids); \
>> \
>> static struct spi_driver fbtft_driver_spi_driver = { \
>> .driver = { \
>> .name = _name, \
>> .of_match_table = dt_ids, \
>> }, \
>> + .id_table = spi_ids, \
>> .probe = fbtft_driver_probe_spi, \
>> .remove = fbtft_driver_remove_spi, \
>> }; \
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
>
prev parent reply other threads:[~2021-11-30 20:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-27 22:20 [PATCH] staging: fbtft: add spi_device_id table Heiner Kallweit
2021-11-30 8:16 ` Geert Uytterhoeven
2021-11-30 20:22 ` Heiner Kallweit [this message]
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=8597bdf2-c383-43b5-6205-f78c90b4957a@gmail.com \
--to=hkallweit1@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).