From: "周琰杰 (Zhou Yanjie)" <zhouyanjie@wanyeetech.com>
To: tsbogend@alpha.franken.de, robh+dt@kernel.org
Cc: linux-mips@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, paulburton@kernel.org,
paul@crapouillou.net, ak@linux.intel.com, ebiederm@xmission.com,
dongsheng.qiu@ingenic.com, aric.pzqi@ingenic.com,
rick.tyliu@ingenic.com, yanfei.li@ingenic.com,
sernia.zhou@foxmail.com, zhenwenjin@gmail.com
Subject: [PATCH v4 0/5] Add support for Ingenic X1830 SoC and Y&A CU1830-Neo board.
Date: Tue, 14 Jul 2020 13:32:24 +0800 [thread overview]
Message-ID: <20200714053229.33195-1-zhouyanjie@wanyeetech.com> (raw)
v3->v4:
1.Modify the commit message and add the change description
for CU1000-Neo in patch [2/5].
2.The wrongly written "ingenic,x1000" in compatible is
changed to "ingenic,x1000e" in "cu1000-neo.dts".
3.Adjust the order of nodes according to the corresponding
address value for X1000.
4.Drop unnecessary node in "wlan_pwrseq" in "cu1000-neo.dts".
5.Add the leds node to "cu1000-neo.dts".
周琰杰 (Zhou Yanjie) (5):
MIPS: Ingenic: Add Ingenic X1830 support.
dt-bindings: MIPS: Add X1830 based CU1830-Neo and fix bug in
CU1000-Neo.
MIPS: Ingenic: Add YSH & ATIL CU Neo board support.
MIPS: Ingenic: Fix bugs and add missing LED node for X1000.
MIPS: CU1000-Neo: Refresh defconfig to support LED.
.../devicetree/bindings/mips/ingenic/devices.yaml | 12 +-
arch/mips/boot/dts/ingenic/Makefile | 1 +
arch/mips/boot/dts/ingenic/cu1000-neo.dts | 114 ++++----
arch/mips/boot/dts/ingenic/cu1830-neo.dts | 168 ++++++++++++
arch/mips/boot/dts/ingenic/x1000.dtsi | 126 +++++----
arch/mips/boot/dts/ingenic/x1830.dtsi | 300 +++++++++++++++++++++
arch/mips/configs/cu1000-neo_defconfig | 4 +
arch/mips/configs/cu1830-neo_defconfig | 123 +++++++++
arch/mips/jz4740/Kconfig | 10 +
9 files changed, 733 insertions(+), 125 deletions(-)
create mode 100644 arch/mips/boot/dts/ingenic/cu1830-neo.dts
create mode 100644 arch/mips/boot/dts/ingenic/x1830.dtsi
create mode 100644 arch/mips/configs/cu1830-neo_defconfig
--
2.11.0
next reply other threads:[~2020-07-14 5:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 5:32 周琰杰 (Zhou Yanjie) [this message]
2020-07-14 5:32 ` [PATCH v4 1/5] MIPS: Ingenic: Add Ingenic X1830 support 周琰杰 (Zhou Yanjie)
2020-07-14 5:32 ` [PATCH v4 2/5] dt-bindings: MIPS: Add X1830 based CU1830-Neo and fix bug in CU1000-Neo 周琰杰 (Zhou Yanjie)
2020-07-14 20:49 ` Rob Herring
2020-07-14 5:32 ` [PATCH v4 3/5] MIPS: Ingenic: Add YSH & ATIL CU Neo board support 周琰杰 (Zhou Yanjie)
2020-07-14 5:32 ` [PATCH v4 4/5] MIPS: Ingenic: Fix bugs and add missing LED node for X1000 周琰杰 (Zhou Yanjie)
2020-07-14 5:32 ` [PATCH v4 5/5] MIPS: CU1000-Neo: Refresh defconfig to support LED 周琰杰 (Zhou Yanjie)
2020-07-16 9:51 ` [PATCH v4 0/5] Add support for Ingenic X1830 SoC and Y&A CU1830-Neo board Thomas Bogendoerfer
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=20200714053229.33195-1-zhouyanjie@wanyeetech.com \
--to=zhouyanjie@wanyeetech.com \
--cc=ak@linux.intel.com \
--cc=aric.pzqi@ingenic.com \
--cc=devicetree@vger.kernel.org \
--cc=dongsheng.qiu@ingenic.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=paul@crapouillou.net \
--cc=paulburton@kernel.org \
--cc=rick.tyliu@ingenic.com \
--cc=robh+dt@kernel.org \
--cc=sernia.zhou@foxmail.com \
--cc=tsbogend@alpha.franken.de \
--cc=yanfei.li@ingenic.com \
--cc=zhenwenjin@gmail.com \
/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).