linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Clément Péron" <peron.clem@gmail.com>
To: Maxime Ripard <mripard@kernel.org>,
	Tomeu Vizoso <tomeu.vizoso@collabora.com>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	"Clément Péron" <peron.clem@gmail.com>
Subject: [PATCH v7 0/2] Allwinner H6 Mali GPU support
Date: Wed, 30 Oct 2019 16:07:40 +0100	[thread overview]
Message-ID: <20191030150742.3573-1-peron.clem@gmail.com> (raw)

Hi,

Proper iommu patches has been merged[0].

There is still work to do to make it works with panfrost
but all modules can be probed and removed smoothly.

These bindings could be used also for out-of-tree modules.

[0]: https://lore.kernel.org/linux-iommu/cover.1569851517.git.robin.murphy@arm.com/

Change since v6:
 - Remove iommu patches
 - Rebase on 5.4-rc4

Clément Péron (2):
  arm64: dts: allwinner: Add ARM Mali GPU node for H6
  arm64: dts: allwinner: Add mali GPU supply for H6 boards

 .../boot/dts/allwinner/sun50i-h6-beelink-gs1.dts   |  6 ++++++
 .../boot/dts/allwinner/sun50i-h6-orangepi-3.dts    |  6 ++++++
 .../boot/dts/allwinner/sun50i-h6-orangepi.dtsi     |  6 ++++++
 .../boot/dts/allwinner/sun50i-h6-pine-h64.dts      |  6 ++++++
 arch/arm64/boot/dts/allwinner/sun50i-h6.dtsi       | 14 ++++++++++++++
 5 files changed, 38 insertions(+)

-- 
2.20.1


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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-30 15:07 Clément Péron [this message]
2019-10-30 15:07 ` [PATCH v7 1/2] arm64: dts: allwinner: Add ARM Mali GPU node for H6 Clément Péron
2019-10-30 15:07 ` [PATCH v7 2/2] arm64: dts: allwinner: Add mali GPU supply for H6 boards Clément Péron
2019-10-31 12:35 ` [PATCH v7 0/2] Allwinner H6 Mali GPU support 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=20191030150742.3573-1-peron.clem@gmail.com \
    --to=peron.clem@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mripard@kernel.org \
    --cc=tomeu.vizoso@collabora.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;
as well as URLs for NNTP newsgroup(s).