public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Marco Nenciarini <mnencia@kcore.it>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: platform-driver-x86@vger.kernel.org, linux-media@vger.kernel.org,
	hao.yao@intel.com, sakari.ailus@linux.intel.com, andy@kernel.org
Subject: Re: [PATCH] platform/x86: int3472: Add GPIO type 0x02 (strobe) mapping
Date: Fri, 20 Mar 2026 17:40:23 +0100	[thread overview]
Message-ID: <ab14d0M9TkC_yV9D@spark.kcore.it> (raw)
In-Reply-To: <CAHp75VeiNd2Ptj9aoZcmSO-c+-RQG-R7kxpzyk3edKU2Ur05Gg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1052 bytes --]

Hi Andy,

First, apologies for the triple submission. It was a sending error
on my side (mutt submitted three separate copies), not three patch
versions. Please disregard the duplicates.

Regarding your feedback:

> Link tag, Closes tags, Cc placement

Noted, thank you for the clear guidance. I will apply these if I
send an updated version.

> get_maintainer.pl

Thank you for the pointer and for sharing your ge2maintainer.sh
script.

> strobe / privacy-led mapping

Hans pointed out that GPIO type 0x02 is actually for an IR flood
LED, not a privacy LED. After digging into the ACPI tables on my
machine, I confirmed he is correct. The GPIO belongs to an INT3472
controlling an empty IR sensor slot, not the active OV08F4 camera.
I have replied to Hans with the full analysis. The mapping in this
patch is semantically wrong, so it may not be needed at all, or it
would need the refactoring Hans suggested.

Thanks,
Marco

-- 
Marco Nenciarini - mnencia@kcore.it
7C23 B804 3E65 D298 0A21  B6E2 589F 03F0 1BA5 5038

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2026-03-20 16:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-20  9:34 [PATCH] platform/x86: int3472: Add GPIO type 0x02 (strobe) mapping Marco Nenciarini
2026-03-20 11:57 ` Andy Shevchenko
2026-03-20 11:59   ` Andy Shevchenko
2026-03-20 16:40   ` Marco Nenciarini [this message]
2026-03-20 12:35 ` johannes.goede
2026-03-20 16:12   ` Marco Nenciarini
  -- strict thread matches above, loose matches on Subject: below --
2026-03-20  9:33 Marco Nenciarini
2026-03-20  9:32 Marco Nenciarini

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=ab14d0M9TkC_yV9D@spark.kcore.it \
    --to=mnencia@kcore.it \
    --cc=andy.shevchenko@gmail.com \
    --cc=andy@kernel.org \
    --cc=hao.yao@intel.com \
    --cc=linux-media@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=sakari.ailus@linux.intel.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