From: Ondrej Jirman <megous@megous.com>
To: linux-sunxi@googlegroups.com, Rob Herring <robh+dt@kernel.org>,
Maxime Ripard <mripard@kernel.org>, Chen-Yu Tsai <wens@csie.org>
Cc: Ondrej Jirman <megous@megous.com>,
Mark Rutland <mark.rutland@arm.com>,
Corentin Labbe <clabbe@baylibre.com>,
Georgii Staroselskii <georgii.staroselskii@emlid.com>,
Samuel Holland <samuel@sholland.org>,
Martijn Braam <martijn@brixit.nl>, Luca Weiss <luca@z3ntu.xyz>,
Bhushan Shah <bshah@kde.org>, Icenowy Zheng <icenowy@aosc.io>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/3] Add support for Pine64 PinePhone Linux Smartphone
Date: Thu, 27 Feb 2020 02:26:47 +0100 [thread overview]
Message-ID: <20200227012650.1179151-1-megous@megous.com> (raw)
This series adds an initial support for Pine64 PinePhone.
Please take a look.
thank you and regards,
Ondrej Jirman
Changes in v2:
- make i2c2_pins default pinctrl config for i2c2 node
- add description of the differences between 1.0 and 1.1 to the
commit message
- added copyright header for Martijn Braam
- drop pinctrl config from i2c1 and i2c2 nodes, since it's
now the default
- extend comments on i2c2 and uart3 nodes to be more clear
- rebased on top of linux-next and resolved conflicts
- dropped the function-enumerator from leds
Changes not made:
- I didn't drop pinctrl configs on mmc0, mmc2 and uart3
- these are actually not default in dtsi, as was suggested
- gpio-leds kept with the new function/color binding, but I dropped
the function-enumerator
It seems intention for the future (since about 06-2019[0]) is for LEDs to not
have a devicename in their class name, because that's determinable
from the sysfs in other ways, and to use the function and color
properties instead of label in DT.
[0] https://lore.kernel.org/lkml/20190609190803.14815-5-jacek.anaszewski@gmail.com/T/
function-enumerator is supposed to be used if function/color don't
make the LED name unique for the board. [1] So I dropped function-enumerator
from my series, as it just added a numeric suffix to the LED name
for no reason.
[1] https://lore.kernel.org/patchwork/patch/1063388/
This follow the recent new board binding additions to the kernel (in 5.6):
https://elixir.bootlin.com/linux/v5.6-rc3/source/arch/arm64/boot/dts/amlogic/meson-gx-libretech-pc.dtsi#L96
Ondrej Jirman (3):
arm64: dts: sun50i-a64: Add i2c2 pins
dt-bindings: arm: sunxi: Add PinePhone 1.0 and 1.1 bindings
arm64: dts: allwinner: Add initial support for Pine64 PinePhone
.../devicetree/bindings/arm/sunxi.yaml | 10 +
arch/arm64/boot/dts/allwinner/Makefile | 2 +
.../allwinner/sun50i-a64-pinephone-1.0.dts | 11 +
.../allwinner/sun50i-a64-pinephone-1.1.dts | 11 +
.../dts/allwinner/sun50i-a64-pinephone.dtsi | 379 ++++++++++++++++++
arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi | 8 +-
6 files changed, 420 insertions(+), 1 deletion(-)
create mode 100644 arch/arm64/boot/dts/allwinner/sun50i-a64-pinephone-1.0.dts
create mode 100644 arch/arm64/boot/dts/allwinner/sun50i-a64-pinephone-1.1.dts
create mode 100644 arch/arm64/boot/dts/allwinner/sun50i-a64-pinephone.dtsi
--
2.25.1
next reply other threads:[~2020-02-27 1:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 1:26 Ondrej Jirman [this message]
2020-02-27 1:26 ` [PATCH v2 1/3] arm64: dts: sun50i-a64: Add i2c2 pins Ondrej Jirman
2020-02-27 1:26 ` [PATCH v2 2/3] dt-bindings: arm: sunxi: Add PinePhone 1.0 and 1.1 bindings Ondrej Jirman
2020-02-27 1:32 ` Ondřej Jirman
2020-02-27 1:26 ` [PATCH v2 3/3] arm64: dts: allwinner: Add initial support for Pine64 PinePhone Ondrej Jirman
2020-02-27 13:04 ` [PATCH v2 0/3] Add support for Pine64 PinePhone Linux Smartphone Maxime Ripard
2020-02-27 15:52 ` Ondřej Jirman
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=20200227012650.1179151-1-megous@megous.com \
--to=megous@megous.com \
--cc=bshah@kde.org \
--cc=clabbe@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=georgii.staroselskii@emlid.com \
--cc=icenowy@aosc.io \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=luca@z3ntu.xyz \
--cc=mark.rutland@arm.com \
--cc=martijn@brixit.nl \
--cc=mripard@kernel.org \
--cc=robh+dt@kernel.org \
--cc=samuel@sholland.org \
--cc=wens@csie.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
all inboxes | Powered by JetHome®