dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Wahren <stefan.wahren@i2se.com>
To: Maxime Ripard <maxime@cerno.tech>
Cc: Nicolas Saenz Julienne <nsaenz@kernel.org>,
	Emma Anholt <emma@anholt.net>, David Airlie <airlied@linux.ie>,
	dri-devel@lists.freedesktop.org,
	Nathan Chancellor <nathan@kernel.org>
Subject: Re: [PATCH RFC] drm/vc4: hdmi: Fix connector detect logic
Date: Tue, 6 Jul 2021 17:45:27 +0200	[thread overview]
Message-ID: <0ca8564a-03b8-e13f-b4c2-468bac877e4f@i2se.com> (raw)
In-Reply-To: <20210706132131.4bylrs5u2xmypjcy@gilmour>

Hi Maxime,

Am 06.07.21 um 15:21 schrieb Maxime Ripard:
> Hi Stefan,
>
> On Tue, Jul 06, 2021 at 12:48:05PM +0200, Stefan Wahren wrote:
>> Am 06.07.21 um 11:58 schrieb Maxime Ripard:
>>> Hi,
>>>
>>> On Mon, Jul 05, 2021 at 11:36:34PM +0200, Stefan Wahren wrote:
>>>> Commit "drm/vc4: hdmi: Convert to gpiod" changes the behavior of
>>>> vc4_hdmi_connector_detect() which results into CPU hangs in case there
>>>> is no HDMI connected. Let's restore the old behavior.
>>>>
>>>> Reported-by: Nathan Chancellor <nathan@kernel.org>
>>>> Reported-by: Ojaswin Mujoo <ojaswin98@gmail.com>
>>>> Fixes: 6800234ceee0 ("drm/vc4: hdmi: Convert to gpiod")
>>>> Signed-off-by: Stefan Wahren <stefan.wahren@i2se.com>
>>> I already sent this patch last week:
>>>
>>> https://lore.kernel.org/dri-devel/20210628124257.140453-3-maxime@cerno.tech/
>> oops, i only looked in the July archive.
>>
>>> I'm not entirely sure how this could create a CPU hang though. Withouth
>>> this patch, if the HPD GPIO is low, we would first try to retrieve the
>>> EDID, and then if it doesn't we would read the hotplug register.
>> Yes, the real issue has been revealed by the original change and this
>> patch only "hides" it again.
>>> The first is using a separate i2c controller (and even if it was in the
>>> same power domain, we have the pm_runtime_resume call), and the register
>>> read should be fine too?
>> Sorry, i don't have a clue and time for further investigations.
>>
>> Does it mean, you are not able to reproduce this issue?
> On next-20210706 at least it works fine for me without an HDMI monitor
> connected, yes:

which configuration do you use? Did you tried arm/multi_v7_defconfig?

I tried yesterday mainline ("a180bd1d7e16173d965b263c5a536aa40afa2a2a")
with multi_v7_defconfig and the issue was there.



  reply	other threads:[~2021-07-06 15:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-05 21:36 [PATCH RFC] drm/vc4: hdmi: Fix connector detect logic Stefan Wahren
2021-07-06  9:58 ` Maxime Ripard
2021-07-06 10:48   ` Stefan Wahren
2021-07-06 13:21     ` Maxime Ripard
2021-07-06 15:45       ` Stefan Wahren [this message]
2021-07-07 13:11         ` Maxime Ripard
2021-07-07 18:01           ` Stefan Wahren
2021-07-16 15:49             ` Maxime Ripard

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=0ca8564a-03b8-e13f-b4c2-468bac877e4f@i2se.com \
    --to=stefan.wahren@i2se.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emma@anholt.net \
    --cc=maxime@cerno.tech \
    --cc=nathan@kernel.org \
    --cc=nsaenz@kernel.org \
    /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