From: Dongcheng Yan <dongcheng.yan@intel.com>
To: 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, dongcheng.yan@linux.intel.com, hao.yao@intel.com
Subject: [PATCH v1 2/2] media: i2c: change lt6911uxe irq_gpio name to "hpd"
Date: Fri, 11 Apr 2025 16:23:57 +0800 [thread overview]
Message-ID: <20250411082357.392713-2-dongcheng.yan@intel.com> (raw)
In-Reply-To: <20250411082357.392713-1-dongcheng.yan@intel.com>
lt6911uxe is used in IPU6 / x86 platform, worked with an out-of-tree
int3472 patch and upstream intel/ipu6 before.
The upstream int3472 driver uses "hpd" instead of "readystat" now.
this patch updates the irq_gpio name to "hpd" accordingly, so that
mere users can now use the upstream version directly without relying
on out-of-tree int3472 pin support.
The new name "hpd" (Hotplug Detect) aligns with common naming
conventions used in other drivers(like adv7604) and documentation.
Fixes: e49563c3be09d4 ("media: i2c: add lt6911uxe hdmi bridge driver")
Cc: stable@vger.kernel.org
Signed-off-by: Dongcheng Yan <dongcheng.yan@intel.com>
---
drivers/media/i2c/lt6911uxe.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/media/i2c/lt6911uxe.c b/drivers/media/i2c/lt6911uxe.c
index c5b40bb58a37..24857d683fcf 100644
--- a/drivers/media/i2c/lt6911uxe.c
+++ b/drivers/media/i2c/lt6911uxe.c
@@ -605,10 +605,10 @@ static int lt6911uxe_probe(struct i2c_client *client)
return dev_err_probe(dev, PTR_ERR(lt6911uxe->reset_gpio),
"failed to get reset gpio\n");
- lt6911uxe->irq_gpio = devm_gpiod_get(dev, "readystat", GPIOD_IN);
+ lt6911uxe->irq_gpio = devm_gpiod_get(dev, "hpd", GPIOD_IN);
if (IS_ERR(lt6911uxe->irq_gpio))
return dev_err_probe(dev, PTR_ERR(lt6911uxe->irq_gpio),
- "failed to get ready_stat gpio\n");
+ "failed to get hpd gpio\n");
ret = lt6911uxe_fwnode_parse(lt6911uxe, dev);
if (ret)
--
2.34.1
next prev parent reply other threads:[~2025-04-11 8:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 8:23 [PATCH v1 1/2] platform/x86: int3472: add hpd pin support Dongcheng Yan
2025-04-11 8:23 ` Dongcheng Yan [this message]
2025-04-11 8:34 ` [PATCH v1 2/2] media: i2c: change lt6911uxe irq_gpio name to "hpd" Hans de Goede
2025-04-14 7:54 ` Yan, Dongcheng
2025-04-11 8:33 ` [PATCH v1 1/2] platform/x86: int3472: add hpd pin support Hans de Goede
2025-04-14 7:52 ` Yan, Dongcheng
2025-04-14 8:11 ` Andy Shevchenko
2025-04-14 8:40 ` Yan, Dongcheng
2025-04-14 8:49 ` Andy Shevchenko
2025-04-14 9:59 ` Yan, Dongcheng
2025-04-14 11:04 ` Hans de Goede
2025-04-14 11:09 ` Hans de Goede
2025-04-14 11:43 ` Sakari Ailus
2025-04-14 12:21 ` Hans de Goede
2025-04-14 12:32 ` Sakari Ailus
2025-04-14 12:37 ` Hans de Goede
2025-04-14 12:54 ` Sakari Ailus
2025-04-14 14:24 ` Hans de Goede
2025-04-14 8:52 ` Sakari Ailus
2025-04-14 10:01 ` 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=20250411082357.392713-2-dongcheng.yan@intel.com \
--to=dongcheng.yan@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bingbu.cao@linux.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=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