From: Hans de Goede <hdegoede@redhat.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Dan Scally" <djrscally@gmail.com>,
"Alan Stern" <stern@rowland.harvard.edu>,
"Sakari Ailus" <sakari.ailus@linux.intel.com>,
"Hao Yao" <hao.yao@intel.com>,
"Bingbu Cao" <bingbu.cao@intel.com>, Duane <duanek@chorus.net>,
platform-driver-x86@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [PATCH v2 0/9] platform/x86: int3472: Add handshake pin support
Date: Thu, 3 Apr 2025 12:30:29 +0200 [thread overview]
Message-ID: <37de4bf2-c6c1-4d16-9f04-c0d9152dfe7b@redhat.com> (raw)
In-Reply-To: <CAHp75VfxjYQ=RzeYUWP7gu=xJ=f1gH=VGXz_cBRqBvkfSH02ow@mail.gmail.com>
Hi Andy,
Thank you for all the reviews.
On 2-Apr-25 11:02 PM, Andy Shevchenko wrote:
> On Wed, Apr 2, 2025 at 11:25 PM Hans de Goede <hdegoede@redhat.com> wrote:
>>
>> New Intel Meteor Lake based laptops with IPU6 cameras have a new type 0x12
>> pin defined in the INT3472 sensor companion device which describes
>> the sensor's GPIOs.
>>
>> This pin is primarily used on designs with a Lattice FPGA chip which is
>> capable of running the sensor independently of the main CPU for features
>> like presence detection. This pin needs to be driven high to make the FPGA
>> run the power-on sequence of the sensor. After driving the pin high
>> the FPGA "firmware" needs 25ms to comlpete the power-on sequence.
>>
>> This series implements support for this by modelling the handshake GPIO
>> as a GPIO driven 'dvdd' regulator with an enable-time of 25 ms, also see:
>>
>> https://lore.kernel.org/platform-driver-x86/59f672c3-6d87-4ec7-9b7f-f44fe2cce934@redhat.com/
>>
>> Patch 1 Is an unrelated cleanup which I had lying around
>> Patches 2-7 Prepare + Implement the handshake GPIO
>> Patch 8 Is a small patch adding some extra debugging to GPIO remapping
>
> You meant patch 9 here, right?
>
> Offtopic: I sent you a message asking about AtomISP patch queue
> status, but no answer. I understand that you are kinda very busy,
> still it seems we missed one cycle for the patches you already have in
> your queue. I haven't investigated where the bottle neck happened,
> though. Hence just asking what's the plan with them and other patches
> that are already in the mailing list (I have received at least two
> that I was Cc'ed on).
Yeah, I've been burried in work a bit, so this fall through the cracks.
I've some more bandwidth now and I have a mailfolder with all
the pending atomisp patches in there. I plan to start merging these
soon and to send out an atomisp pull-request for 6.15 well in time.
Regards,
Hans
next prev parent reply other threads:[~2025-04-03 10:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 20:25 [PATCH v2 0/9] platform/x86: int3472: Add handshake pin support Hans de Goede
2025-04-02 20:25 ` [PATCH v2 1/9] platform/x86: int3472: Add skl_int3472_register_clock() helper Hans de Goede
2025-04-02 20:25 ` [PATCH v2 2/9] platform/x86: int3472: Stop setting a supply-name for GPIO regulators Hans de Goede
2025-04-02 20:25 ` [PATCH v2 3/9] platform/x86: int3472: Drop unused gpio field from struct int3472_gpio_regulator Hans de Goede
2025-04-02 20:25 ` [PATCH v2 4/9] platform/x86: int3472: Rework AVDD second sensor quirk handling Hans de Goede
2025-04-02 21:10 ` Andy Shevchenko
2025-04-02 20:25 ` [PATCH v2 5/9] platform/x86: int3472: Make regulator supply name configurable Hans de Goede
2025-04-02 21:08 ` Andy Shevchenko
2025-04-02 20:25 ` [PATCH v2 6/9] platform/x86: int3472: Avoid GPIO regulator spikes Hans de Goede
2025-04-02 21:04 ` Andy Shevchenko
2025-04-03 9:43 ` Hans de Goede
2025-04-03 14:05 ` Andy Shevchenko
2025-04-02 20:25 ` [PATCH v2 7/9] platform/x86: int3472: Prepare for registering more then 1 GPIO regulator Hans de Goede
2025-04-02 20:59 ` Andy Shevchenko
2025-04-02 20:25 ` [PATCH v2 8/9] platform/x86: int3472: Add handshake pin support Hans de Goede
2025-04-02 20:56 ` Andy Shevchenko
2025-04-16 11:06 ` Hans de Goede
2025-04-16 13:09 ` Andy Shevchenko
2025-04-16 13:09 ` Andy Shevchenko
2025-04-16 13:13 ` Hans de Goede
2025-04-02 20:25 ` [PATCH v2 9/9] platform/x86: int3472: Debug log when remapping pins Hans de Goede
2025-04-02 20:51 ` Andy Shevchenko
2025-04-02 21:02 ` [PATCH v2 0/9] platform/x86: int3472: Add handshake pin support Andy Shevchenko
2025-04-03 10:30 ` Hans de Goede [this message]
2025-04-03 14:05 ` Andy Shevchenko
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=37de4bf2-c6c1-4d16-9f04-c0d9152dfe7b@redhat.com \
--to=hdegoede@redhat.com \
--cc=andy.shevchenko@gmail.com \
--cc=andy@kernel.org \
--cc=bingbu.cao@intel.com \
--cc=djrscally@gmail.com \
--cc=duanek@chorus.net \
--cc=hao.yao@intel.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-media@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=stern@rowland.harvard.edu \
/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