From: Daniel Thompson <daniel.thompson@linaro.org>
To: Julius Zint <julius@zint.sh>
Cc: Lee Jones <lee@kernel.org>, Jingoo Han <jingoohan1@gmail.com>,
Helge Deller <deller@gmx.de>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 0/1] Backlight driver for the Apple Studio Display
Date: Mon, 3 Jul 2023 11:36:20 +0100 [thread overview]
Message-ID: <20230703103620.GB4328@aspen.lan> (raw)
In-Reply-To: <20230701120806.11812-1-julius@zint.sh>
On Sat, Jul 01, 2023 at 02:08:02PM +0200, Julius Zint wrote:
> I have been using and testing this as a DKMS for 6 months now without
> any known issues. It bothers me, that it needs to be part of the
> initramfs instead of just working out of the box. Maybe someone else
> here knows, how to tell the USB HID driver, that this is not a HID device
> and it should keep its fingers from it.
If is says it is a HID device and is uses HID reports for control then
it *is* a HID device!
In other words you need your driver to register as a HID driver instead
of sending raw HID frames using the USB stack. If you do that then the
HID core infrastructure will ensure the right driver gets loaded (it
has special logic to automatically unregister hid-generic and load the
better driver as soon as one becomes available).
Daniel.
next prev parent reply other threads:[~2023-07-03 10:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-01 12:08 [PATCH 0/1] Backlight driver for the Apple Studio Display Julius Zint
2023-07-01 12:08 ` [PATCH 1/1] backlight: apple_bl_usb: Add Apple Studio Display support Julius Zint
2023-07-01 13:32 ` Rafał Miłecki
2023-07-01 14:00 ` kernel test robot
2023-07-01 22:00 ` Sam Ravnborg
2023-07-03 10:36 ` Daniel Thompson [this message]
2023-07-04 18:48 ` [PATCH 0/1] Backlight driver for the Apple Studio Display Julius Zint
[not found] <43d33bc0374ff57f45020c35d8234a0c74cffb77@hey.com>
2023-11-17 22:21 ` Julius Zint
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=20230703103620.GB4328@aspen.lan \
--to=daniel.thompson@linaro.org \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=jingoohan1@gmail.com \
--cc=julius@zint.sh \
--cc=lee@kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).