From: Markus Elfring <Markus.Elfring@web.de>
To: Kuro Chung <kuro.chung@ite.corp-partner.google.com>,
dri-devel@lists.freedesktop.org, kernel-janitors@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrzej Hajda <andrzej.hajda@intel.com>,
Angelo Gioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Allen Chen <allen.chen@ite.com.tw>,
Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@gmail.com>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Jonas Karlman <jonas@kwiboo.se>,
Kenneth Haung <kenneth.hung@ite.com.tw>,
Kuro Chung <kuro.chung@ite.com.tw>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Pin-yen Lin <treapking@chromium.org>,
Robert Foss <rfoss@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>
Subject: Re: [PATCH v9] drm/bridge: it6505: This patch fixes hibernate to resume no display issue
Date: Fri, 17 May 2024 20:30:49 +0200 [thread overview]
Message-ID: <94ef2d0b-15d0-4c40-ab52-a5d88a666b3c@web.de> (raw)
In-Reply-To: <20240517021654.1034218-1-kuro.chung@ite.com.tw>
Please omit the word combination “This patch” from the summary phrase.
…
> But the input FIFO reset will also trigger error interrupts of output
> module rising.Thus, it6505 have to wait a period can clear those
> expected error interrupts caused by manual hardware reset in one
> interrupt handler calling to avoid interrupt looping.
Please improve this change description another bit.
…
> ---
> drivers/gpu/drm/bridge/ite-it6505.c | 73 +++++++++++++++++++----------
…
You may present version descriptions behind the marker line.
Regards,
Markus
prev parent reply other threads:[~2024-05-17 18:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 2:16 kuro
2024-05-17 10:37 ` AngeloGioacchino Del Regno
2024-05-17 18:30 ` Markus Elfring [this message]
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=94ef2d0b-15d0-4c40-ab52-a5d88a666b3c@web.de \
--to=markus.elfring@web.de \
--cc=airlied@gmail.com \
--cc=allen.chen@ite.com.tw \
--cc=andrzej.hajda@intel.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=kenneth.hung@ite.com.tw \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuro.chung@ite.com.tw \
--cc=kuro.chung@ite.corp-partner.google.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=treapking@chromium.org \
--cc=tzimmermann@suse.de \
/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®