From: PrasannaKumar Muralidharan <prasannatsmkumar@gmail.com>
To: robh+dt@kernel.org, mark.rutland@arm.com, ralf@linux-mips.org,
mturquette@baylibre.com, sboyd@codeaurora.org,
devicetree@vger.kernel.org, linux-mips@linux-mips.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
paul@crapouillou.net, malat@debian.org, dom.peklo@gmail.com
Cc: PrasannaKumar Muralidharan <prasannatsmkumar@gmail.com>
Subject: [RFC 0/4] Add Ingenic X1000 SoC Support
Date: Wed, 27 Sep 2017 20:45:23 +0530 [thread overview]
Message-ID: <20170927151527.25570-1-prasannatsmkumar@gmail.com> (raw)
Add support for Ingenic X1000 SoC. This patch set provides enough bits
to boot a kernel to an initramfs user space.
I implemented this code during 2016. Boot stuck at "calibrating delay
loop ...". Now I have fixed the issue by setting the correct irq. I do
not have access to this device anymore so could not test the fix.
Marking this patch series as RFC as this needs to be tested.
Test and feedback appreciated.
This series enables uart, timer and interrupt controller. As this is
very minimal a static elf binary should be used as init and should be
available in initramfs.
PrasannaKumar Muralidharan (4):
dt-bindings: Add Ingenic X1000 SoC clock define
clk: Add Ingenic X1000 CGU driver
MIPS: Ingenic: Initial X1000 SoC support
MIPS: Ingenic: Add Halley2 development board support
arch/mips/boot/dts/ingenic/Makefile | 1 +
arch/mips/boot/dts/ingenic/halley2.dts | 46 ++++++++
arch/mips/boot/dts/ingenic/x1000.dtsi | 93 +++++++++++++++
arch/mips/configs/halley2_defconfig | 61 ++++++++++
arch/mips/jz4740/Kconfig | 10 ++
arch/mips/jz4740/time.c | 2 +-
drivers/clk/ingenic/Makefile | 1 +
drivers/clk/ingenic/x1000-cgu.c | 203 +++++++++++++++++++++++++++++++++
include/dt-bindings/clock/x1000-cgu.h | 46 ++++++++
9 files changed, 462 insertions(+), 1 deletion(-)
create mode 100644 arch/mips/boot/dts/ingenic/halley2.dts
create mode 100644 arch/mips/boot/dts/ingenic/x1000.dtsi
create mode 100644 arch/mips/configs/halley2_defconfig
create mode 100644 drivers/clk/ingenic/x1000-cgu.c
create mode 100644 include/dt-bindings/clock/x1000-cgu.h
--
2.10.0
next reply other threads:[~2017-09-27 15:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 15:15 PrasannaKumar Muralidharan [this message]
2017-09-27 15:15 ` [RFC 1/4] dt-bindings: Add Ingenic X1000 SoC clock define PrasannaKumar Muralidharan
2017-09-27 15:15 ` [RFC 2/4] clk: Add Ingenic X1000 CGU driver PrasannaKumar Muralidharan
2017-10-25 9:23 ` Stephen Boyd
2017-09-27 15:15 ` [RFC 3/4] MIPS: Ingenic: Initial X1000 SoC support PrasannaKumar Muralidharan
2018-03-06 0:08 ` James Hogan
2018-03-07 13:44 ` PrasannaKumar Muralidharan
2018-03-07 14:19 ` Jiaxun Yang
2018-03-07 15:21 ` PrasannaKumar Muralidharan
2018-03-07 14:35 ` James Hogan
2018-03-07 15:05 ` PrasannaKumar Muralidharan
2018-03-07 15:10 ` James Hogan
2018-03-07 15:22 ` PrasannaKumar Muralidharan
2018-03-07 15:52 ` Jiaxun Yang
2018-03-07 16:25 ` PrasannaKumar Muralidharan
2018-03-07 18:13 ` Mathieu Malaterre
2018-03-10 19:05 ` Jiaxun Yang
2017-09-27 15:15 ` [RFC 4/4] MIPS: Ingenic: Add Halley2 development board support PrasannaKumar Muralidharan
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=20170927151527.25570-1-prasannatsmkumar@gmail.com \
--to=prasannatsmkumar@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dom.peklo@gmail.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=malat@debian.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=paul@crapouillou.net \
--cc=ralf@linux-mips.org \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.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