From: Ran Bi <ran.bi@mediatek.com>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Rob Herring <robh+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: Alessandro Zummo <a.zummo@towertech.it>,
Mark Rutland <mark.rutland@arm.com>, <linux-rtc@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
<srv_heupstream@mediatek.com>, YT Shen <yt.shen@mediatek.com>,
Eddie Huang <eddie.huang@mediatek.com>,
Yingjoe Chen <yingjoe.chen@mediatek.com>,
Flora Fu <flora.fu@mediatek.com>,
Sean Wang <sean.wang@mediatek.com>, Ran Bi <ran.bi@mediatek.com>
Subject: [PATCH 0/3] Add Support for MediaTek MT2712 RTC
Date: Tue, 2 Jul 2019 11:21:17 +0800 [thread overview]
Message-ID: <20190702032120.16539-1-ran.bi@mediatek.com> (raw)
This patchset add support to MT2712 RTC. MT2712 RTC is a SoC based RTC
with different architecture compared to MT7622 RTC.
Ran Bi (3):
bindings: rtc: add bindings for MT2712 RTC
rtc: Add support for the MediaTek MT2712 RTC
arm64: dts: add rtc nodes for MT2712
.../devicetree/bindings/rtc/rtc-mt2712.txt | 14 +
arch/arm64/boot/dts/mediatek/mt2712e.dtsi | 6 +
drivers/rtc/Kconfig | 10 +
drivers/rtc/Makefile | 1 +
drivers/rtc/rtc-mt2712.c | 495 ++++++++++++++++++
5 files changed, 526 insertions(+)
create mode 100644 Documentation/devicetree/bindings/rtc/rtc-mt2712.txt
create mode 100644 drivers/rtc/rtc-mt2712.c
--
2.18.0
next reply other threads:[~2019-07-02 3:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-02 3:21 Ran Bi [this message]
2019-07-02 3:21 ` [PATCH 1/3] bindings: rtc: add bindings for MT2712 RTC Ran Bi
2019-07-22 22:51 ` Rob Herring
2019-07-02 3:21 ` [PATCH 2/3] rtc: Add support for the MediaTek " Ran Bi
2019-07-13 21:12 ` Alexandre Belloni
2019-07-17 8:54 ` Ran Bi
2019-07-17 9:06 ` Alexandre Belloni
2019-07-02 3:21 ` [PATCH 3/3] arm64: dts: add rtc nodes for MT2712 Ran Bi
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=20190702032120.16539-1-ran.bi@mediatek.com \
--to=ran.bi@mediatek.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=eddie.huang@mediatek.com \
--cc=flora.fu@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-rtc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sean.wang@mediatek.com \
--cc=srv_heupstream@mediatek.com \
--cc=yingjoe.chen@mediatek.com \
--cc=yt.shen@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;
as well as URLs for NNTP newsgroup(s).