From: Rob Clark <robdclark@gmail.com>
To: linux-arm-msm@vger.kernel.org
Cc: Rob Clark <robdclark@gmail.com>
Subject: [PATCH 0/3] Basic support for inforce IFC6410 board
Date: Mon, 16 Dec 2013 12:00:51 -0500 [thread overview]
Message-ID: <1387213254-23020-1-git-send-email-robdclark@gmail.com> (raw)
Couple little patches, plus work-in-progress DT file for the IFC6410.
With this, plus the msm clk support[1], I have serial console working
on top of 3.13-rc4. The debug UART patch is not strictly required,
but it is a lot easier to debug when you can see what is going on in
early boot before the serial driver is up.
[1] http://www.spinics.net/lists/devicetree/msg08409.html
Rob Clark (3):
mach-msm: add aqp8064 debug uart
mach-msm: enable sparsemem for 8960
RFC: mach-msm: add DT for ifc6410 (apq8064)
arch/arm/Kconfig.debug | 9 ++
arch/arm/boot/dts/qcom-apq8064-ifc6410.dts | 131 +++++++++++++++++++++++++++++
arch/arm/include/debug/msm.S | 5 ++
arch/arm/mach-msm/Kconfig | 3 +
arch/arm/mach-msm/board-dt.c | 1 +
arch/arm/mach-msm/include/mach/memory.h | 22 +++++
6 files changed, 171 insertions(+)
create mode 100644 arch/arm/boot/dts/qcom-apq8064-ifc6410.dts
create mode 100644 arch/arm/mach-msm/include/mach/memory.h
--
1.8.4.2
next reply other threads:[~2013-12-16 17:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 17:00 Rob Clark [this message]
2013-12-16 17:00 ` [PATCH 1/3] mach-msm: add aqp8064 debug uart Rob Clark
2013-12-16 17:26 ` Christopher Covington
2013-12-16 17:39 ` Rob Clark
2013-12-16 17:00 ` [PATCH 2/3] mach-msm: enable sparsemem for 8960 Rob Clark
2013-12-16 19:32 ` Rob Clark
2013-12-16 17:00 ` [RFC 3/3] RFC: mach-msm: add DT for ifc6410 (apq8064) Rob Clark
2013-12-16 19:57 ` Stephen Boyd
2013-12-16 20:03 ` Olof Johansson
2013-12-16 20:10 ` Rob Clark
2013-12-16 20:14 ` Olof Johansson
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=1387213254-23020-1-git-send-email-robdclark@gmail.com \
--to=robdclark@gmail.com \
--cc=linux-arm-msm@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.