From: Robert Foss <robert.foss@linaro.org>
To: Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Andrzej Hajda <andrzej.hajda@intel.com>,
Pin-yen Lin <treapking@chromium.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Jonas Karlman <jonas@kwiboo.se>,
Jernej Skrabec <jernej.skrabec@gmail.com>
Cc: Robert Foss <robert.foss@linaro.org>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
linux-kernel@vger.kernel.org, allen chen <allen.chen@ite.com.tw>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/bridge: it6505: Add caching for EDID
Date: Thu, 15 Dec 2022 11:45:10 +0100 [thread overview]
Message-ID: <167110107985.909515.966397009406015766.b4-ty@linaro.org> (raw)
In-Reply-To: <20221115112720.911158-1-treapking@chromium.org>
On Tue, 15 Nov 2022 19:27:20 +0800, Pin-yen Lin wrote:
> Add caching when EDID is read, and invalidate the cache until the
> bridge detects HPD low or sink count changes on HPD_IRQ.
>
> It takes 1.2s for IT6505 bridge to read a 3-block EDID, and skipping
> one EDID read would be a notable difference on user experience.
>
>
> [...]
Applied, thanks!
Repo: https://cgit.freedesktop.org/drm/drm-misc/
[1/1] drm/bridge: it6505: Add caching for EDID
commit: 11feaef69d0cb81278294299bbfd86f94c2004e3
Rob
WARNING: multiple messages have this Message-ID (diff)
From: Robert Foss <robert.foss@linaro.org>
To: Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Andrzej Hajda <andrzej.hajda@intel.com>,
Pin-yen Lin <treapking@chromium.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Jonas Karlman <jonas@kwiboo.se>,
Jernej Skrabec <jernej.skrabec@gmail.com>
Cc: allen chen <allen.chen@ite.com.tw>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Robert Foss <robert.foss@linaro.org>
Subject: Re: [PATCH] drm/bridge: it6505: Add caching for EDID
Date: Thu, 15 Dec 2022 11:45:10 +0100 [thread overview]
Message-ID: <167110107985.909515.966397009406015766.b4-ty@linaro.org> (raw)
In-Reply-To: <20221115112720.911158-1-treapking@chromium.org>
On Tue, 15 Nov 2022 19:27:20 +0800, Pin-yen Lin wrote:
> Add caching when EDID is read, and invalidate the cache until the
> bridge detects HPD low or sink count changes on HPD_IRQ.
>
> It takes 1.2s for IT6505 bridge to read a 3-block EDID, and skipping
> one EDID read would be a notable difference on user experience.
>
>
> [...]
Applied, thanks!
Repo: https://cgit.freedesktop.org/drm/drm-misc/
[1/1] drm/bridge: it6505: Add caching for EDID
commit: 11feaef69d0cb81278294299bbfd86f94c2004e3
Rob
next prev parent reply other threads:[~2022-12-15 10:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 11:27 [PATCH] drm/bridge: it6505: Add caching for EDID Pin-yen Lin
2022-11-15 11:27 ` Pin-yen Lin
2022-12-13 15:51 ` Robert Foss
2022-12-13 15:51 ` Robert Foss
2022-12-14 16:51 ` Robert Foss
2022-12-14 16:51 ` Robert Foss
2022-12-15 8:36 ` Pin-yen Lin
2022-12-15 8:36 ` Pin-yen Lin
2022-12-15 10:29 ` Robert Foss
2022-12-15 10:29 ` Robert Foss
2022-12-15 10:45 ` Robert Foss [this message]
2022-12-15 10:45 ` Robert Foss
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=167110107985.909515.966397009406015766.b4-ty@linaro.org \
--to=robert.foss@linaro.org \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=allen.chen@ite.com.tw \
--cc=andrzej.hajda@intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.