From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Pin-yen Lin <treapking@chromium.org>,
Andrzej Hajda <andrzej.hajda@intel.com>,
Neil Armstrong <narmstrong@baylibre.com>,
Robert Foss <robert.foss@linaro.org>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Jonas Karlman <jonas@kwiboo.se>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>
Cc: linux-kernel@vger.kernel.org, Hermes Wu <hermes.wu@ite.com.tw>,
Allen Chen <allen.chen@ite.com.tw>,
Hsin-Yi Wang <hsinyi@chromium.org>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 2/2] drm/bridge: it6505: Add pre_enable/post_disable callback
Date: Mon, 3 Oct 2022 13:38:36 +0200 [thread overview]
Message-ID: <27115639-bfe4-4e8a-f557-57a26ccd042f@collabora.com> (raw)
In-Reply-To: <20221003050335.1007931-3-treapking@chromium.org>
Il 03/10/22 07:03, Pin-yen Lin ha scritto:
> Add atomic_pre_enable and atomic_post_disable callback to make sure the
> bridge is not powered off until atomic_post_disable is called. This
> prevents a power leakage when it6505 is powered off, but the upstream
> DRM bridge is still sending display signals.
>
> Fixes: b5c84a9edcd4 ("drm/bridge: add it6505 driver")
> Signed-off-by: Pin-yen Lin <treapking@chromium.org>
>
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
prev parent reply other threads:[~2022-10-03 11:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 5:03 [PATCH v2 0/2] drm/bridge: it6505: Power management fixes for it6505 bridge Pin-yen Lin
2022-10-03 5:03 ` [PATCH v2 1/2] drm/bridge: it6505: Adapt runtime power management framework Pin-yen Lin
2022-10-03 11:38 ` AngeloGioacchino Del Regno
2022-10-03 5:03 ` [PATCH v2 2/2] drm/bridge: it6505: Add pre_enable/post_disable callback Pin-yen Lin
2022-10-03 11:38 ` AngeloGioacchino Del Regno [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=27115639-bfe4-4e8a-f557-57a26ccd042f@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@linux.ie \
--cc=allen.chen@ite.com.tw \
--cc=andrzej.hajda@intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hermes.wu@ite.com.tw \
--cc=hsinyi@chromium.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.com \
--cc=robert.foss@linaro.org \
--cc=treapking@chromium.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;
as well as URLs for NNTP newsgroup(s).