From: Aditya Garg <gargaditya08@live.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: "bentiss@kernel.org" <bentiss@kernel.org>,
"Benjamin Tissoires" <benjamin.tissoires@redhat.com>,
"Thomas Weißschuh" <linux@weissschuh.net>,
"Thomas Weißschuh" <thomas@t-8ch.de>,
"Kerem Karabay" <kekrby@gmail.com>,
"Orlando Chamberlain" <orlandoch.dev@gmail.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>
Subject: Re: [PATCH RESEND v2 1/4] HID: hid-appletb-bl: add driver for the backlight of Apple Touch Bars
Date: Wed, 5 Feb 2025 03:50:17 +0000 [thread overview]
Message-ID: <PN0PR01MB8288DA05B1DEE461C605348DB8F72@PN0PR01MB8288.INDPRD01.PROD.OUTLOOK.COM> (raw)
> On 4 Feb 2025, at 7:47 AM, Jiri Kosina <jikos@kernel.org> wrote:
>
> On Tue, 4 Feb 2025, Aditya Garg wrote:
>
>> You might have noticed that the hid-apple driver has code for the magic
>> backlight. Now we have a case of MacBook Air 2020, which does not have a
>> touchbar but still shows presence of the touchbar backlight device, just
>> because it needs it for the keyboard backlight. In case we merge both
>> the backlight and touchbar code in a driver, on that model, the
>> backlight breaks. If kept separate, the touchbar driver simply doesn't
>> load and backlight works.
>
> Sorry for being dense, but does that mean that it's either hid-appletb-bl
> or hid-apple, but never both to make a good user experience on those
> devices?
>
> If so, can you please point out what exactly is the reason?
>
> Either those have different VID/PID combination, and then it can be easily
> made conditional both in code and in runtime.
> Are we talking about conflicting VID/PID combinations, some of them
> needing current hid-apple, and some of them needing (in a mutually
> exclusive way) hid-appletb-bl?
>
Just to clarify a bit more,
The touchbar backlight device is 05ac:8102, in all the models with magic backlight, that is, with as well as without touchbar. The MacBook Air 2020 is the only model with this device but not having a touchbar.
This device is responsible for both the touchbar brightness and the keyboard backlight, the 0th interface being responsible for keyboard backlight on Air and 1st on others.
> Thanks,
>
> --
> Jiri Kosina
> SUSE Labs
>
next reply other threads:[~2025-02-05 3:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 3:50 Aditya Garg [this message]
2025-02-07 12:53 ` [PATCH RESEND v2 1/4] HID: hid-appletb-bl: add driver for the backlight of Apple Touch Bars Jiri Kosina
-- strict thread matches above, loose matches on Subject: below --
2025-02-03 16:58 [PATCH RESEND v2 0/4] Touch Bar driver for Apple Macs with T2 Security Chip Aditya Garg
2025-02-03 17:02 ` [PATCH RESEND v2 1/4] HID: hid-appletb-bl: add driver for the backlight of Apple Touch Bars Aditya Garg
2025-02-03 21:55 ` Jiri Kosina
2025-02-04 2:11 ` Aditya Garg
2025-02-04 2:17 ` Jiri Kosina
2025-02-04 2:54 ` Aditya Garg
2025-02-03 17:03 ` Aditya Garg
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=PN0PR01MB8288DA05B1DEE461C605348DB8F72@PN0PR01MB8288.INDPRD01.PROD.OUTLOOK.COM \
--to=gargaditya08@live.com \
--cc=benjamin.tissoires@redhat.com \
--cc=bentiss@kernel.org \
--cc=jikos@kernel.org \
--cc=kekrby@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=orlandoch.dev@gmail.com \
--cc=thomas@t-8ch.de \
/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