From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: "Yan, Dongcheng" <dongcheng.yan@intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
"Yan, Dongcheng" <dongcheng.yan@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
hverkuil@xs4all.nl, u.kleine-koenig@baylibre.com,
ricardo.ribalda@gmail.com, bingbu.cao@linux.intel.com,
hao.yao@intel.com
Subject: Re: [PATCH v1 1/2] platform/x86: int3472: add hpd pin support
Date: Mon, 14 Apr 2025 11:43:30 +0000 [thread overview]
Message-ID: <Z_z04jMiTg_xW-c2@kekkonen.localdomain> (raw)
In-Reply-To: <9dc86b0c-b63c-447d-aa2f-953fbccb1d27@redhat.com>
Hans, Dongcheng,
On Mon, Apr 14, 2025 at 01:09:47PM +0200, Hans de Goede wrote:
> Hi,
>
> On 14-Apr-25 13:04, Hans de Goede wrote:
> > Hi,
> >
> > On 14-Apr-25 11:59, Yan, Dongcheng wrote:
> >> Hi Andy and Hans,
> >>
> >> I found the description of lt6911uxe's GPIO in the spec:
> >> GPIO5 is used as the interrupt signal (50ms low level) to inform SOC
> >> start reading registers from 6911UXE;
> >>
> >> So setting the polarity as GPIO_ACTIVE_LOW is acceptable?
> >
> > Yes that is acceptable, thank you for looking this up.
>
> p.s.
>
> Note that setting GPIO_ACTIVE_LOW will invert the values returned
> by gpiod_get_value(), so if the driver uses that you will need
> to fix this in the driver.
>
> Hmm, thinking more about this, I just realized that this is an
> input pin to the CPU, not an output pin like all other pins
> described by the INT3472 device. I missed that as first.
>
> In that case using GPIO_LOOKUP_FLAGS_DEFAULT as before probably
> makes the most sense. Please add a comment that this is an input
> pin to the INT3472 patch and keep GPIO_LOOKUP_FLAGS_DEFAULT for
> the next version.
The GPIO_LOOKUP_FLAGS_DEFAULT is the "Linux default", not the hardware or
firmware default so I don't think it's relevant in this context. There's a
single non-GPIO bank driver using it, probably mistakenly.
I'd also use GPIO_ACTIVE_LOW, for the reason Dongcheng pointed to above.
--
Regards,
Sakari Ailus
next prev parent reply other threads:[~2025-04-14 11:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 8:23 Dongcheng Yan
2025-04-11 8:23 ` [PATCH v1 2/2] media: i2c: change lt6911uxe irq_gpio name to "hpd" Dongcheng Yan
2025-04-11 8:34 ` 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 [this message]
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=Z_z04jMiTg_xW-c2@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=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
all inboxes | Powered by JetHome®