From: Heiner Kallweit <hkallweit1@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
linux-staging@lists.linux.dev
Subject: [PATCH v2 0/2] staging: fbtft: add and use macro FBTFT_REGISTER_SPI_DRIVER
Date: Wed, 1 Dec 2021 22:01:22 +0100 [thread overview]
Message-ID: <773dc6ff-f2b4-4192-a128-c34bd3f5be01@gmail.com> (raw)
After 5fa6863ba692 ("spi: Check we have a spi_device_id for each DT
compatible") we need to add spi id_tables. Changing existing macro
FBTFT_REGISTER_DRIVER would have meant to change arguments and
therefore adjust all fbtft drivers.
This series adds a new and simplified macro FBTFT_REGISTER_SPI_DRIVER
that includes a spi id_table, and in addition to that:
- does not define a platform driver
- uses macro module_spi_driver()
Also the MODULE_ALIASes can be removed.
Works for me with a SH1106-based OLED display incl. module autoload.
For now I changed this driver only because I have hw to test it.
v2:
- consider that spi id_table name consists of device part of compatible string only
- instead of changing the existing macro, add a new one and make fb_sh1106 the first user
Heiner Kallweit (2):
staging: fbtft: add macro FBTFT_REGISTER_SPI_DRIVER
staging: fbtft: sh1106: use new macro FBTFT_REGISTER_SPI_DRIVER
drivers/staging/fbtft/fb_sh1106.c | 7 +-----
drivers/staging/fbtft/fbtft.h | 41 +++++++++++++++++++++++++++++++
2 files changed, 42 insertions(+), 6 deletions(-)
--
2.34.1
next reply other threads:[~2021-12-01 21:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 21:01 Heiner Kallweit [this message]
2021-12-01 21:02 ` [PATCH v2 1/2] staging: fbtft: add macro FBTFT_REGISTER_SPI_DRIVER Heiner Kallweit
2021-12-01 21:04 ` [PATCH v2 2/2] staging: fbtft: sh1106: use new " Heiner Kallweit
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=773dc6ff-f2b4-4192-a128-c34bd3f5be01@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).