From: Dmitry Osipenko <digetx@gmail.com>
To: "Thierry Reding" <thierry.reding@gmail.com>,
"Jonathan Hunter" <jonathanh@nvidia.com>,
"Matt Merhar" <mattmerhar@protonmail.com>,
"Peter Geis" <pgwipeout@gmail.com>,
"Nicolas Chauvet" <kwizart@gmail.com>,
"Michał Mirosław" <mirq-linux@rere.qmqm.pl>
Cc: linux-tegra@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v14 0/2] Add memory bandwidth management to NVIDIA Tegra DRM driver
Date: Thu, 11 Mar 2021 20:09:28 +0300 [thread overview]
Message-ID: <be8ed07b-3301-f64f-a599-9bba40d42288@gmail.com> (raw)
In-Reply-To: <20210311170606.7543-1-digetx@gmail.com>
11.03.2021 20:06, Dmitry Osipenko пишет:
> This series adds memory bandwidth management to the NVIDIA Tegra DRM driver,
> which is done using interconnect framework. It fixes display corruption that
> happens due to insufficient memory bandwidth.
>
> Changelog:
>
> v14: - Made improvements that were suggested by Michał Mirosław to v13:
>
> - Changed 'unsigned int' to 'bool'.
> - Renamed functions which calculate bandwidth state.
> - Reworked comment in the code that explains why downscaled plane
> require higher bandwidth.
> - Added round-up to bandwidth calculation.
> - Added sanity checks of the plane index and fixed out-of-bounds
> access which happened on T124 due to the cursor plane index.
>
> v13: - No code changes. Patches missed v5.12, re-sending them for v5.13.
>
> Dmitry Osipenko (2):
> drm/tegra: dc: Support memory bandwidth management
> drm/tegra: dc: Extend debug stats with total number of events
>
> drivers/gpu/drm/tegra/Kconfig | 1 +
> drivers/gpu/drm/tegra/dc.c | 362 ++++++++++++++++++++++++++++++++++
> drivers/gpu/drm/tegra/dc.h | 19 ++
> drivers/gpu/drm/tegra/drm.c | 14 ++
> drivers/gpu/drm/tegra/hub.c | 3 +
> drivers/gpu/drm/tegra/plane.c | 127 ++++++++++++
> drivers/gpu/drm/tegra/plane.h | 15 ++
> 7 files changed, 541 insertions(+)
>
Michał, please let me know if v14 looks good to you. I'll appreciate
yours r-b, thanks in advance.
prev parent reply other threads:[~2021-03-11 17:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 17:06 Dmitry Osipenko
2021-03-11 17:06 ` [PATCH v14 1/2] drm/tegra: dc: Support memory bandwidth management Dmitry Osipenko
2021-03-11 17:12 ` Dmitry Osipenko
2021-03-11 17:06 ` [PATCH v14 2/2] drm/tegra: dc: Extend debug stats with total number of events Dmitry Osipenko
2021-03-11 17:09 ` Dmitry Osipenko [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=be8ed07b-3301-f64f-a599-9bba40d42288@gmail.com \
--to=digetx@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jonathanh@nvidia.com \
--cc=kwizart@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mattmerhar@protonmail.com \
--cc=mirq-linux@rere.qmqm.pl \
--cc=pgwipeout@gmail.com \
--cc=thierry.reding@gmail.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
all inboxes | Powered by JetHome®