From: Krzysztof Kozlowski <krzk@kernel.org>
To: Linus Walleij <linusw@kernel.org>
Cc: David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Hans Ulli Kroll <ulli.kroll@googlemail.com>,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: display: faraday,tve200: Use a level-high interrupt
Date: Sun, 27 Sep 2026 19:42:00 +0200 [thread overview]
Message-ID: <20260927-steady-infrared-penguin-baa4fb@quoll> (raw)
In-Reply-To: <20260921-gemini-tve200-fix-v1-1-8be03ac2a8f7@kernel.org>
On Mon, Sep 21, 2026 at 11:15:54AM +0200, Linus Walleij wrote:
> The TVE200 vertical interrupt can remain pending after acknowledgment.
> Using rising-edge triggering can leave it unserviced when no new edge
> is generated, causing vblank and page-flip timeouts on the D-Link DIR-685.
>
> Use level-high triggering in the binding example so a pending interrupt
> is delivered again without requiring a new edge.
>
> Fixes: 8b17e80d9e46 ("drm/tve200: Add DT bindings")
Example has no impact beside validation, thus no bug to fix here,
really.
> Assisted-by: LLM
> Signed-off-by: Linus Walleij <linusw@kernel.org>
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-09-27 17:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 9:15 [PATCH 0/2] Fix Gemini TVE200 interrupt triggering Linus Walleij
2026-09-21 9:15 ` [PATCH 1/2] dt-bindings: display: faraday,tve200: Use a level-high interrupt Linus Walleij
2026-09-27 17:42 ` Krzysztof Kozlowski [this message]
2026-09-28 13:17 ` Rob Herring (Arm)
2026-09-28 13:19 ` Linus Walleij
2026-09-21 9:15 ` [PATCH 2/2] ARM: dts: gemini: Use a level-high interrupt for TVE200 Linus Walleij
2026-09-21 9:25 ` sashiko-bot
2026-09-22 12:16 ` Linus Walleij
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=20260927-steady-infrared-penguin-baa4fb@quoll \
--to=krzk@kernel.org \
--cc=airlied@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=robh@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=ulli.kroll@googlemail.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