Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Abhinav Kumar <quic_abhinavk@quicinc.com>,
	Rob Clark <robdclark@gmail.com>, Sean Paul <sean@poorly.run>
Cc: Stephen Boyd <swboyd@chromium.org>,
	David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
	Bjorn Andersson <andersson@kernel.org>,
	linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
	freedreno@lists.freedesktop.org
Subject: Re: [PATCH v2 1/2] drm/msm/dpu: drop the regdma configuration
Date: Fri, 21 Apr 2023 20:50:38 +0300	[thread overview]
Message-ID: <73e49bab-78a7-1fc2-e521-ede5429ed62e@linaro.org> (raw)
In-Reply-To: <911e0a6e-eae4-8f98-8247-f6b2e8a0aeb9@quicinc.com>

On 21/04/2023 20:46, Abhinav Kumar wrote:
> 
> 
> On 4/20/2023 3:25 PM, Dmitry Baryshkov wrote:
>> The regdma is currently not used by the current driver. We have no way
>> to practically verify that the regdma is described correctly. Drop it
>> now.
>>
>> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
>> ---
> 
> As Marijn noted, perhaps we can drop even DPU_CLK_CTRL_REG_DMA. But you 
> can add that separately, hence

I'd say it's not worth the trouble.

> 
> Reviewed-by: Abhinav Kumar <quic_abhinavk@quicinc.com>

-- 
With best wishes
Dmitry


      reply	other threads:[~2023-04-21 17:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-20 22:25 [PATCH v2 1/2] drm/msm/dpu: drop the regdma configuration Dmitry Baryshkov
2023-04-20 22:25 ` [PATCH v2 2/2] drm/msm/dpu: stop mapping the regdma region Dmitry Baryshkov
2023-04-21  7:35   ` Marijn Suijten
2023-04-21 17:49     ` Dmitry Baryshkov
2023-04-21 17:48   ` Abhinav Kumar
2023-04-21  7:34 ` [PATCH v2 1/2] drm/msm/dpu: drop the regdma configuration Marijn Suijten
2023-04-21 17:46 ` Abhinav Kumar
2023-04-21 17:50   ` Dmitry Baryshkov [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=73e49bab-78a7-1fc2-e521-ede5429ed62e@linaro.org \
    --to=dmitry.baryshkov@linaro.org \
    --cc=airlied@gmail.com \
    --cc=andersson@kernel.org \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --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