From: abhinavk@codeaurora.org
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Clark <robdclark@gmail.com>, Sean Paul <sean@poorly.run>,
Jonathan Marek <jonathan@marek.ca>,
Stephen Boyd <sboyd@kernel.org>,
linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
David Airlie <airlied@linux.ie>,
freedreno@lists.freedesktop.org
Subject: Re: [PATCH v2 0/4] drm/msm: improve register snapshotting
Date: Tue, 27 Apr 2021 12:10:45 -0700 [thread overview]
Message-ID: <cffa1baab24ae7dd6f292726abfaf4d5@codeaurora.org> (raw)
In-Reply-To: <20210427001828.2375555-1-dmitry.baryshkov@linaro.org>
On 2021-04-26 17:18, Dmitry Baryshkov wrote:
> Rework MSM coredump support: add DSI PHY registers, simplify
> snapshotting code.
>
> Changes since v1:
> - Readd mutex serializing register snapshot calls
>
> - Add DSI PHY register dumping support
>
Need to mention the dependency here , got missed from the prev patchset
> ----------------------------------------------------------------
> Dmitry Baryshkov (4):
> drm/msm: pass dump state as a function argument
> drm/msm: make msm_disp_state transient data struct
> drm/msm: get rid of msm_iomap_size
> drm/msm/dsi: add DSI PHY registers to snapshot data
>
> drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c | 5 +-
> drivers/gpu/drm/msm/disp/msm_disp_snapshot.c | 90
> +++++++----------------
> drivers/gpu/drm/msm/disp/msm_disp_snapshot.h | 21 +-----
> drivers/gpu/drm/msm/disp/msm_disp_snapshot_util.c | 22 ++----
> drivers/gpu/drm/msm/dp/dp_display.c | 4 +-
> drivers/gpu/drm/msm/dsi/dsi.c | 5 +-
> drivers/gpu/drm/msm/dsi/dsi.h | 5 +-
> drivers/gpu/drm/msm/dsi/dsi_host.c | 11 +--
> drivers/gpu/drm/msm/dsi/phy/dsi_phy.c | 31 +++++++-
> drivers/gpu/drm/msm/dsi/phy/dsi_phy.h | 4 +
> drivers/gpu/drm/msm/msm_drv.c | 27 +++----
> drivers/gpu/drm/msm/msm_drv.h | 6 +-
> drivers/gpu/drm/msm/msm_kms.h | 8 +-
> 13 files changed, 97 insertions(+), 142 deletions(-)
>
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2021-04-27 19:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 0:18 [PATCH v2 0/4] drm/msm: improve register snapshotting Dmitry Baryshkov
2021-04-27 0:18 ` [PATCH v2 1/4] drm/msm: pass dump state as a function argument Dmitry Baryshkov
2021-04-27 0:18 ` [PATCH v2 2/4] drm/msm: make msm_disp_state transient data struct Dmitry Baryshkov
2021-04-27 19:19 ` [Freedreno] " abhinavk
2021-04-27 20:29 ` Dmitry Baryshkov
2021-04-27 22:11 ` abhinavk
2021-04-27 0:18 ` [PATCH v2 3/4] drm/msm: get rid of msm_iomap_size Dmitry Baryshkov
2021-04-27 19:29 ` [Freedreno] " abhinavk
2021-04-27 20:32 ` Dmitry Baryshkov
2021-04-27 22:12 ` abhinavk
2021-04-28 2:47 ` Bjorn Andersson
2021-04-28 13:41 ` Dmitry Baryshkov
2021-04-28 13:59 ` Bjorn Andersson
2021-04-28 14:03 ` Dmitry Baryshkov
2021-04-27 0:18 ` [PATCH v2 4/4] drm/msm/dsi: add DSI PHY registers to snapshot data Dmitry Baryshkov
2021-04-27 22:14 ` abhinavk
2021-04-27 19:10 ` abhinavk [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=cffa1baab24ae7dd6f292726abfaf4d5@codeaurora.org \
--to=abhinavk@codeaurora.org \
--cc=airlied@linux.ie \
--cc=bjorn.andersson@linaro.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=jonathan@marek.ca \
--cc=linux-arm-msm@vger.kernel.org \
--cc=robdclark@gmail.com \
--cc=sboyd@kernel.org \
--cc=sean@poorly.run \
/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).