From: Weiyi Lu <weiyi.lu@mediatek.com>
To: Matthias Brugger <matthias.bgg@gmail.com>,
Stephen Boyd <sboyd@codeaurora.org>
Cc: Mike Turquette <mturquette@baylibre.com>,
Rob Herring <robh@kernel.org>,
James Liao <jamesjj.liao@mediatek.com>,
Fan Chen <fan.chen@mediatek.com>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-mediatek@lists.infradead.org>, <linux-clk@vger.kernel.org>,
<srv_heupstream@mediatek.com>
Subject: Re: [PATCH v2 0/5] update Mediatek MT2712 clock and scpsys support
Date: Tue, 20 Mar 2018 14:07:48 +0800 [thread overview]
Message-ID: <1521526068.13313.8.camel@mtksdaap41> (raw)
In-Reply-To: <20180312070342.4335-1-weiyi.lu@mediatek.com>
On Mon, 2018-03-12 at 15:03 +0800, Weiyi Lu wrote:
> This series is based on v4.16-rc1 and composed of scpsys control (PATCH 1-2) and clock control (PATCH 3-5).
> Basically, all changes are for the ECO design change of MT2712.
>
> changes since v1:
> - Avoid renumbering clocks. Append new clocks at the bottom of each own subsystem.
>
Hi Matthias & Stephen,
Sorry to bother. Just saw patch 1/2 are already pushed to v4.16-next-soc
and patch 3/5 are applied onto clk-next. What about the patch 4(arm64:
dts: add clock device nodes of MT2712). Does there any problem remain or
it cause some problems? Many thanks.
> Weiyi Lu (5):
> dt-bindings: soc: update MT2712 power dt-bindings
> soc: mediatek: update power domain data of MT2712
> dt-bindings: clock: add clocks for MT2712
> arm64: dts: add clock device nodes of MT2712
> clk: mediatek: update clock driver of MT2712
>
> arch/arm64/boot/dts/mediatek/mt2712e.dtsi | 28 +++++++++++++
> drivers/clk/mediatek/clk-mt2712.c | 69 ++++++++++++++++++++++++-------
> drivers/soc/mediatek/mtk-scpsys.c | 42 ++++++++++++++++++-
> include/dt-bindings/clock/mt2712-clk.h | 12 +++++-
> include/dt-bindings/power/mt2712-power.h | 3 ++
> 5 files changed, 136 insertions(+), 18 deletions(-)
>
next prev parent reply other threads:[~2018-03-20 6:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 7:03 [PATCH v2 0/5] update Mediatek MT2712 clock and scpsys support Weiyi Lu
2018-03-12 7:03 ` Weiyi Lu
2018-03-12 7:03 ` [PATCH v2 1/5] dt-bindings: soc: update MT2712 power dt-bindings Weiyi Lu
2018-03-19 1:32 ` Matthias Brugger
2018-03-12 7:03 ` [PATCH v2 2/5] soc: mediatek: update power domain data of MT2712 Weiyi Lu
2018-03-19 1:33 ` Matthias Brugger
2018-03-12 7:03 ` [PATCH v2 3/5] dt-bindings: clock: add clocks for MT2712 Weiyi Lu
2018-03-18 12:48 ` Rob Herring
2018-03-19 21:38 ` Stephen Boyd
2018-03-12 7:03 ` [PATCH v2 4/5] arm64: dts: add clock device nodes of MT2712 Weiyi Lu
2018-03-12 7:03 ` [PATCH v2 5/5] clk: mediatek: update clock driver " Weiyi Lu
2018-03-19 21:38 ` Stephen Boyd
2018-03-20 6:07 ` Weiyi Lu [this message]
2018-03-20 7:23 ` [PATCH v2 0/5] update Mediatek MT2712 clock and scpsys support Stephen Boyd
2018-03-21 9:11 ` Matthias Brugger
2018-04-17 14:22 ` 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=1521526068.13313.8.camel@mtksdaap41 \
--to=weiyi.lu@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=fan.chen@mediatek.com \
--cc=jamesjj.liao@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=srv_heupstream@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