From: maxime.ripard@bootlin.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: sun8i: Add initial Orangepi Zero Plus 2 H3 support
Date: Mon, 30 Jul 2018 10:45:19 +0200 [thread overview]
Message-ID: <20180730084519.iqyhvocxsfuopze7@flea> (raw)
In-Reply-To: <20180727125739.22871-1-diego.rondini@kynetics.com>
On Fri, Jul 27, 2018 at 02:57:39PM +0200, Diego Rondini wrote:
> +/dts-v1/;
> +
> +#include "sun8i-h3.dtsi"
> +
> +#include <dt-bindings/gpio/gpio.h>
> +
> +/ {
> + model = "OrangePi Zero Plus2 H3";
> + compatible = "xunlong,orangepi-zero-plus2", "allwinner,sun8i-h3";
The H5 version doesn't make that easy, and it's unfortunate, but we
should have a different compatible for the H3 and H5 versions.
What about something like xunlong,orangepi-zero-plus2-h3?
> +&uart1 {
> + pinctrl-names = "default";
> + pinctrl-0 = <&uart1_pins>, <&uart1_rts_cts_pins>;
> + status = "okay";
> +};
I guess it is the BT chip? Which chip is it?
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/20180730/6a698a51/attachment.sig>
next prev parent reply other threads:[~2018-07-30 8:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-27 12:57 [PATCH] ARM: dts: sun8i: Add initial Orangepi Zero Plus 2 H3 support Diego Rondini
2018-07-30 8:45 ` Maxime Ripard [this message]
2018-07-30 9:17 ` Diego Rondini
2018-07-31 14:15 ` Maxime Ripard
2018-07-30 11:52 ` [PATCH v2] " Diego Rondini
2018-07-31 14:16 ` Maxime Ripard
2018-08-03 7:56 ` [PATCH v3] " Diego Rondini
2018-08-20 13:33 ` 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=20180730084519.iqyhvocxsfuopze7@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;
as well as URLs for NNTP newsgroup(s).