linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: Elaine Zhang <zhangqing@rock-chips.com>
Cc: cl@rock-chips.com, robh+dt@kernel.org, mark.rutland@arm.com,
	zhengxing@rock-chips.com, andy.yan@rock-chips.com,
	jay.xu@rock-chips.com, matthias.bgg@gmail.com,
	paweljarosz3691@gmail.com, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	wsa@the-dreams.de, linux-i2c@vger.kernel.org, jic23@kernel.org,
	knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net,
	wxt@rock-chips.com, david.wu@rock-chips.com,
	linux-iio@vger.kernel.org, shawn.lin@rock-chips.com,
	akpm@linux-foundation.org, dianders@chromium.org,
	yamada.masahiro@socionext.com, catalin.marinas@arm.com,
	will.deacon@arm.com, afaerber@suse.de, shawnguo@kernel.org,
	khilman@baylibre.com, arnd@arndb.de, fabio.estevam@nxp.com,
	kever.yang@rock-chips.com, tony.xie@rock-chips.com,
	huangtao@rock-chips.com, yhx@rock-chips.com,
	rocky.hao@rock-chips.com
Subject: Re: [PATCH v4 4/6] arm64: dts: rockchip: add core dtsi file for RK3328 SoCs
Date: Wed, 05 Apr 2017 12:11:11 +0200	[thread overview]
Message-ID: <4811905.ImQG7774i7@diego> (raw)
In-Reply-To: <58E4516D.4000805@rock-chips.com>

Hi Elaine,

Am Mittwoch, 5. April 2017, 10:07:41 CEST schrieb Elaine Zhang:
> On 04/05/2017 12:04 AM, Heiko Stuebner wrote:
> > Am Montag, 27. März 2017, 17:40:48 CEST schrieb cl@rock-chips.com:
> >> From: Liang Chen <cl@rock-chips.com>
> >> 
> >> This patch adds core dtsi file for Rockchip RK3328 SoCs.
> >> 
> >> Signed-off-by: Liang Chen <cl@rock-chips.com>
> > 
> > applied for 4.12, with the following list of changes:
> > 
> > - reorder some properties to bring them in alphabetical order
> > - dropped the status-disabled from the power-controller
> > 
> >    power-domain control is a quite essential part of the system, so if
> >    boards really want to disable them, they should do it in their board
> >    file
> >    Having power-domains on all the time, is also our default in all other
> >    devicetrees.
> > 
> > - removed #dma-cells from spi0 -> this is not a dma controller
> > - reword the cru assigned-clocks comment a bit
> > - fixed sdmmc1_bus4 pins, as indicated by Shawn and after looking up the
> > 
> >    correct pins in the manual
> > 
> > And a final question, are you sure about SCLK_PDM becoming a child of the
> > APLL in your cru assigned-clocks, as the APLL will vary later on with
> > cpufreq active?
> 
> the NPLL will vary later on with cpufreq active.
> 
> The NPLL is better than APLL, so NPLL is for clk_core,and apll is for pdm.
> 
> please see the TRM in CRU:
> 1.4 Function Description
> /........./
> To maximize the flexibility, some of clocks can select divider source
> from 5 PLLs. (Note: It’s
> recommended to use NEW PLL instead of ARM PLL as arm clock source,
> because NEW PLL is
> near to ARM. And it’s jitter is better than ARM PLL).

Thanks for the clarification - this way it definitly makes sense.


Thanks
Heiko

  reply	other threads:[~2017-04-05 10:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-27  9:40 [PATCH v4 0/6] initialize dtsi file and dts file for RK3328 SoCs cl
2017-03-27  9:40 ` [PATCH v4 1/6] dt-bindings: iio: rockchip-saradc: add support for rk3328 cl
2017-03-27 13:25   ` Heiko Stuebner
2017-04-02  8:58     ` Jonathan Cameron
2017-03-27  9:40 ` [PATCH v4 3/6] dt-bindings: soc: rockchip: grf: " cl
2017-04-04 15:44   ` Heiko Stuebner
2017-03-27  9:40 ` [PATCH v4 4/6] arm64: dts: rockchip: add core dtsi file for RK3328 SoCs cl
2017-03-31  8:27   ` Shawn Lin
2017-04-04 16:04   ` Heiko Stuebner
2017-04-05  2:07     ` Elaine Zhang
2017-04-05 10:11       ` Heiko Stübner [this message]
2017-03-27  9:40 ` [PATCH v4 5/6] arm64: dts: rockchip: add dts file for RK3328 cl
2017-04-04 16:15   ` Heiko Stuebner
2017-03-27  9:46 ` [PATCH v4 6/6] dt-bindings: document rockchip rk3328-evb board cl
2017-04-04 16:10   ` Heiko Stuebner
2017-03-30 15:05 ` [PATCH v4 0/6] initialize dtsi file and dts file for RK3328 SoCs Wolfram Sang

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=4811905.ImQG7774i7@diego \
    --to=heiko@sntech.de \
    --cc=afaerber@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=andy.yan@rock-chips.com \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=cl@rock-chips.com \
    --cc=david.wu@rock-chips.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=fabio.estevam@nxp.com \
    --cc=huangtao@rock-chips.com \
    --cc=jay.xu@rock-chips.com \
    --cc=jic23@kernel.org \
    --cc=kever.yang@rock-chips.com \
    --cc=khilman@baylibre.com \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=matthias.bgg@gmail.com \
    --cc=paweljarosz3691@gmail.com \
    --cc=pmeerw@pmeerw.net \
    --cc=robh+dt@kernel.org \
    --cc=rocky.hao@rock-chips.com \
    --cc=shawn.lin@rock-chips.com \
    --cc=shawnguo@kernel.org \
    --cc=tony.xie@rock-chips.com \
    --cc=will.deacon@arm.com \
    --cc=wsa@the-dreams.de \
    --cc=wxt@rock-chips.com \
    --cc=yamada.masahiro@socionext.com \
    --cc=yhx@rock-chips.com \
    --cc=zhangqing@rock-chips.com \
    --cc=zhengxing@rock-chips.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).