From: Thomas Zimmermann <tzimmermann@suse.de>
To: deller@gmx.de, daniel@ffwll.ch, sam@ravnborg.org, javierm@redhat.com
Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-staging@lists.linux.dev, linux-hyperv@vger.kernel.org,
linux-input@vger.kernel.org,
Thomas Zimmermann <tzimmermann@suse.de>
Subject: [PATCH 0/8] fbdev: Use helpers for deferred I/O
Date: Mon, 28 Aug 2023 15:14:16 +0200 [thread overview]
Message-ID: <20230828132131.29295-1-tzimmermann@suse.de> (raw)
Here's another patchset for deferred-I/O helpers. Update a number
of fbdev drivers with deferred I/O to use fbdev's helper macros and
Kconfig tokens.
Generating and initializing via helpers macros will later allow for
a fine-grained setup, depending on Kconfig options. For example, it
will be possible to leave out file I/O if FB_DEVICE has not been set.
Each driver in special in its own way. The smscufx and udlfb drivers
support file I/O without damage updates. (That probably doesn't work
correctly.) So they provide their own mmap code. The hyperv_fb driver
sometimes operates on memory in I/O address spaces and fails to do
damage handling correctly for write operations. The picolcd and fbtft
drivers are outside of fbdev.
Thomas Zimmermann (8):
fbdev/smscufx: Use fb_ops helpers for deferred I/O
fbdev/udlfb: Use fb_ops helpers for deferred I/O
fbdev: Add Kconfig macro FB_IOMEM_HELPERS_DEFERRED
fbdev/hyperv_fb: Use fb_ops helpers for deferred I/O
hid: Remove trailing whitespace
hid/picolcd: Use fb_ops helpers for deferred I/O
staging/fbtft: Initialize fb_op struct as static const
staging/fbtft: Use fb_ops helpers for deferred I/O
drivers/hid/Kconfig | 8 +--
drivers/hid/hid-picolcd_fb.c | 73 ++++++----------------
drivers/staging/fbtft/Kconfig | 6 +-
drivers/staging/fbtft/fbtft-core.c | 99 ++++++++----------------------
drivers/video/fbdev/Kconfig | 5 +-
drivers/video/fbdev/core/Kconfig | 6 ++
drivers/video/fbdev/hyperv_fb.c | 48 +++++----------
drivers/video/fbdev/smscufx.c | 85 +++++++------------------
drivers/video/fbdev/udlfb.c | 89 +++++++--------------------
9 files changed, 114 insertions(+), 305 deletions(-)
--
2.41.0
next reply other threads:[~2023-08-28 13:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 13:14 Thomas Zimmermann [this message]
2023-08-28 13:14 ` [PATCH 1/8] fbdev/smscufx: Use fb_ops helpers for deferred I/O Thomas Zimmermann
2023-09-04 12:59 ` Javier Martinez Canillas
2023-09-04 14:39 ` Thomas Zimmermann
2023-09-04 14:45 ` Thomas Zimmermann
2023-09-04 15:26 ` Javier Martinez Canillas
2023-08-28 13:14 ` [PATCH 2/8] fbdev/udlfb: " Thomas Zimmermann
2023-09-04 13:05 ` Javier Martinez Canillas
2023-09-04 14:43 ` Thomas Zimmermann
2023-09-04 15:28 ` Javier Martinez Canillas
2023-08-28 13:14 ` [PATCH 3/8] fbdev: Add Kconfig macro FB_IOMEM_HELPERS_DEFERRED Thomas Zimmermann
2023-09-04 13:10 ` Javier Martinez Canillas
2023-08-28 13:14 ` [PATCH 4/8] fbdev/hyperv_fb: Use fb_ops helpers for deferred I/O Thomas Zimmermann
2023-09-04 13:18 ` Javier Martinez Canillas
2023-08-28 13:14 ` [PATCH 5/8] hid: Remove trailing whitespace Thomas Zimmermann
2023-09-04 13:24 ` Javier Martinez Canillas
2023-08-28 13:14 ` [PATCH 6/8] hid/picolcd: Use fb_ops helpers for deferred I/O Thomas Zimmermann
2023-09-04 13:27 ` Javier Martinez Canillas
2023-08-28 13:14 ` [PATCH 7/8] staging/fbtft: Initialize fb_op struct as static const Thomas Zimmermann
2023-08-28 14:51 ` Greg KH
2023-09-04 13:28 ` Javier Martinez Canillas
2023-08-28 13:14 ` [PATCH 8/8] staging/fbtft: Use fb_ops helpers for deferred I/O Thomas Zimmermann
2023-08-28 14:51 ` Greg KH
2023-09-04 13:28 ` Javier Martinez Canillas
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=20230828132131.29295-1-tzimmermann@suse.de \
--to=tzimmermann@suse.de \
--cc=daniel@ffwll.ch \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=sam@ravnborg.org \
/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).