From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/5] arm64: Allwinner H5 support
Date: Thu, 24 Nov 2016 11:59:58 +0100 [thread overview]
Message-ID: <20161124105958.xzp4fr2fs4p42upx@lukather> (raw)
In-Reply-To: <1479950235-26821-1-git-send-email-andre.przywara@arm.com>
On Thu, Nov 24, 2016 at 01:17:10AM +0000, Andre Przywara wrote:
> This series adds support for the recently released Allwinner H5 SoC [1] and
> the Orange Pi PC 2 board [2].
> This exercise is rather easy this time, since the new SoC is very similar
> to the existing H3 SoC and can thus share a lot of support.
> To express this, the first patch splits the H3 .dtsi to allow reusing
> it later. The last two patches add the H5 .dtsi and the .dts for the
> first available board featuring this chip, based on that shared base DT.
>
> This is some early version, it's based on a merge of various -for-4.10
> branches from Maxime's repository.
> I can boot this on the OPi board and MMC and USB seem to work fine.
> I haven't tested any other peripherals yet.
> Some open issues:
> - The naming: Following the Allwinner scheme this should be "sun50i-h5"
> (which I use in this series), but it shares so much with the H3 that
> "sun8i-h5" wouldn't be wrong either. It gets a bit weird with that shared
> .dtsi, which I call sun8i-h3-h5.dtsi for now.
> - The clocks and pinctrl look _almost_ similar. I may sound like a broken
> record, but our habit of requiring kernel support for those almost identical
> SoCs really bites us now. As the MMC got updated, I fear there is _one_
> additional pin that we need for the HS400 transfer mode. Also I am afraid
> the MMC clock may be slightly different due to the advanced MMC support.
> At the moment this is not an issue, as the driver only support DDR50 at
> most anyway, so we get away with it now.
> I wonder if it's feasible to add those things to the existing H3 clocks
> and pinctrl to avoid another set of drivers.
> - I just see that I missed those patches that add just the names to the
> binding docs. I will send them once we agreed on the naming.
I don't have any major comments but I guess it all depends on the DT
maintainers view on the symbolic link to share the DTSI.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20161124/938ef169/attachment-0001.sig>
next prev parent reply other threads:[~2016-11-24 10:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-24 1:17 [RFC PATCH 0/5] arm64: Allwinner H5 support Andre Przywara
2016-11-24 1:17 ` [RFC PATCH 1/5] arm: dts: sun8i: split Allwinner H3 .dtsi Andre Przywara
2016-11-24 1:17 ` [RFC PATCH 2/5] dmaengine: allow sun6i-dma for more SoCs Andre Przywara
2016-11-24 4:16 ` Chen-Yu Tsai
2016-11-24 9:16 ` Andre Przywara
2016-11-24 9:30 ` Chen-Yu Tsai
2016-11-24 10:12 ` Andre Przywara
2016-11-24 10:55 ` Maxime Ripard
2016-11-24 11:15 ` Andre Przywara
2016-11-24 20:44 ` Maxime Ripard
2016-11-24 1:17 ` [RFC PATCH 3/5] arm64: defconfig: sunxi: include options for Allwinner H5 SoC Andre Przywara
2016-11-24 10:57 ` Maxime Ripard
2016-11-24 11:01 ` Chen-Yu Tsai
2016-11-24 11:09 ` Andre Przywara
2016-11-24 1:17 ` [RFC PATCH 4/5] arm64: dts: sunxi: add Allwinner H5 .dtsi Andre Przywara
2016-11-24 1:17 ` [RFC PATCH 5/5] arm64: dts: sunxi: add support for the Orange Pi PC 2 board Andre Przywara
2016-11-24 10:59 ` Maxime Ripard [this message]
2016-11-24 11:05 ` [RFC PATCH 0/5] arm64: Allwinner H5 support Andre Przywara
2016-11-24 17:03 ` [linux-sunxi] " Ian Campbell
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=20161124105958.xzp4fr2fs4p42upx@lukather \
--to=maxime.ripard@free-electrons.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