From: Bingbu Cao <bingbu.cao@linux.intel.com>
To: Hao Yao <hao.yao@intel.com>,
Dan Scally <dan.scally@ideasonboard.com>,
djrscally@gmail.com, Hans de Goede <hdegoede@redhat.com>,
Sakari Ailus <sakari.ailus@intel.com>
Cc: Bingbu Cao <bingbu.cao@intel.com>,
platform-driver-x86@vger.kernel.org, linux-media@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH] platform/x86: int3472: Add handshake GPIO function
Date: Tue, 10 Oct 2023 15:17:50 +0800 [thread overview]
Message-ID: <38c9ff1c-8d3b-8675-9780-2bb6c87ba815@linux.intel.com> (raw)
In-Reply-To: <20231007021225.9240-1-hao.yao@intel.com>
Hao,
On 10/7/23 10:12 AM, Hao Yao wrote:
> Handshake pin is used for Lattice MIPI aggregator to enable the
> camera sensor. After pulled up, recommend to wail ~250ms to get
> everything ready.
Is the delay for specific camera or requirement from Lattice.
250ms is bad for camera.
>
> Signed-off-by: Hao Yao <hao.yao@intel.com>
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> drivers/platform/x86/intel/int3472/common.h | 1 +
> drivers/platform/x86/intel/int3472/discrete.c | 5 +++++
> 2 files changed, 6 insertions(+)
>
> diff --git a/drivers/platform/x86/intel/int3472/common.h b/drivers/platform/x86/intel/int3472/common.h
> index 655ae3ec0593..3ad4c72afb45 100644
> --- a/drivers/platform/x86/intel/int3472/common.h
> +++ b/drivers/platform/x86/intel/int3472/common.h
> @@ -23,6 +23,7 @@
> #define INT3472_GPIO_TYPE_POWER_ENABLE 0x0b
> #define INT3472_GPIO_TYPE_CLK_ENABLE 0x0c
> #define INT3472_GPIO_TYPE_PRIVACY_LED 0x0d
> +#define INT3472_GPIO_TYPE_HANDSHAKE 0x12
>
> #define INT3472_PDEV_MAX_NAME_LEN 23
> #define INT3472_MAX_SENSOR_GPIOS 3
> diff --git a/drivers/platform/x86/intel/int3472/discrete.c b/drivers/platform/x86/intel/int3472/discrete.c
> index b644ce65c990..4753161b4080 100644
> --- a/drivers/platform/x86/intel/int3472/discrete.c
> +++ b/drivers/platform/x86/intel/int3472/discrete.c
> @@ -111,6 +111,10 @@ static void int3472_get_func_and_polarity(u8 type, const char **func, u32 *polar
> *func = "power-enable";
> *polarity = GPIO_ACTIVE_HIGH;
> break;
> + case INT3472_GPIO_TYPE_HANDSHAKE:
> + *func = "handshake";
> + *polarity = GPIO_ACTIVE_HIGH;
> + break;
> default:
> *func = "unknown";
> *polarity = GPIO_ACTIVE_HIGH;
> @@ -201,6 +205,7 @@ static int skl_int3472_handle_gpio_resources(struct acpi_resource *ares,
> switch (type) {
> case INT3472_GPIO_TYPE_RESET:
> case INT3472_GPIO_TYPE_POWERDOWN:
> + case INT3472_GPIO_TYPE_HANDSHAKE:
> ret = skl_int3472_map_gpio_to_sensor(int3472, agpio, func, polarity);
> if (ret)
> err_msg = "Failed to map GPIO pin to sensor\n";
>
--
Best regards,
Bingbu Cao
next prev parent reply other threads:[~2023-10-10 7:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-07 2:12 [PATCH] platform/x86: int3472: Add handshake GPIO function Hao Yao
2023-10-10 7:17 ` Bingbu Cao [this message]
2023-10-10 7:53 ` Hao Yao
2023-10-12 12:22 ` Hans de Goede
2023-11-27 7:31 ` Hao Yao
2024-03-31 10:51 ` Anthony I Gilea
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=38c9ff1c-8d3b-8675-9780-2bb6c87ba815@linux.intel.com \
--to=bingbu.cao@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bingbu.cao@intel.com \
--cc=dan.scally@ideasonboard.com \
--cc=djrscally@gmail.com \
--cc=hao.yao@intel.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