From: Doug Brown <doug@schmorgal.com>
To: Lucas Stach <l.stach@pengutronix.de>,
Russell King <linux+etnaviv@armlinux.org.uk>,
Christian Gmeiner <christian.gmeiner@gmail.com>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>
Cc: Doug Brown <doug@schmorgal.com>,
etnaviv@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: [PATCH 0/2] drm/etnaviv: GC300 fixes
Date: Fri, 2 Sep 2022 23:05:56 -0700 [thread overview]
Message-ID: <20220903060558.55167-1-doug@schmorgal.com> (raw)
This series contains a few special cases for supporting the GC300
properly. These were found in the drivers in the vivante_kernel_drivers
repository. These changes were tested on a PXA168 with GC300 revision
0x2201 (date 0x20080814, time 0x12051100), which already has an existing
special case in the driver to modify the revision to 0x1051.
I was a little unsure of the "correct" way to do the fixup to the power
register offsets. I implemented the change in gpu_write and gpu_read,
but if someone has a better idea I would be happy to do it differently.
Doug Brown (2):
drm/etnaviv: add missing quirks for GC300
drm/etnaviv: fix power register offset on GC300
drivers/gpu/drm/etnaviv/etnaviv_gpu.c | 11 +++++++++--
drivers/gpu/drm/etnaviv/etnaviv_gpu.h | 16 ++++++++++++++--
2 files changed, 23 insertions(+), 4 deletions(-)
--
2.25.1
next reply other threads:[~2022-09-03 6:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-03 6:05 Doug Brown [this message]
2022-09-03 6:05 ` [PATCH 1/2] drm/etnaviv: add missing quirks for GC300 Doug Brown
2022-09-03 11:38 ` Christian Gmeiner
2022-09-03 6:05 ` [PATCH 2/2] drm/etnaviv: fix power register offset on GC300 Doug Brown
2022-09-03 11:49 ` Christian Gmeiner
2022-09-05 21:05 ` Doug Brown
2022-09-06 8:12 ` Lucas Stach
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=20220903060558.55167-1-doug@schmorgal.com \
--to=doug@schmorgal.com \
--cc=airlied@linux.ie \
--cc=christian.gmeiner@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=etnaviv@lists.freedesktop.org \
--cc=l.stach@pengutronix.de \
--cc=linux+etnaviv@armlinux.org.uk \
/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