From: Emil Medve <Emilian.Medve@Freescale.com>
To: Scott Wood <scottwood@Freescale.com>
Cc: yuantian.tang@Freescale.com, linuxppc-dev@lists.ozlabs.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/3] powerpc/dts: Factorize the clock control node
Date: Thu, 30 Oct 2014 08:58:29 -0500 [thread overview]
Message-ID: <54524405.5090509@Freescale.com> (raw)
In-Reply-To: <1414538500.23458.125.camel@snotra.buserror.net>
Hello Scott,
On 10/28/2014 06:21 PM, Scott Wood wrote:
> On Wed, 2014-10-22 at 09:42 -0500, Emil Medve wrote:
>> Signed-off-by: Emil Medve <Emilian.Medve@Freescale.com>
>> Change-Id: I25ce24a25862b4ca460164159867abefe00ccdd1
>
> Please remove gerrit stuff prior to submitting.
I did remove the bulk of it. I wanted to keep the Change-Id so I can
easily correlate the upstream patches with the sordid internal history.
Seems the upstream history has enough instances of 'Change-Id' for this
not to be an issue
>> diff --git a/arch/powerpc/boot/dts/fsl/qoriq-clockgen1.dtsi b/arch/powerpc/boot/dts/fsl/qoriq-clockgen1.dtsi
>> new file mode 100644
>> index 0000000..4871048
>> --- /dev/null
>> +++ b/arch/powerpc/boot/dts/fsl/qoriq-clockgen1.dtsi
>> @@ -0,0 +1,78 @@
>> +/*
>> + * QorIQ clock control device tree stub [ controller @ offset 0xe1000 ]
>> + *
>> + * Copyright 2014 Freescale Semiconductor Inc.
>> + *
>> + * Redistribution and use in source and binary forms, with or without
>> + * modification, are permitted provided that the following conditions are met:
>> + * * Redistributions of source code must retain the above copyright
>> + * notice, this list of conditions and the following disclaimer.
>> + * * Redistributions in binary form must reproduce the above copyright
>> + * notice, this list of conditions and the following disclaimer in the
>> + * documentation and/or other materials provided with the distribution.
>> + * * Neither the name of Freescale Semiconductor nor the
>> + * names of its contributors may be used to endorse or promote products
>> + * derived from this software without specific prior written permission.
>> + *
>> + *
>> + * ALTERNATIVELY, this software may be distributed under the terms of the
>> + * GNU General Public License ("GPL") as published by the Free Software
>> + * Foundation, either version 2 of that License or (at your option) any
>> + * later version.
>> + *
>> + * THIS SOFTWARE IS PROVIDED BY Freescale Semiconductor ``AS IS'' AND ANY
>> + * EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
>> + * WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
>> + * DISCLAIMED. IN NO EVENT SHALL Freescale Semiconductor BE LIABLE FOR ANY
>> + * DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
>> + * (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
>> + * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
>> + * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
>> + * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
>> + * SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
>> + */
>> +
>> +global-utilities@e1000 {
>> + compatible = "fsl,qoriq-clockgen-1.0";
>> + ranges = <0x0 0xe1000 0x1000>;
>> + reg = <0xe1000 0x1000>;
>> + clock-frequency = <0>;
>> + #address-cells = <1>;
>> + #size-cells = <1>;
>> +
>> + sysclk: sysclk {
>> + #clock-cells = <0>;
>> + compatible = "fsl,qoriq-sysclk-1.0", "fixed-clock";
>> + clock-output-names = "sysclk";
>> + };
>> + pll0: pll0@800 {
>> + #clock-cells = <1>;
>> + reg = <0x800 0x4>;
>> + compatible = "fsl,qoriq-core-pll-1.0";
>> + clocks = <&sysclk>;
>> + clock-output-names = "pll0", "pll0-div2";
>> + };
>> + pll1: pll1@820 {
>> + #clock-cells = <1>;
>> + reg = <0x820 0x4>;
>> + compatible = "fsl,qoriq-core-pll-1.0";
>> + clocks = <&sysclk>;
>> + clock-output-names = "pll1", "pll1-div2";
>> + };
>> + mux0: mux0@0 {
>> + #clock-cells = <0>;
>> + reg = <0x0 0x4>;
>> + compatible = "fsl,qoriq-core-mux-1.0";
>> + clocks = <&pll0 0>, <&pll0 1>, <&pll1 0>, <&pll1 1>;
>> + clock-names = "pll0", "pll0-div2", "pll1", "pll1-div2";
>> + clock-output-names = "cmux0";
>> + };
>> + mux1: mux1@20 {
>> + #clock-cells = <0>;
>> + reg = <0x20 0x4>;
>> + compatible = "fsl,qoriq-core-mux-1.0";
>> + clocks = <&pll0 0>, <&pll0 1>, <&pll1 0>, <&pll1 1>;
>> + clock-names = "pll0", "pll0-div2", "pll1", "pll1-div2";
>> + clock-output-names = "cmux1";
>> + };
>> +};
>
> I don't think the mux stuff belongs here, given that clockgen2.dtsi
> doesn't have it, and I saw at least one clockgen1 user needing to
> supplement this with more muxes.
The intent was to put here devices/nodes that are common per chassis
from the low to high end. Specific SoC would change/augment this as
appropriate. I could have put each node in its own file as we've done
elsewhere, but I thought it would be too much
Yes, chassis v1 and v2 have differences, but that's not unexpected
>> @@ -1068,7 +1043,6 @@
>> clocks = <&sysclk>;
>> clock-output-names = "pll2", "pll2-div2", "pll2-div4";
>> };
>> -
>> pll3: pll3@860 {
>> #clock-cells = <1>;
>> reg = <0x860 0x4>;
>> @@ -1076,7 +1050,6 @@
>> clocks = <&sysclk>;
>> clock-output-names = "pll3", "pll3-div2", "pll3-div4";
>> };
>> -
>> pll4: pll4@880 {
>> #clock-cells = <1>;
>> reg = <0x880 0x4>;
>
> Why?
Why what?
Cheers,
next prev parent reply other threads:[~2014-10-30 14:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 14:42 [PATCH 1/3] powerpc/dts: Factorize the clock control node Emil Medve
2014-10-22 14:42 ` [PATCH 2/3] dt/bindings: qoriq-clock: Add binding for the platform PLL Emil Medve
2014-10-28 23:23 ` Scott Wood
2014-10-22 14:42 ` [PATCH 3/3] powerpc/dts: Add node(s) " Emil Medve
2014-10-28 23:21 ` [PATCH 1/3] powerpc/dts: Factorize the clock control node Scott Wood
2014-10-30 13:58 ` Emil Medve [this message]
2014-10-30 23:21 ` Scott Wood
2014-11-06 15:34 ` Emil Medve
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=54524405.5090509@Freescale.com \
--to=emilian.medve@freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=scottwood@Freescale.com \
--cc=yuantian.tang@Freescale.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).