From: gary.bisson@boundarydevices.com (Gary Bisson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/5] ARM: dts: imx: update Boundary Devices boards support
Date: Tue, 1 Nov 2016 18:10:01 +0100 [thread overview]
Message-ID: <20161101171006.24594-1-gary.bisson@boundarydevices.com> (raw)
In-Reply-To: <20161025211955.5345-1-gary.bisson@boundarydevices.com>
Hi all,
This series includes several patches to update the support for our platforms.
Here are the main goals of this series:
1- Adding support for our latest SOM (SOM2)
2- Replace underscores in nodes name
3- Fix panel naming consistency across the boards
Changelog v1->v2:
- Drop the USB PHY reset changes, waiting for Peter's series [1] to get in.
- Replace underscores in nodes name
Let me know if you have any question.
Regards,
Gary
[1] https://www.spinics.net/lists/arm-kernel/msg536105.html
Gary Bisson (5):
ARM: dts: imx: add Boundary Devices Nitrogen6_SOM2 support
ARM: dts: imx6qdl-sabrelite: use hyphens for nodes name
ARM: dts: imx6qdl-nitrogen6x: use hyphens for nodes name
ARM: dts: imx6qdl-nit6xlite: use hyphens for nodes name
ARM: dts: imx6qdl-nitrogen6_max: use hyphens for nodes name
arch/arm/boot/dts/Makefile | 1 +
arch/arm/boot/dts/imx6q-nitrogen6_som2.dts | 53 ++
arch/arm/boot/dts/imx6qdl-nit6xlite.dtsi | 32 +-
arch/arm/boot/dts/imx6qdl-nitrogen6_max.dtsi | 18 +-
arch/arm/boot/dts/imx6qdl-nitrogen6_som2.dtsi | 770 ++++++++++++++++++++++++++
arch/arm/boot/dts/imx6qdl-nitrogen6x.dtsi | 12 +-
arch/arm/boot/dts/imx6qdl-sabrelite.dtsi | 10 +-
7 files changed, 849 insertions(+), 47 deletions(-)
create mode 100644 arch/arm/boot/dts/imx6q-nitrogen6_som2.dts
create mode 100644 arch/arm/boot/dts/imx6qdl-nitrogen6_som2.dtsi
--
2.9.3
next prev parent reply other threads:[~2016-11-01 17:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-25 21:19 [PATCH 0/5] ARM: dts: imx: update Boundary Devices boards support Gary Bisson
2016-10-25 21:19 ` [PATCH 1/5] ARM: dts: imx: add Boundary Devices Nitrogen6_SOM2 support Gary Bisson
2016-11-01 14:13 ` Shawn Guo
2016-11-01 14:54 ` Gary Bisson
2016-11-02 7:35 ` Shawn Guo
2016-10-25 21:19 ` [PATCH 2/5] ARM: dts: imx6qdl-sabrelite: rename panel nodes Gary Bisson
2016-10-25 21:19 ` [PATCH 3/5] ARM: dts: imx6qdl-sabrelite: add missing USB PHY reset control Gary Bisson
2016-10-25 21:28 ` Fabio Estevam
2016-10-25 21:53 ` Gary Bisson
2016-11-01 14:17 ` Shawn Guo
2016-10-25 21:19 ` [PATCH 4/5] ARM: dts: imx6qdl-nitrogen6x: rename panel nodes Gary Bisson
2016-10-25 21:19 ` [PATCH 5/5] ARM: dts: imx6qdl-nitrogen6x: add missing USB PHY reset control Gary Bisson
2016-11-01 17:10 ` Gary Bisson [this message]
2016-11-01 17:10 ` [PATCH v2 1/5] ARM: dts: imx: add Boundary Devices Nitrogen6_SOM2 support Gary Bisson
2016-11-01 17:10 ` [PATCH v2 2/5] ARM: dts: imx6qdl-sabrelite: use hyphens for nodes name Gary Bisson
2016-11-01 17:10 ` [PATCH v2 3/5] ARM: dts: imx6qdl-nitrogen6x: " Gary Bisson
2016-11-01 17:10 ` [PATCH v2 4/5] ARM: dts: imx6qdl-nit6xlite: " Gary Bisson
2016-11-01 17:10 ` [PATCH v2 5/5] ARM: dts: imx6qdl-nitrogen6_max: " Gary Bisson
2016-11-02 7:40 ` [PATCH v2 0/5] ARM: dts: imx: update Boundary Devices boards support Shawn Guo
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=20161101171006.24594-1-gary.bisson@boundarydevices.com \
--to=gary.bisson@boundarydevices.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).