From: maxime.ripard@bootlin.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/7] Allwinner A64 DE2 CCU support with dedicated DE2 bus driver
Date: Mon, 25 Jun 2018 18:00:52 +0200 [thread overview]
Message-ID: <20180625160052.kgje2hnzwhfcm2i5@flea> (raw)
In-Reply-To: <20180622122615.55836-1-icenowy@aosc.io>
Hi,
On Fri, Jun 22, 2018 at 08:26:08PM +0800, Icenowy Zheng wrote:
> This patchset tries to implement the Allwinner A64 DE2 as a bus driver,
> in order to model the fact that the SRAM claim controls the access to
> the whole DE2 memory space.
>
> PATCH 1 and PATCH 4 are for the CCU part.
>
> PATCH 2 is the device tree binding for the A64 DE2 bus, and PATCH 3
> implements the bus driver.
>
> PATCH 5 adds the DE2 CCU device tree node, with the DE2 bus node.
>
> PATCH 6 and 7 are HDMI simplefb patches for A64. They're present as a
> test to this patchset.
Apart from the (minor) comments I made that can be fixed up while
applying, I'm happy with those changes. I'd still like to get a review
from Rob, so I'll wait for it to apply them.
Thanks a lot for working on this,
Maxime
--
Maxime Ripard, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180625/c3c13d20/attachment-0001.sig>
next prev parent reply other threads:[~2018-06-25 16:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 12:26 [PATCH v2 0/7] Allwinner A64 DE2 CCU support with dedicated DE2 bus driver Icenowy Zheng
2018-06-22 12:26 ` [PATCH v2 1/7] dt-bindings: add compatible string for the A64 DE2 CCU Icenowy Zheng
2018-06-25 16:00 ` Maxime Ripard [this message]
2018-06-27 18:37 ` [PATCH v2 0/7] Allwinner A64 DE2 CCU support with dedicated DE2 bus driver Maxime Ripard
2018-06-27 20:21 ` Icenowy Zheng
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=20180625160052.kgje2hnzwhfcm2i5@flea \
--to=maxime.ripard@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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