From: Vinod Koul <vkoul@kernel.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>,
Abhinav Kumar <quic_abhinavk@quicinc.com>,
kernel test robot <lkp@intel.com>,
David Airlie <airlied@linux.ie>,
linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
Stephen Boyd <swboyd@chromium.org>,
Daniel Vetter <daniel@ffwll.ch>,
freedreno@lists.freedesktop.org
Subject: Re: [Freedreno] [PATCH v2] drm/msm/dsi: use RMW cycles in dsi_update_dsc_timing
Date: Wed, 4 May 2022 19:01:48 +0530 [thread overview]
Message-ID: <YnKARNKFBuEx+Xli@matsya> (raw)
In-Reply-To: <20220430175533.3817792-1-dmitry.baryshkov@linaro.org>
On 30-04-22, 20:55, Dmitry Baryshkov wrote:
> The downstream uses read-modify-write for updating command mode
> compression registers. Let's follow this approach. This also fixes the
> following warning:
>
> drivers/gpu/drm/msm/dsi/dsi_host.c:918:23: warning: variable 'reg_ctrl' set but not used [-Wunused-but-set-variable]
Reviewed-by: Vinod Koul <vkoul@kernel.org>
Tested on pixel3:
Tested-by: Vinod Koul <vkoul@kernel.org>
--
~Vinod
prev parent reply other threads:[~2022-05-04 13:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-30 17:55 [PATCH v2] drm/msm/dsi: use RMW cycles in dsi_update_dsc_timing Dmitry Baryshkov
2022-04-30 18:42 ` Abhinav Kumar
2022-04-30 18:58 ` Marijn Suijten
2022-04-30 19:25 ` [Freedreno] " Abhinav Kumar
2022-05-01 20:06 ` Marijn Suijten
2022-05-01 23:56 ` Abhinav Kumar
2022-05-02 8:02 ` Dmitry Baryshkov
2022-05-02 8:34 ` Marijn Suijten
2022-05-02 10:02 ` Dmitry Baryshkov
2022-05-02 21:56 ` Marijn Suijten
2022-04-30 19:28 ` Dmitry Baryshkov
2022-05-01 20:41 ` Marijn Suijten
2022-05-01 22:44 ` Dmitry Baryshkov
2022-05-02 8:43 ` Marijn Suijten
2022-05-02 9:41 ` Dmitry Baryshkov
2022-05-02 21:53 ` Marijn Suijten
2022-05-04 13:41 ` [Freedreno] " Vinod Koul
2022-05-04 13:38 ` Vinod Koul
2022-05-04 13:35 ` Vinod Koul
2022-05-04 13:31 ` Vinod Koul [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=YnKARNKFBuEx+Xli@matsya \
--to=vkoul@kernel.org \
--cc=airlied@linux.ie \
--cc=bjorn.andersson@linaro.org \
--cc=daniel@ffwll.ch \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=lkp@intel.com \
--cc=quic_abhinavk@quicinc.com \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
--cc=swboyd@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).