From: <mars.cheng@mediatek.com>
To: <matthias.bgg@gmail.com>
Cc: <cc.hwang@mediatek.com>, <loda.chou@mediatek.com>,
<miles.chen@mediatek.com>, <scott.shu@mediatek.com>,
<jades.shih@mediatek.com>, <yingjoe.chen@mediatek.com>,
<my.chuang@mediatek.com>, <linux-kernel@vger.kernel.org>,
<linux-mediatek@lists.infradead.org>,
<devicetree@vger.kernel.org>
Subject: [PATCH v3 0/2] Add mt6580 basic chip support
Date: Tue, 7 Jul 2015 15:56:09 +0800 [thread overview]
Message-ID: <1436255771-5367-1-git-send-email-mars.cheng@mediatek.com> (raw)
This patch adds basic support for Mediatek's new 4-core chip, mt6580.
Based on v4.2-rc1.
This patch add basic support for Mediatek's new 4-core chip, mt6580.
Changes in v3:
1. Remove useless Change-Id
2. Add complete device tree binding in Documentation
Changes in v2:
1. Use stdout-path in device tree to indicate console
2. Remove board-specific bootargs
Mars Cheng (2):
Document: DT: Add bindings for mediatek MT6580 SoC Platform
ARM: dts: mediatek: add mt6580 basic support
Documentation/devicetree/bindings/arm/mediatek.txt | 4 +
.../bindings/arm/mediatek/mediatek,sysirq.txt | 1 +
.../devicetree/bindings/serial/mtk-uart.txt | 3 +-
.../bindings/timer/mediatek,mtk-timer.txt | 6 +-
arch/arm/boot/dts/Makefile | 1 +
arch/arm/boot/dts/mt6580-evbp1.dts | 35 ++++++
arch/arm/boot/dts/mt6580.dtsi | 123 +++++++++++++++++++++
7 files changed, 171 insertions(+), 2 deletions(-)
create mode 100644 arch/arm/boot/dts/mt6580-evbp1.dts
create mode 100644 arch/arm/boot/dts/mt6580.dtsi
--
1.8.1.1.dirty
next reply other threads:[~2015-07-07 7:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 7:56 mars.cheng [this message]
2015-07-07 7:56 ` [PATCH v3 1/2] Document: DT: Add bindings for mediatek MT6580 SoC Platform mars.cheng
2015-07-07 7:56 ` [PATCH 2/2] ARM: dts: mediatek: add mt6580 basic support mars.cheng
2015-07-07 8:10 ` Mars Cheng
2015-07-10 15:01 ` Matthias Brugger
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=1436255771-5367-1-git-send-email-mars.cheng@mediatek.com \
--to=mars.cheng@mediatek.com \
--cc=cc.hwang@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=jades.shih@mediatek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=loda.chou@mediatek.com \
--cc=matthias.bgg@gmail.com \
--cc=miles.chen@mediatek.com \
--cc=my.chuang@mediatek.com \
--cc=scott.shu@mediatek.com \
--cc=yingjoe.chen@mediatek.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
all inboxes | Powered by JetHome®