Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Dongcheng Yan <dongcheng.yan@intel.com>
Cc: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
	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,
	stable@vger.kernel.org, dongcheng.yan@linux.intel.com,
	hao.yao@intel.com
Subject: Re: [PATCH v3 1/2] platform/x86: int3472: add hpd pin support
Date: Mon, 28 Apr 2025 15:29:31 +0000	[thread overview]
Message-ID: <aA-e2zBMgb1OF-8U@kekkonen.localdomain> (raw)
In-Reply-To: <20250425104331.3165876-1-dongcheng.yan@intel.com>

Hi Dongcheng,

On Fri, Apr 25, 2025 at 06:43:30PM +0800, 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>

Thanks for the update.

Reviewed-by: Sakari Ailus <sakari.ailus@linux.intel.com>

-- 
Regards,

Sakari Ailus

  parent reply	other threads:[~2025-04-28 15:29 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
2025-04-28 14:16 ` Hans de Goede
2025-04-28 15:29 ` Sakari Ailus [this message]
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=aA-e2zBMgb1OF-8U@kekkonen.localdomain \
    --to=sakari.ailus@linux.intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=bingbu.cao@linux.intel.com \
    --cc=dongcheng.yan@intel.com \
    --cc=dongcheng.yan@linux.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=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