From: Torstein Eide <torsteine+linux@gmail.com>
To: Jiri Kosina <jikos@kernel.org>, Benjamin Tissoires <bentiss@kernel.org>
Cc: Hans de Goede <hansg@kernel.org>,
Maoyi Xie <maoyixie.tju@gmail.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 2/4] HID: lg-g15: add LCD pixel-content framebuffer
Date: Mon, 9 Nov 2026 10:44:24 +0100 [thread overview]
Message-ID: <20261109094426.1432465-3-torsteine+linux@gmail.com> (raw)
In-Reply-To: <20261109094426.1432465-1-torsteine+linux@gmail.com>
Add a 160x43 1bpp fbdev framebuffer for the GamePanel LCD's pixel
content, behind the new HID_LOGITECH_G15_FB option.
Updates use fbdev deferred I/O: when userspace dirties the framebuffer
(mmap, write() or the drawing ops) the frame is packed into the LCD's
column-major wire format and sent as Output Report 3. The packed wire
buffer is a heap allocation, not a stack array, since the USB core
refuses to DMA-map stack memory. A set bit is a dark pixel, so the
visual is FB_VISUAL_MONO01.
The keyboard ignores output reports unless an URB is queued on the
input endpoint, so the HID device is kept open while the framebuffer
exists. The fb_info is released from fb_destroy, as it may outlive the
HID device while /dev/fbN is still open. The last frame is re-sent on
resume, since the LCD loses its content across a USB reset.
Tested on Logitech G15v2.
Based on libg15.c.
Signed-off-by: Torstein Eide <torsteine+linux@gmail.com>
Based-on-work-by: Philip Lawatsch <philip@lawatsch.at>
Based-on-work-by: Alex Ibrado <alex@ibrado.org>
Based-on-work-by: Anthony J. Mirabella <mirabeaj@gmail.com>
Based-on-work-by: Mike Lampard <mlampard@users.sourceforge.net>
Assisted-by: Claude:claude-opus-5-5
---
drivers/hid/Kconfig | 13 ++
drivers/hid/hid-lg-g15.c | 303 +++++++++++++++++++++++++++++++++++++++
2 files changed, 316 insertions(+)
diff --git a/drivers/hid/Kconfig b/drivers/hid/Kconfig
index 2481bc01c435..57305180818a 100644
--- a/drivers/hid/Kconfig
+++ b/drivers/hid/Kconfig
@@ -674,6 +674,19 @@ config HID_LOGITECH
help
Support for Logitech devices that are not fully compliant with HID standard.
+config HID_LOGITECH_G15_FB
+ bool "Logitech G15 LCD framebuffer support"
+ depends on HID_LOGITECH
+ depends on HID_LOGITECH=FB || FB=y
+ select FB_SYSMEM_HELPERS_DEFERRED
+ help
+ Provide access to the 160x43 monochrome GamePanel LCD of the
+ Logitech G15 and G15 v2 keyboards via a framebuffer device.
+
+ The LCD is updated with deferred I/O whenever the framebuffer
+ contents change. Say Y here if you want to draw on the LCD from
+ userspace or bind a framebuffer console to it.
+
config HID_LOGITECH_DJ
tristate "Logitech receivers full support"
depends on USB_HID
diff --git a/drivers/hid/hid-lg-g15.c b/drivers/hid/hid-lg-g15.c
index 50abe6c58b10..35d183787383 100644
--- a/drivers/hid/hid-lg-g15.c
+++ b/drivers/hid/hid-lg-g15.c
@@ -6,6 +6,7 @@
*/
#include <linux/device.h>
+#include <linux/fb.h>
#include <linux/hid.h>
#include <linux/leds.h>
#include <linux/led-class-multicolor.h>
@@ -13,6 +14,7 @@
#include <linux/random.h>
#include <linux/sched.h>
#include <linux/usb.h>
+#include <linux/vmalloc.h>
#include <linux/wait.h>
#include <dt-bindings/leds/common.h>
@@ -22,6 +24,22 @@
#define LG_G15_FEATURE_REPORT 0x02
+/*
+ * LCD pixel content, G15/G15 v2 GamePanel LCD only. Not a Feature Report:
+ * a numbered Output Report sent over the interrupt-OUT endpoint. The wire
+ * buffer has a fixed 32-byte header before the packed pixel data starts,
+ * and the packer's last (partial) row-group reads up to 132 bytes past
+ * the logical WIDTH/8*HEIGHT frame size, so the backing allocation must
+ * be padded to LG_G15_LCD_WIRE_SIZE, not just the logical frame size.
+ */
+#define LG_G15_LCD_OUTPUT_REPORT 0x03
+#define LG_G15_LCD_WIDTH 160
+#define LG_G15_LCD_HEIGHT 43
+#define LG_G15_LCD_ROW_BYTES (LG_G15_LCD_WIDTH / 8)
+#define LG_G15_LCD_FB_SIZE (LG_G15_LCD_ROW_BYTES * LG_G15_LCD_HEIGHT)
+#define LG_G15_LCD_WIRE_OFFSET 32
+#define LG_G15_LCD_WIRE_SIZE 0x03e0
+
#define LG_G510_FEATURE_M_KEYS_LEDS 0x04
#define LG_G510_FEATURE_BACKLIGHT_RGB 0x05
#define LG_G510_FEATURE_POWER_ON_RGB 0x06
@@ -88,6 +106,17 @@ struct lg_g15_led {
u8 red, green, blue;
};
+struct lg_g15_fbdev {
+ struct fb_info *info; /* NULL when no framebuffer is registered */
+ /*
+ * Packed wire-format buffer, heap-allocated (not a local/stack
+ * array): it gets DMA-mapped by hid_hw_output_report()/usbhid, and
+ * the USB core refuses to map stack memory (returns -EAGAIN, see
+ * object_is_on_stack() in drivers/usb/core/hcd.c).
+ */
+ u8 *wire;
+};
+
struct lg_g15_data {
/* Must be first for proper dma alignment */
u8 transfer_buf[LG_G15_TRANSFER_BUF_SIZE];
@@ -99,6 +128,7 @@ struct lg_g15_data {
struct hid_device *hdev;
enum lg_g15_model model;
struct lg_g15_led leds[LG_G15_LED_ARRAY_SIZE];
+ struct lg_g15_fbdev fbdev; /* G15/G15 v2 GamePanel LCD only */
bool game_mode_enabled;
bool backlight_disabled; /* true == HW backlight toggled *OFF* */
bool lcd_contrast_set; /* LCD contrast written at least once */
@@ -1051,6 +1081,270 @@ static void lg_g15_setup_led_rgb(struct lg_g15_data *g15, int index)
gled->mcdev.subled_info = subled_info;
}
+/********* G15 LCD framebuffer *********/
+
+#ifdef CONFIG_HID_LOGITECH_G15_FB
+
+/*
+ * fb_info private data. The fb_info can outlive the HID device (e.g. when
+ * /dev/fbN is still open on unplug), so the link back to the device is
+ * cleared in lg_g15_unregister_fb() and the fb_info itself is only freed
+ * from fb_destroy once its last user is gone.
+ */
+struct lg_g15_fb_par {
+ struct fb_deferred_io defio;
+ /* Protects g15 and serializes frame updates */
+ struct mutex lock;
+ /* NULL once the HID device is gone */
+ struct lg_g15_data *g15;
+ /* At least one frame was sent successfully */
+ bool sent;
+};
+
+static const struct fb_fix_screeninfo lg_g15_fb_fix = {
+ .id = "G15 LCD",
+ .type = FB_TYPE_PACKED_PIXELS,
+ /* A set bit is a dark pixel */
+ .visual = FB_VISUAL_MONO01,
+ .xpanstep = 0,
+ .ypanstep = 0,
+ .ywrapstep = 0,
+ .line_length = LG_G15_LCD_ROW_BYTES,
+ .smem_len = LG_G15_LCD_FB_SIZE,
+ .accel = FB_ACCEL_NONE,
+};
+
+static const struct fb_var_screeninfo lg_g15_fb_var = {
+ .xres = LG_G15_LCD_WIDTH,
+ .yres = LG_G15_LCD_HEIGHT,
+ .xres_virtual = LG_G15_LCD_WIDTH,
+ .yres_virtual = LG_G15_LCD_HEIGHT,
+ .bits_per_pixel = 1,
+ .red = { 0, 1, 0 },
+ .green = { 0, 1, 0 },
+ .blue = { 0, 1, 0 },
+ .vmode = FB_VMODE_NONINTERLACED,
+};
+
+/*
+ * Packs pixels column-major (8 vertically-stacked source rows per
+ * destination byte), not the row-major layout the linear fb buffer holds.
+ *
+ * fb is LG_G15_LCD_WIRE_SIZE bytes (padded, not just LG_G15_LCD_FB_SIZE) -
+ * the last of the six 8-row groups only has 3 real pixel-rows (43 isn't a
+ * multiple of 8), and this reads past the logical frame into that padding
+ * for the other 5.
+ */
+static void lg_g15_fb_pack(u8 *wire, const u8 *fb)
+{
+ unsigned int output_offset = LG_G15_LCD_WIRE_OFFSET;
+ unsigned int base_offset = 0;
+ unsigned int row, col;
+ unsigned int height_in_bytes = DIV_ROUND_UP(LG_G15_LCD_HEIGHT, 8);
+
+ for (row = 0; row < height_in_bytes; row++) {
+ for (col = 0; col < LG_G15_LCD_WIDTH; col++) {
+ unsigned int bit = col % 8;
+ unsigned int sub;
+ u8 packed = 0;
+
+ for (sub = 0; sub < 8; sub++) {
+ unsigned int pixel_offset =
+ base_offset + sub * LG_G15_LCD_ROW_BYTES;
+
+ packed |= ((fb[pixel_offset] << bit) & 0x80) >> (7 - sub);
+ }
+
+ wire[output_offset] = packed;
+ output_offset++;
+ if (bit == 7)
+ base_offset++;
+ }
+ base_offset += LG_G15_LCD_WIDTH - LG_G15_LCD_ROW_BYTES;
+ }
+}
+
+/*
+ * Deferred IO callback, runs when userspace dirtied the framebuffer (through
+ * mmap, write() or the drawing ops). Writes made while a frame is being sent
+ * re-arm the deferred work, so no update is lost.
+ */
+static void lg_g15_fb_deferred_io(struct fb_info *info, struct list_head *pagereflist)
+{
+ struct lg_g15_fb_par *par = info->par;
+ struct lg_g15_data *g15;
+ u8 *wire;
+ int ret;
+
+ mutex_lock(&par->lock);
+
+ g15 = par->g15;
+ if (!g15)
+ goto out;
+
+ wire = g15->fbdev.wire;
+ memset(wire, 0, LG_G15_LCD_WIRE_OFFSET);
+ lg_g15_fb_pack(wire, (const u8 *)info->screen_buffer);
+ wire[0] = LG_G15_LCD_OUTPUT_REPORT;
+
+ ret = hid_hw_output_report(g15->hdev, wire, LG_G15_LCD_WIRE_SIZE);
+ if (ret < 0)
+ hid_err_ratelimited(g15->hdev, "Error writing LCD framebuffer: %d\n", ret);
+ else
+ par->sent = true;
+
+out:
+ mutex_unlock(&par->lock);
+}
+
+static void lg_g15_fb_damage_range(struct fb_info *info, off_t off, size_t len)
+{
+ schedule_delayed_work(&info->deferred_work, info->fbdefio->delay);
+}
+
+static void lg_g15_fb_damage_area(struct fb_info *info, u32 x, u32 y,
+ u32 width, u32 height)
+{
+ schedule_delayed_work(&info->deferred_work, info->fbdefio->delay);
+}
+
+FB_GEN_DEFAULT_DEFERRED_SYSMEM_OPS(lg_g15_fb,
+ lg_g15_fb_damage_range,
+ lg_g15_fb_damage_area)
+
+static int lg_g15_fb_blank(int blank, struct fb_info *info)
+{
+ return 0;
+}
+
+static void lg_g15_fb_destroy(struct fb_info *info)
+{
+ struct lg_g15_fb_par *par = info->par;
+
+ fb_deferred_io_cleanup(info);
+ mutex_destroy(&par->lock);
+ vfree(info->screen_buffer);
+ framebuffer_release(info);
+}
+
+static const struct fb_ops lg_g15_fb_ops = {
+ .owner = THIS_MODULE,
+ FB_DEFAULT_DEFERRED_OPS(lg_g15_fb),
+ .fb_destroy = lg_g15_fb_destroy,
+ .fb_blank = lg_g15_fb_blank,
+};
+
+static int lg_g15_register_fb(struct lg_g15_data *g15)
+{
+ struct lg_g15_fbdev *fbdev = &g15->fbdev;
+ struct lg_g15_fb_par *par;
+ struct fb_info *info;
+ void *buffer;
+ int ret;
+
+ fbdev->wire = devm_kzalloc(&g15->hdev->dev, LG_G15_LCD_WIRE_SIZE, GFP_KERNEL);
+ if (!fbdev->wire)
+ return -ENOMEM;
+
+ /* Padded to LG_G15_LCD_WIRE_SIZE - see the comment by that macro. */
+ buffer = vzalloc(LG_G15_LCD_WIRE_SIZE);
+ if (!buffer)
+ return -ENOMEM;
+
+ info = framebuffer_alloc(sizeof(*par), &g15->hdev->dev);
+ if (!info) {
+ ret = -ENOMEM;
+ goto err_free_buffer;
+ }
+
+ par = info->par;
+ mutex_init(&par->lock);
+ par->g15 = g15;
+ par->defio.delay = HZ / 10;
+ par->defio.deferred_io = lg_g15_fb_deferred_io;
+
+ info->fbdefio = &par->defio;
+ info->fbops = &lg_g15_fb_ops;
+ info->flags |= FBINFO_VIRTFB;
+ info->screen_buffer = buffer;
+ info->screen_size = LG_G15_LCD_FB_SIZE;
+ info->fix = lg_g15_fb_fix;
+ info->var = lg_g15_fb_var;
+
+ ret = fb_deferred_io_init(info);
+ if (ret)
+ goto err_release_info;
+
+ /*
+ * As with the G-keys settings report in probe, the keyboard ignores
+ * output reports unless an URB is queued on the input endpoint, so
+ * keep the device open for as long as the framebuffer exists.
+ */
+ ret = hid_hw_open(g15->hdev);
+ if (ret)
+ goto err_defio_cleanup;
+
+ ret = register_framebuffer(info);
+ if (ret)
+ goto err_hw_close;
+
+ fbdev->info = info;
+ return 0;
+
+err_hw_close:
+ hid_hw_close(g15->hdev);
+err_defio_cleanup:
+ fb_deferred_io_cleanup(info);
+err_release_info:
+ mutex_destroy(&par->lock);
+ framebuffer_release(info);
+err_free_buffer:
+ vfree(buffer);
+ return ret;
+}
+
+static void lg_g15_unregister_fb(struct lg_g15_data *g15)
+{
+ struct fb_info *info = g15->fbdev.info;
+ struct lg_g15_fb_par *par;
+
+ if (!info)
+ return;
+
+ /* Waits for a running update; later ones see par->g15 == NULL */
+ par = info->par;
+ mutex_lock(&par->lock);
+ par->g15 = NULL;
+ mutex_unlock(&par->lock);
+
+ g15->fbdev.info = NULL;
+ /* The fb_info is freed by lg_g15_fb_destroy() once its last user is gone */
+ unregister_framebuffer(info);
+ hid_hw_close(g15->hdev);
+}
+
+/* The LCD loses its pixel content across a USB reset or power loss */
+static void lg_g15_fb_redraw(struct lg_g15_data *g15)
+{
+ struct fb_info *info = g15->fbdev.info;
+ struct lg_g15_fb_par *par;
+
+ if (!info)
+ return;
+
+ par = info->par;
+ if (par->sent)
+ schedule_delayed_work(&info->deferred_work, 0);
+}
+
+#else /* CONFIG_HID_LOGITECH_G15_FB */
+
+static inline int lg_g15_register_fb(struct lg_g15_data *g15) { return 0; }
+static inline void lg_g15_unregister_fb(struct lg_g15_data *g15) { }
+static inline void lg_g15_fb_redraw(struct lg_g15_data *g15) { }
+
+#endif /* CONFIG_HID_LOGITECH_G15_FB */
+
static int lg_g15_register_led(struct lg_g15_data *g15, int i, const char *name)
{
int ret;
@@ -1407,6 +1701,10 @@ static int lg_g15_probe(struct hid_device *hdev, const struct hid_device_id *id)
ret = lg_g15_register_led(g15, LG_G15_LCD_CONTRAST, "g15::lcd_contrast");
if (ret)
goto error_hw_stop;
+
+ ret = lg_g15_register_fb(g15);
+ if (ret)
+ goto error_hw_stop;
}
return 0;
@@ -1462,6 +1760,9 @@ static void lg_g15_remove(struct hid_device *hdev)
if (g15 && g15->work.func)
cancel_work_sync(&g15->work);
+ if (g15)
+ lg_g15_unregister_fb(g15);
+
hid_hw_stop(hdev);
}
@@ -1481,6 +1782,8 @@ static int lg_g15_resume(struct hid_device *hdev)
if (contrast->cdev.dev && g15->lcd_contrast_set)
lg_g15_contrast_set(&contrast->cdev, contrast->brightness);
+ lg_g15_fb_redraw(g15);
+
return 0;
}
--
2.53.0
next prev parent reply other threads:[~2026-11-09 9:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 9:44 [PATCH 0/4] HID: lg-g15: G15 v2 LCD and game-mode support Torstein Eide
2026-11-09 9:44 ` [PATCH 1/4] HID: lg-g15: add LCD contrast LED Torstein Eide
2026-11-09 9:44 ` Torstein Eide [this message]
2026-11-09 9:44 ` [PATCH 3/4] HID: lg-g15: report Super-key-lock state on G15 v2's keyboard interface Torstein Eide
2026-11-09 9:44 ` [PATCH 4/4] HID: lg-g15: cancel LED work only after stopping the hardware Torstein Eide
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=20261109094426.1432465-3-torsteine+linux@gmail.com \
--to=torsteine+linux@gmail.com \
--cc=bentiss@kernel.org \
--cc=hansg@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maoyixie.tju@gmail.com \
/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
all inboxes | Powered by JetHome®