From: Dmitry Osipenko <digetx@gmail.com>
To: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>
Cc: 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>,
linux-tegra@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v15 2/2] drm/tegra: dc: Extend debug stats with total number of events
Date: Wed, 17 Mar 2021 20:44:15 +0300 [thread overview]
Message-ID: <c68ea34c-6b9f-61ce-a58a-8def27a1127a@gmail.com> (raw)
In-Reply-To: <20210314221130.GB2733@qmqm.qmqm.pl>
15.03.2021 01:11, Michał Mirosław пишет:
> On Thu, Mar 11, 2021 at 08:22:55PM +0300, Dmitry Osipenko wrote:
>> It's useful to know the total number of underflow events and currently
>> the debug stats are getting reset each time CRTC is being disabled. Let's
>> account the overall number of events that doesn't get a reset.
> [...]
>
> Looks good. It seems independent from the other patch.
>
> Reviewed-by: Michał Mirosław <mirq-linux@rere.qmqm.pl>
>
This patch was created in order to help with debugging of the bandwidth
management, but technically it's independent. Thank you for the review.
prev parent reply other threads:[~2021-03-17 17:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 17:22 [PATCH v15 0/2] Add memory bandwidth management to NVIDIA Tegra DRM driver Dmitry Osipenko
2021-03-11 17:22 ` [PATCH v15 1/2] drm/tegra: dc: Support memory bandwidth management Dmitry Osipenko
2021-03-14 22:31 ` Michał Mirosław
2021-03-15 18:39 ` Dmitry Osipenko
2021-03-16 22:56 ` Dmitry Osipenko
2021-03-11 17:22 ` [PATCH v15 2/2] drm/tegra: dc: Extend debug stats with total number of events Dmitry Osipenko
2021-03-14 22:11 ` Michał Mirosław
2021-03-17 17:44 ` 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=c68ea34c-6b9f-61ce-a58a-8def27a1127a@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;
as well as URLs for NNTP newsgroup(s).