linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Loic Poulain <loic.poulain@linaro.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: robdclark@gmail.com, sean@poorly.run, robh+dt@kernel.org,
	devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	dri-devel@lists.freedesktop.org, bjorn.andersson@linaro.org
Subject: Re: [PATCH 1/2] drm/msm: add support for QCM2290 MDSS
Date: Wed, 19 Jan 2022 09:44:05 +0100	[thread overview]
Message-ID: <CAMZdPi8VLa4VEKk9BsO5i-cSA=itpUTBr6YoQN7Y7AE6Jugo_Q@mail.gmail.com> (raw)
In-Reply-To: <c37daeda-e58e-6a93-36aa-28e392bb06f2@linaro.org>

Hi Dmitry,

On Tue, 18 Jan 2022 at 19:02, Dmitry Baryshkov
<dmitry.baryshkov@linaro.org> wrote:
>
> On 18/01/2022 18:47, Loic Poulain wrote:
> > Add compatibility for QCM2290 display subsystem, including
> > required entries in DPU hw catalog.
> >
> > Signed-off-by: Loic Poulain <loic.poulain@linaro.org>
> > ---
> >   drivers/gpu/drm/msm/disp/dpu1/dpu_hw_catalog.c | 175 ++++++++++++++++++++++++-
> >   drivers/gpu/drm/msm/disp/dpu1/dpu_hw_catalog.h |   1 +
> >   drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c        |   1 +
> >   drivers/gpu/drm/msm/msm_drv.c                  |   1 +
> >   4 files changed, 177 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_hw_catalog.c b/drivers/gpu/drm/msm/disp/dpu1/dpu_hw_catalog.c
> > index ce6f32a..7fa3fc7 100644
> > --- a/drivers/gpu/drm/msm/disp/dpu1/dpu_hw_catalog.c
> > +++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_hw_catalog.c
> > @@ -25,6 +25,8 @@
> >   #define VIG_SM8250_MASK \
[...]
> > +static const struct dpu_vbif_cfg qcm2290_vbif[] = {
> > +     {
> > +     .name = "vbif_0", .id = VBIF_0,
> > +     .base = 0, .len = 0x1040,
> > +     .features = BIT(DPU_VBIF_QOS_REMAP),
> > +     .xin_halt_timeout = 0x4000,
> > +     .qos_rt_tbl = {
> > +             .npriority_lvl = ARRAY_SIZE(sdm845_rt_pri_lvl),
> > +             .priority_lvl = sdm845_rt_pri_lvl,
> > +             },
> > +     .memtype_count = 14,
> > +     .memtype = {3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3},
> > +     },
> > +};
>
> The only difference from sdm845_vbif is the lack of .qos_nrt_tbl. Is
> this on purpose?

Yes, I've not found any info related to non-rt for QCM2290 dpu, but I
assume it would be safe to just use sdm845_vbif here, as the others.

Regards,
Loic

      reply	other threads:[~2022-01-19  8:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-18 15:47 [PATCH 1/2] drm/msm: add support for QCM2290 MDSS Loic Poulain
2022-01-18 15:47 ` [PATCH 2/2] dt-bindings: msm: disp: add yaml schemas for QCM2290 DPU bindings Loic Poulain
2022-01-19  2:55   ` Rob Herring
2022-01-18 18:02 ` [PATCH 1/2] drm/msm: add support for QCM2290 MDSS Dmitry Baryshkov
2022-01-19  8:44   ` Loic Poulain [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='CAMZdPi8VLa4VEKk9BsO5i-cSA=itpUTBr6YoQN7Y7AE6Jugo_Q@mail.gmail.com' \
    --to=loic.poulain@linaro.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=robdclark@gmail.com \
    --cc=robh+dt@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).