From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: "José Guilherme de Castro Rodrigues" <jose.guilherme.cr.bh@gmail.com>
Cc: Corentin Chary <corentin.chary@gmail.com>,
"Luke D. Jones" <luke@ljones.dev>,
Denis Benato <benato.denis96@gmail.com>,
Hans de Goede <hansg@kernel.org>,
platform-driver-x86@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] platform/x86: asus-wmi: fix camera key led on Zenbook S14
Date: Thu, 9 Apr 2026 15:45:29 +0300 (EEST) [thread overview]
Message-ID: <7db8d74a-e250-d790-aaca-d02a08a7c091@linux.intel.com> (raw)
In-Reply-To: <ac6xgsMxzpnU_8FA@djouze-zen>
[-- Attachment #1: Type: text/plain, Size: 1213 bytes --]
On Thu, 2 Apr 2026, José Guilherme de Castro Rodrigues wrote:
> On Tue, Mar 31, 2026 at 08:01:47PM -0300, José Guilherme de Castro Rodrigues wrote:
> >
> > This change is not visible to userspace, as no sysfs attribute for
> > ASUS_WMI_DEVID_CAMERA_LED_NEG exists.
> >
> > + if (is_camera_toggle(code) && asus->camera_neg_led_available) {
> > + camera_neg_led_trigger_update(asus);
> > + return;
> > + }
> > +
> > if (!sparse_keymap_report_event(asus->inputdev, code,
> > key_value, autorelease))
> > pr_info("Unknown key code 0x%x\n", code);
>
> This change is actually visible to userspace because I'm early returning
> and that means the event for the camera key is not propagated to
> userspace. Sashiko correctly identified that, as well as another detail
> in formatting (using space instead of tab for indentation on the newly
> added macros). The event is currently not used on my system, so I didn't
> notice it before.
>
> Removing the return fixes this. I can send a new version of the patch if
> necessary.
Please just send a new version. It will be much easier for me when I don't
need to hunt down odd spaces or do multi-line code edits.
--
i.
prev parent reply other threads:[~2026-04-09 12:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 23:01 [PATCH] platform/x86: asus-wmi: fix camera key led on Zenbook S14 José Guilherme de Castro Rodrigues
2026-04-02 18:12 ` José Guilherme de Castro Rodrigues
2026-04-09 12:45 ` Ilpo Järvinen [this message]
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=7db8d74a-e250-d790-aaca-d02a08a7c091@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=benato.denis96@gmail.com \
--cc=corentin.chary@gmail.com \
--cc=hansg@kernel.org \
--cc=jose.guilherme.cr.bh@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luke@ljones.dev \
--cc=platform-driver-x86@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