From: Kunihiko Hayashi <hayashi.kunihiko-uWyLwvC0a2jby3iVrkZq2A@public.gmane.org>
To: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Cc: yamada.masahiro-uWyLwvC0a2jby3iVrkZq2A@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
mark.rutland-5wv7dgnIgG8@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Kunihiko Hayashi
<hayashi.kunihiko-uWyLwvC0a2jby3iVrkZq2A@public.gmane.org>
Subject: [PATCH v2 0/2] add support for LD20/11 Global boards
Date: Mon, 12 Jun 2017 15:07:37 +0900 [thread overview]
Message-ID: <1497247659-1610-1-git-send-email-hayashi.kunihiko@socionext.com> (raw)
Initial version of device tree for LD20/11 Global boards.
---
Changes in v2:
- use SPDX-License-Identifier for the license description
- add the atmel manufacturer to the compatible string for I2C EEPROM
Kunihiko Hayashi (2):
arm64: dts: uniphier: add support for LD11 Global board
arm64: dts: uniphier: add support for LD20 Global board
arch/arm64/boot/dts/socionext/Makefile | 2 +
.../boot/dts/socionext/uniphier-ld11-global.dts | 70 ++++++++++++++++++++++
.../boot/dts/socionext/uniphier-ld20-global.dts | 52 ++++++++++++++++
3 files changed, 124 insertions(+)
create mode 100644 arch/arm64/boot/dts/socionext/uniphier-ld11-global.dts
create mode 100644 arch/arm64/boot/dts/socionext/uniphier-ld20-global.dts
--
2.7.4
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2017-06-12 6:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-12 6:07 Kunihiko Hayashi [this message]
2017-06-12 6:07 ` [PATCH v2 1/2] arm64: dts: uniphier: add support for LD11 Global board Kunihiko Hayashi
2017-06-12 6:07 ` [PATCH v2 2/2] arm64: dts: uniphier: add support for LD20 " Kunihiko Hayashi
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=1497247659-1610-1-git-send-email-hayashi.kunihiko@socionext.com \
--to=hayashi.kunihiko-uwylwvc0a2jby3ivrkzq2a@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=yamada.masahiro-uWyLwvC0a2jby3iVrkZq2A@public.gmane.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).