From: "Yan, Dongcheng" <dongcheng.yan@linux.intel.com>
To: Dongcheng Yan <dongcheng.yan@intel.com>,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
sakari.ailus@linux.intel.com, hverkuil@xs4all.nl,
andriy.shevchenko@linux.intel.com, hdegoede@redhat.com,
u.kleine-koenig@baylibre.com, ricardo.ribalda@gmail.com,
bingbu.cao@linux.intel.com
Cc: stable@vger.kernel.org, hao.yao@intel.com
Subject: Re: [PATCH v3 1/2] platform/x86: int3472: add hpd pin support
Date: Fri, 25 Apr 2025 18:54:06 +0800 [thread overview]
Message-ID: <3da17cf1-f489-42af-aef5-a7a9f800fe17@linux.intel.com> (raw)
In-Reply-To: <20250425104331.3165876-1-dongcheng.yan@intel.com>
Hi reviewers,
I'm sorry for that I forget to rm cc:stable@vger.kernel.org in maillist
Best Regards,
Dongcheng
On 4/25/2025 6:43 PM, Dongcheng Yan wrote:
> Typically HDMI to MIPI CSI-2 bridges have a pin to signal image data is
> being received. On the host side this is wired to a GPIO for polling or
> interrupts. This includes the Lontium HDMI to MIPI CSI-2 bridges
> lt6911uxe and lt6911uxc.
>
> The GPIO "hpd" is used already by other HDMI to CSI-2 bridges, use it
> here as well.
>
> Signed-off-by: Dongcheng Yan <dongcheng.yan@intel.com>
> ---
> drivers/platform/x86/intel/int3472/common.h | 1 +
> drivers/platform/x86/intel/int3472/discrete.c | 6 ++++++
> 2 files changed, 7 insertions(+)
>
> diff --git a/drivers/platform/x86/intel/int3472/common.h b/drivers/platform/x86/intel/int3472/common.h
> index 51b818e62a25..4593d567caf4 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_CLK_ENABLE 0x0c
> #define INT3472_GPIO_TYPE_PRIVACY_LED 0x0d
> #define INT3472_GPIO_TYPE_HANDSHAKE 0x12
> +#define INT3472_GPIO_TYPE_HOTPLUG_DETECT 0x13
>
> #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 394975f55d64..efa3bc7af193 100644
> --- a/drivers/platform/x86/intel/int3472/discrete.c
> +++ b/drivers/platform/x86/intel/int3472/discrete.c
> @@ -191,6 +191,10 @@ static void int3472_get_con_id_and_polarity(struct int3472_discrete_device *int3
> *con_id = "privacy-led";
> *gpio_flags = GPIO_ACTIVE_HIGH;
> break;
> + case INT3472_GPIO_TYPE_HOTPLUG_DETECT:
> + *con_id = "hpd";
> + *gpio_flags = GPIO_ACTIVE_HIGH;
> + break;
> case INT3472_GPIO_TYPE_POWER_ENABLE:
> *con_id = "avdd";
> *gpio_flags = GPIO_ACTIVE_HIGH;
> @@ -221,6 +225,7 @@ static void int3472_get_con_id_and_polarity(struct int3472_discrete_device *int3
> * 0x0b Power enable
> * 0x0c Clock enable
> * 0x0d Privacy LED
> + * 0x13 Hotplug detect
> *
> * There are some known platform specific quirks where that does not quite
> * hold up; for example where a pin with type 0x01 (Power down) is mapped to
> @@ -290,6 +295,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_HOTPLUG_DETECT:
> ret = skl_int3472_map_gpio_to_sensor(int3472, agpio, con_id, gpio_flags);
> if (ret)
> err_msg = "Failed to map GPIO pin to sensor\n";
>
> base-commit: 4d1e8c8f11c611db5828e4bae7292bc295eea8ef
next prev parent reply other threads:[~2025-04-25 10:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 10:43 [PATCH v3 1/2] platform/x86: int3472: add hpd pin support Dongcheng Yan
2025-04-25 10:43 ` [PATCH v3 2/2] media: i2c: change lt6911uxe irq_gpio name to "hpd" Dongcheng Yan
2025-04-25 10:51 ` [PATCH v3 1/2] platform/x86: int3472: add hpd pin support kernel test robot
2025-04-25 10:54 ` Yan, Dongcheng [this message]
2025-04-28 14:16 ` Hans de Goede
2025-04-28 15:29 ` Sakari Ailus
2025-07-02 10:19 ` Ilpo Järvinen
2025-07-02 10:23 ` Yan, Dongcheng
2025-07-02 10:53 ` Sakari Ailus
2025-07-02 11:09 ` Ilpo Järvinen
2025-07-02 11:22 ` Sakari Ailus
2025-07-02 11:48 ` Andy Shevchenko
2025-07-03 3:09 ` Yan, Dongcheng
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=3da17cf1-f489-42af-aef5-a7a9f800fe17@linux.intel.com \
--to=dongcheng.yan@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bingbu.cao@linux.intel.com \
--cc=dongcheng.yan@intel.com \
--cc=hao.yao@intel.com \
--cc=hdegoede@redhat.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=ricardo.ribalda@gmail.com \
--cc=sakari.ailus@linux.intel.com \
--cc=stable@vger.kernel.org \
--cc=u.kleine-koenig@baylibre.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