From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 5/5] ARM64: MediaTek MT8173: Add SCPSYS device node
Date: Wed, 17 Jun 2015 09:56:47 +0200 [thread overview]
Message-ID: <20150617075647.GG6325@pengutronix.de> (raw)
In-Reply-To: <7hlhfjy0tq.fsf@deeprootsystems.com>
On Tue, Jun 16, 2015 at 11:17:53AM -0700, Kevin Hilman wrote:
> Sascha Hauer <s.hauer@pengutronix.de> writes:
>
> > This adds the SCPSYS device node to the MT8173 dtsi file.
> >
> > Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> > ---
> > arch/arm64/boot/dts/mediatek/mt8173.dtsi | 10 ++++++++++
> > 1 file changed, 10 insertions(+)
> >
> > diff --git a/arch/arm64/boot/dts/mediatek/mt8173.dtsi b/arch/arm64/boot/dts/mediatek/mt8173.dtsi
> > index 924fdb6..12430f0 100644
> > --- a/arch/arm64/boot/dts/mediatek/mt8173.dtsi
> > +++ b/arch/arm64/boot/dts/mediatek/mt8173.dtsi
> > @@ -125,6 +125,16 @@
> > <GIC_SPI 147 IRQ_TYPE_LEVEL_HIGH>;
> > };
> >
> > + scpsys: scpsys at 10006000 {
> > + compatible = "mediatek,mt8173-scpsys";
> > + #power-domain-cells = <1>;
> > + reg = <0 0x10006000 0 0x1000>;
> > + clocks = <&clk26m>,
> > + <&topckgen CLK_TOP_MM_SEL>;
>
> Neither your binding doc (nor the generic one) mentions these clock
> properties or what they are used for. They appear to define a clock
> that must be enabled in order to for the power domain to be on.
Ok, will add documentation for this.
>
> Also the order here seems rather important and probably needs
> documenting in the binding (e.g. the clk_id order is hard-coded in the
> driver.)
The order is not important, the clock-names property defines which clock
is which.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2015-06-17 7:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-09 8:46 [PATCH v4] Mediatek SCPSYS power domain support Sascha Hauer
2015-06-09 8:46 ` [PATCH 1/5] soc: mediatek: Add infracfg misc driver support Sascha Hauer
2015-06-09 8:47 ` [PATCH 2/5] dt-bindings: soc: Add documentation for the MediaTek SCPSYS unit Sascha Hauer
2015-06-09 8:47 ` [PATCH 3/5] soc: Mediatek: Add SCPSYS power domain driver Sascha Hauer
2015-06-10 12:03 ` Matthias Brugger
2015-06-10 14:47 ` Ulf Hansson
2015-06-15 7:45 ` Sascha Hauer
2015-06-09 8:47 ` [PATCH 4/5] ARM64: MediaTek: Add generic pm domain support Sascha Hauer
2015-06-09 8:47 ` [PATCH 5/5] ARM64: MediaTek MT8173: Add SCPSYS device node Sascha Hauer
2015-06-16 18:17 ` Kevin Hilman
2015-06-17 7:56 ` Sascha Hauer [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-05-20 14:18 [PATCH v3] Mediatek SCPSYS power domain support Sascha Hauer
2015-05-20 14:19 ` [PATCH 5/5] ARM64: MediaTek MT8173: Add SCPSYS device node Sascha Hauer
2015-05-21 14:32 ` Daniel Kurtz
2015-05-21 15:34 ` Matthias Brugger
2015-05-21 17:49 ` Sascha Hauer
2015-05-22 2:41 ` James Liao
2015-05-22 4:19 ` Daniel Kurtz
2015-05-22 5:40 ` James Liao
2015-05-22 6:12 ` Daniel Kurtz
2015-05-11 19:23 [PATCH v2] Mediatek SCPSYS power domain support Sascha Hauer
2015-05-11 19:23 ` [PATCH 5/5] ARM64: MediaTek MT8173: Add SCPSYS device node Sascha Hauer
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=20150617075647.GG6325@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).