The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Werner Sembach <wse@tuxedocomputers.com>
To: "Hans de Goede" <hansg@kernel.org>, "Pavel Machek" <pavel@ucw.cz>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	PDx86 <platform-driver-x86@vger.kernel.org>,
	Andy Shevchenko <andy@kernel.org>,
	Guenter Roeck <linux@roeck-us.net>,
	Jiri Kosina <jikos@kernel.org>,
	Benjamin Tissoires <bentiss@kernel.org>,
	Sebastian Reichel <sre@kernel.org>
Subject: Re: [GIT PULL] platform-drivers-x86 for v6.16-1
Date: Tue, 27 May 2025 17:02:57 +0200	[thread overview]
Message-ID: <2c8504d2-7b17-4ce2-b75b-76b73c5fddda@tuxedocomputers.com> (raw)
In-Reply-To: <4cac7f91-608b-4362-99ed-4d8cd5935900@kernel.org>

Hi all,

Am 27.05.25 um 14:47 schrieb Hans de Goede:
> The HID subsystem has no intention to provide a separate
> API for HID lamp array devices instead userspace is expected
> to use /dev/hidraw# and openrgb, the defacto standard for userspace
> RGB LED control, has been working on supporting this for over
> a year already:
>
> https://gitlab.com/CalcProgrammer1/OpenRGB/-/merge_requests/2348
>
> and this support is scheduled to get merged before the next
> oprnrgb release. Also note that openrgb will need to support this
> regardless of the patches we are discussing now, since other
> hw is using this natively.

Hardly anything to add to what Hans wrote, just that now that the kernel side is 
done, I started working on the userspace side to push that forward: 
https://gitlab.com/tuxedocomputers/development/OpenRGB/-/tree/tux_lamparray 
(based on the MR by CalcProgrammer1 linked above)

Best regards,

Werner



  parent reply	other threads:[~2025-05-27 15:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-27  9:44 [GIT PULL] platform-drivers-x86 for v6.16-1 Ilpo Järvinen
2025-05-27 12:07 ` Pavel Machek
2025-05-27 12:47   ` Hans de Goede
2025-05-27 12:49     ` Hans de Goede
2025-05-27 13:13     ` Benjamin Tissoires
2025-05-27 15:02     ` Werner Sembach [this message]
2025-05-27 18:16     ` Pavel Machek
2025-05-29 17:48 ` pr-tracker-bot

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=2c8504d2-7b17-4ce2-b75b-76b73c5fddda@tuxedocomputers.com \
    --to=wse@tuxedocomputers.com \
    --cc=andy@kernel.org \
    --cc=bentiss@kernel.org \
    --cc=hansg@kernel.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=jikos@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=pavel@ucw.cz \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=sre@kernel.org \
    --cc=torvalds@linux-foundation.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