All of lore.kernel.org
 help / color / mirror / Atom feed
From: Iago Toral <itoral@igalia.com>
To: Stefan Wahren <wahrenst@gmx.net>, Maira Canal <mcanal@igalia.com>,
	 dri-devel@lists.freedesktop.org
Cc: Nicolas Saenz Julienne <nsaenz@kernel.org>,
	Emma Anholt <emma@anholt.net>, Melissa Wen <mwen@igalia.com>,
	Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v2 2/4] drm/v3d: fix up register addresses for V3D 7.x
Date: Mon, 30 Oct 2023 11:14:53 +0100	[thread overview]
Message-ID: <7dbf5892f22b01ec3ef99dc1b261f68147fc9715.camel@igalia.com> (raw)
In-Reply-To: <613c4107-26c5-4d48-95c2-15ac8fcca33c@gmx.net>

Hi Stefan,

El lun, 30-10-2023 a las 10:58 +0100, Stefan Wahren escribió:
> Hi Iago,
> 
> Am 30.10.23 um 09:28 schrieb Iago Toral Quiroga:
> > This patch updates a number of register addresses that have
> > been changed in Raspberry Pi 5 (V3D 7.1) and updates the
> > code to use the corresponding registers and addresses based
> > on the actual V3D version.
> > 
> > v2:
> >   - added s-o-b and commit message. (Maíra Canal)
> >   - Used macro that takes version as argument and returns
> >     appropriate values instead of two different definitions
> >     for post-v71 and pre-v71 hardware when possible. (Maíra Canal)
> >   - fixed style warnings from checkpatch.pl. (Maíra Canal)
> > 
> > Signed-off-by: Iago Toral Quiroga <itoral@igalia.com>
> > ---
> >   drivers/gpu/drm/v3d/v3d_debugfs.c | 178 +++++++++++++++++--------
> > -----
> >   drivers/gpu/drm/v3d/v3d_gem.c     |   4 +-
> >   drivers/gpu/drm/v3d/v3d_irq.c     |  46 ++++----
> >   drivers/gpu/drm/v3d/v3d_regs.h    |  94 +++++++++-------
> >   drivers/gpu/drm/v3d/v3d_sched.c   |  38 ++++---
> >   5 files changed, 204 insertions(+), 156 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/v3d/v3d_debugfs.c
> > b/drivers/gpu/drm/v3d/v3d_debugfs.c
> > index 330669f51fa7..f843a50d5dce 100644
> > --- a/drivers/gpu/drm/v3d/v3d_debugfs.c
> > +++ b/drivers/gpu/drm/v3d/v3d_debugfs.c
> > @@ -12,69 +12,83 @@
> >   #include "v3d_drv.h"
> >   #include "v3d_regs.h"
> > 
> > -#define REGDEF(reg) { reg, #reg }
> > +#define REGDEF(min_ver, max_ver, reg) { min_ver, max_ver, reg,
> > #reg }
> >   struct v3d_reg_def {
> > +       u32 min_ver;
> > +       u32 max_ver;
> Is this documented some where which SoC has which V3D version?
> 

Not that I am aware of.

There are really only two Raspberry Pi SoCs supported by v3d: bcm2711
is Raspberry Pi 4 which is V3D 4.2 (compatible with 4.1), and bcm2712
is Raspberry Pi 5 which is V3D 7.1.

I don't know what SoCs are supported by versions of V3D before 4.1, I
think those were targetting set-top-box hardware that Emma used while
setting up the driver before the SoC for Raspberry Pi 4 was available.

Iago

  reply	other threads:[~2023-10-30 10:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-30  8:28 [PATCH v2 0/4] V3D module changes for Pi5 Iago Toral Quiroga
2023-10-30  8:28 ` [PATCH v2 1/4] drm/v3d: update UAPI to match user-space for V3D 7.x Iago Toral Quiroga
2023-10-30  8:28 ` [PATCH v2 2/4] drm/v3d: fix up register addresses " Iago Toral Quiroga
2023-10-30  9:58   ` Stefan Wahren
2023-10-30 10:14     ` Iago Toral [this message]
2023-10-30 10:28       ` Stefan Wahren
2023-10-30 10:30         ` Iago Toral
2023-10-30  8:28 ` [PATCH v2 3/4] dt-bindings: gpu: v3d: Add BCM2712's compatible Iago Toral Quiroga
2023-10-30  9:57   ` Stefan Wahren
2023-10-30 10:18     ` Iago Toral
2023-10-30 10:23       ` Stefan Wahren
2023-10-30 14:39   ` Krzysztof Kozlowski
2023-10-30  8:28 ` [PATCH v2 4/4] drm/v3d: add brcm,2712-v3d as a compatible V3D device Iago Toral Quiroga
2023-10-30 10:01   ` Stefan Wahren
2023-10-30 12:26 ` [PATCH v2 0/4] V3D module changes for Pi5 Maira Canal

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=7dbf5892f22b01ec3ef99dc1b261f68147fc9715.camel@igalia.com \
    --to=itoral@igalia.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emma@anholt.net \
    --cc=mcanal@igalia.com \
    --cc=mwen@igalia.com \
    --cc=nsaenz@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=wahrenst@gmx.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.