From: Maxime Ripard <maxime@cerno.tech>
To: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
Eric Anholt <eric@anholt.net>
Cc: dri-devel@lists.freedesktop.org,
linux-rpi-kernel@lists.infradead.org,
bcm-kernel-feedback-list@broadcom.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Dave Stevenson <dave.stevenson@raspberrypi.com>,
Tim Gover <tim.gover@raspberrypi.com>,
Phil Elwell <phil@raspberrypi.com>
Subject: Re: [PATCH v4 0/9] drm/vc4: Turn the TXP into a CRTC
Date: Tue, 30 Jun 2020 10:25:09 +0200 [thread overview]
Message-ID: <20200630082509.puuzneiipalvrxup@gilmour.lan> (raw)
In-Reply-To: <cover.c33f5fd8b1b2703081f25398eb879937c9f7ce0b.1591882579.git-series.maxime@cerno.tech>
[-- Attachment #1: Type: text/plain, Size: 1145 bytes --]
Hi Eric,
On Thu, Jun 11, 2020 at 03:36:45PM +0200, Maxime Ripard wrote:
> Hi,
>
> This is another part of the rpi4 HDMI series that got promoted to a
> series of its own to try to reduce the main one.
>
> This rework is needed since the bcm2711 used in the rpi4 has a more
> complex routing in the HVS that doesn't allow to use a fairly simple
> mapping like what was used before.
>
> Since that mapping affects both the pixelvalves and the TXP, turning the
> TXP into a CRTC just like pixelvalves are allows to deal with the
> mapping in the CRTC states, which turns out to be pretty convenient.
>
> Let me know what you think,
> Maxime
>
> Changes from v3:
> - Stripped the patches out of the main HDMI series
> - Change the bind order of the HVS to avoid a compatible check
> - Added Eric's tags
> - Rebased on top of drm-misc-next
>
> Maxime Ripard (9):
> drm/vc4: Reorder the bind order of the devices
> drm/vc4: crtc: Move HVS setup code to the HVS driver
Could you review those two patches? You haven't reviewed them yet and
it's holding back the rest of the patches.
Thanks!
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2020-06-30 8:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 13:36 Maxime Ripard
2020-06-11 13:36 ` [PATCH v4 1/9] drm/vc4: Reorder the bind order of the devices Maxime Ripard
2020-06-11 13:36 ` [PATCH v4 2/9] drm/vc4: crtc: Move HVS setup code to the HVS driver Maxime Ripard
2020-06-11 13:36 ` [PATCH v4 3/9] drm/vc4: crtc: Make state functions public Maxime Ripard
2020-06-11 13:36 ` [PATCH v4 4/9] drm/vc4: crtc: Split CRTC data in two Maxime Ripard
2020-06-11 13:36 ` [PATCH v4 5/9] drm/vc4: crtc: Only access the PixelValve registers if we have to Maxime Ripard
2020-06-11 13:36 ` [PATCH v4 6/9] drm/vc4: crtc: Move the CRTC initialisation to a separate function Maxime Ripard
2020-06-11 13:36 ` [PATCH v4 7/9] drm/vc4: crtc: Move the txp_armed function to the TXP Maxime Ripard
2020-06-11 13:36 ` [PATCH v4 8/9] drm/vc4: txp: Turn the TXP into a CRTC of its own Maxime Ripard
2020-06-11 13:36 ` [PATCH v4 9/9] drm/vc4: crtc: Remove the feed_txp tests Maxime Ripard
2020-06-30 8:25 ` Maxime Ripard [this message]
2020-07-07 0:51 ` [PATCH v4 0/9] drm/vc4: Turn the TXP into a CRTC Eric Anholt
2020-07-07 8:54 ` Maxime Ripard
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=20200630082509.puuzneiipalvrxup@gilmour.lan \
--to=maxime@cerno.tech \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dave.stevenson@raspberrypi.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@anholt.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=nsaenzjulienne@suse.de \
--cc=phil@raspberrypi.com \
--cc=tim.gover@raspberrypi.com \
/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
all inboxes | Powered by JetHome®