linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime@cerno.tech>
To: dri-devel@lists.freedesktop.org,
	Daniel Vetter <daniel.vetter@intel.com>,
	David Airlie <airlied@linux.ie>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Maxime Ripard <maxime@cerno.tech>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
	Maxime Ripard <mripard@kernel.org>, Eric Anholt <eric@anholt.net>,
	bcm-kernel-feedback-list@broadcom.com,
	Ray Jui <rjui@broadcom.com>,
	devicetree@vger.kernel.org, Scott Branden <sbranden@broadcom.com>,
	linux-kernel@vger.kernel.org, Daniel Vetter <daniel@ffwll.ch>,
	Rob Herring <robh+dt@kernel.org>,
	linux-rpi-kernel@lists.infradead.org,
	Nicolas Saenz Julienne <nsaenz@kernel.org>,
	linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] drm/vc4: Add support for the BCM2711 VEC
Date: Thu, 20 May 2021 17:03:40 +0200	[thread overview]
Message-ID: <20210520150344.273900-1-maxime@cerno.tech> (raw)

Hi,

The composite output in the BCM2711 is dealt using the VEC. While the earlier
SoCs were properly supported, it wasn't functional on the BCM2711. Add the
needed support from the RPi downstream kernel.

Maxime

Mateusz Kwiatkowski (4):
  drm/vc4: Fix clock source for VEC PixelValve on BCM2711
  dt-bindings: display: bcm2835-vec: Add BCM2711 compatible
  drm/vc4: Separate VEC compatible variants
  ARM: boot: dts: bcm2711: Add BCM2711 VEC compatible

 .../bindings/display/brcm,bcm2835-vec.yaml    |  4 ++-
 arch/arm/boot/dts/bcm2711.dtsi                |  1 +
 drivers/gpu/drm/vc4/vc4_crtc.c                |  2 +-
 drivers/gpu/drm/vc4/vc4_vec.c                 | 27 +++++++++++++++----
 4 files changed, 27 insertions(+), 7 deletions(-)

-- 
2.31.1


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2021-05-20 15:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-20 15:03 Maxime Ripard [this message]
2021-05-20 15:03 ` [PATCH 1/4] drm/vc4: Fix clock source for VEC PixelValve on BCM2711 Maxime Ripard
2021-05-20 15:03 ` [PATCH 2/4] dt-bindings: display: bcm2835-vec: Add BCM2711 compatible Maxime Ripard
2021-05-20 15:03 ` [PATCH 3/4] drm/vc4: Separate VEC compatible variants Maxime Ripard
2021-05-20 15:03 ` [PATCH 4/4] ARM: boot: dts: bcm2711: Add BCM2711 VEC compatible Maxime Ripard
2021-06-08 10:06   ` nicolas saenz julienne
2021-05-20 16:53 ` [PATCH 0/4] drm/vc4: Add support for the BCM2711 VEC Dave Stevenson
2021-05-24 11:52 ` 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=20210520150344.273900-1-maxime@cerno.tech \
    --to=maxime@cerno.tech \
    --cc=airlied@linux.ie \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=daniel.vetter@intel.com \
    --cc=daniel@ffwll.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=eric@anholt.net \
    --cc=f.fainelli@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=nsaenz@kernel.org \
    --cc=rjui@broadcom.com \
    --cc=robh+dt@kernel.org \
    --cc=sbranden@broadcom.com \
    --cc=tzimmermann@suse.de \
    /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).