From: Hao Yao <hao.yao@intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Dan Scally <dan.scally@ideasonboard.com>, <djrscally@gmail.com>,
"Hans de Goede" <hdegoede@redhat.com>,
Sakari Ailus <sakari.ailus@intel.com>,
"Bingbu Cao" <bingbu.cao@intel.com>,
<platform-driver-x86@vger.kernel.org>,
<linux-media@vger.kernel.org>
Subject: Re: [PATCH] platform/x86: int3472: Add strobe GPIO function
Date: Sat, 7 Oct 2023 18:23:10 +0800 [thread overview]
Message-ID: <b89c2ed2-5e19-4565-8ae7-9fd5f6e8387b@intel.com> (raw)
In-Reply-To: <ZSEVSy122qTWwvdy@smile.fi.intel.com>
Thank you Andy,
On 2023/10/7 16:22, Andy Shevchenko wrote:
> On Sat, Oct 07, 2023 at 10:13:09AM +0800, Hao Yao wrote:
>> Strobe pin is used for Lattice MIPI aggregator to control the LED
>> so it can be handled together with privacy LED.
>
> Thinking about this more, I am not now sure that this is a good approach.
> The idea behind the STROBE LED is that is used for flash light and should
> not be like on/off state, but rather the (quite) short pulse.
>
> Combining these two together may even overheat the real strobe LED if used.
I agree. If the GPIO is used for a real flash LED, is it better to
develop a new driver to control it. For example, some cameras need a
flashlight device "LM3643".
> That said, is that platform using strobe GPIO for the privacy LED for real?!
On my Meteor Lake device, this pin is used for IR camera so actually it
should control the IR LED. However I still don't know its detail usage.
It may depends on the Lattice firmware, because I found only the
handshake pin takes effects now and can't do more experiments. I think
we should leave it open and I will update when I find something new.
prev parent reply other threads:[~2023-10-07 10:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-07 2:13 [PATCH] platform/x86: int3472: Add strobe GPIO function Hao Yao
2023-10-07 8:22 ` Andy Shevchenko
2023-10-07 10:23 ` Hao Yao [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=b89c2ed2-5e19-4565-8ae7-9fd5f6e8387b@intel.com \
--to=hao.yao@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bingbu.cao@intel.com \
--cc=dan.scally@ideasonboard.com \
--cc=djrscally@gmail.com \
--cc=hdegoede@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=sakari.ailus@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