From: Alexandre GRIVEAUX <agriveaux@deutnet.info>
To: robh+dt@kernel.org, mark.rutland@arm.com, ralf@linux-mips.org,
paul.burton@mips.com, jhogan@kernel.org, agriveaux@deutnet.info
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: [PATCH v2 0/5] MIPS: CI20: DTS: Add nodes to Creator CI20 board
Date: Tue, 1 Oct 2019 21:08:19 +0200 [thread overview]
Message-ID: <cover.1569955865.git.agriveaux@deutnet.info> (raw)
Attemping to make my CI20 more usefull than a paperweight, I add nodes to Devicetree, at this time:
- Add I2C node PMU and RTC.
- The IW8103 need some work to stay alive because power seem to turn off.
- The leds patch lack of correct option in ci20_defconfig.
- The Cpu patch isn't usefull without SMP support of jz4780.
Alexandre GRIVEAUX (5):
MIPS: JZ4780: DTS: Add I2C nodes
MIPS: CI20: DTS: Add I2C nodes
MIPS: CI20: DTS: Add IW8103 Wifi + bluetooth
MIPS: CI20: DTS: Add Leds
MIPS: JZ4780: DTS: Add CPU nodes
v2 adding previous sended patch: JZ4780: DTS: Add I2C nodes
arch/mips/boot/dts/ingenic/ci20.dts | 214 +++++++++++++++++++++++++
arch/mips/boot/dts/ingenic/jz4780.dtsi | 103 ++++++++++++
2 files changed, 317 insertions(+)
base-commit: 54ecb8f7028c5eb3d740bb82b0f1d90f2df63c5c
--
2.20.1
next reply other threads:[~2019-10-01 19:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 19:08 Alexandre GRIVEAUX [this message]
2019-10-01 19:08 ` [PATCH v2 1/5] MIPS: JZ4780: DTS: Add I2C nodes Alexandre GRIVEAUX
2019-10-07 17:53 ` Paul Burton
2019-10-01 19:09 ` [PATCH v2 2/5] MIPS: CI20: " Alexandre GRIVEAUX
2019-10-07 17:53 ` Paul Burton
2019-10-01 19:09 ` [PATCH v2 3/5] MIPS: CI20: DTS: Add IW8103 Wifi + bluetooth Alexandre GRIVEAUX
2019-10-07 17:53 ` Paul Burton
2019-10-01 19:09 ` [PATCH v2 4/5] MIPS: CI20: DTS: Add Leds Alexandre GRIVEAUX
2019-10-07 17:53 ` Paul Burton
2019-10-01 19:09 ` [PATCH v2 5/5] MIPS: JZ4780: DTS: Add CPU nodes Alexandre GRIVEAUX
2019-10-01 23:20 ` Paul Burton
2019-10-02 19:07 ` Alexandre GRIVEAUX
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=cover.1569955865.git.agriveaux@deutnet.info \
--to=agriveaux@deutnet.info \
--cc=devicetree@vger.kernel.org \
--cc=jhogan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=paul.burton@mips.com \
--cc=ralf@linux-mips.org \
--cc=robh+dt@kernel.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).