From: Shawn Guo <shawnguo@kernel.org>
To: Bai Ping <ping.bai@nxp.com>
Cc: kernel@pengutronix.de, pawel.moll@arm.com, robh+dt@kernel.org,
mturquette@baylibre.com, sboyd@codeaurora.org,
linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, jacky.baip@gmail.com
Subject: Re: [PATCH V3 1/5] clk: imx: Add clock support for imx6qp
Date: Sun, 14 Feb 2016 11:21:03 +0800 [thread overview]
Message-ID: <20160214032103.GD6756@tiger> (raw)
In-Reply-To: <1454407298-15545-1-git-send-email-ping.bai@nxp.com>
On Tue, Feb 02, 2016 at 06:01:34PM +0800, Bai Ping wrote:
> most of the clock tree structures on i.MX6 Quad Plus are
> same as on i.MX6Q. there still some differences between
> these two SOCs. compared to the i.XM6Q, the differents of
> clocks on i.MX6QP is mainly on:
>
> 1. New clock gate added to support the PRE and PRG modules
> 2. 24MHz OSC clock option added to the UART, IPG, ECSPI, and
> CAN clock roots.
> 3. MMDC channel 1 clock gate is now controllable.
> 4. clock gating added to the LDB_DIx_IPU clocks on i.MX6QP
> 5. EMI clock root divider fix
> 6. other updates fo CSCMRx, CSCDRx and CS2CDR registers.
>
> detailed infomation, please refer to the i.MX6QP RM.
>
> Signed-off-by: Bai Ping <ping.bai@nxp.com>
Applied all, thanks.
prev parent reply other threads:[~2016-02-14 3:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 10:01 [PATCH V3 1/5] clk: imx: Add clock support for imx6qp Bai Ping
2016-02-02 10:01 ` [PATCH V3 2/5] ARM: dts: imx: Add basic dts support for imx6qp SOC Bai Ping
2016-02-02 10:01 ` [PATCH V3 3/5] ARM: dts: imx: Add basic dts support for imx6qp-sabreauto Bai Ping
2016-02-02 10:01 ` [PATCH V3 4/5] ARM: dts: imx: Add basic dts support for imx6qp-sabresd Bai Ping
[not found] ` <1454407298-15545-1-git-send-email-ping.bai-3arQi8VN3Tc@public.gmane.org>
2016-02-02 10:01 ` [PATCH V3 5/5] ARM: imx: Add msl code support for imx6qp Bai Ping
2016-02-14 3:21 ` Shawn Guo [this message]
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=20160214032103.GD6756@tiger \
--to=shawnguo@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jacky.baip@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=pawel.moll@arm.com \
--cc=ping.bai@nxp.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.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).