From: p.zabel@pengutronix.de (Philipp Zabel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM i.MX6q: Fix periph_clk2_sel and periph2_clk2_sel clocks
Date: Wed, 17 Apr 2013 12:06:19 +0200 [thread overview]
Message-ID: <1366193179.4389.1.camel@pizza.hi.pengutronix.de> (raw)
In-Reply-To: <516E5931.5010904@de.bosch.com>
Am Mittwoch, den 17.04.2013, 10:11 +0200 schrieb Dirk Behme:
> On 12.04.2013 11:03, Philipp Zabel wrote:
> > Am Freitag, den 12.04.2013, 11:02 +0800 schrieb Shawn Guo:
> >> On Thu, Apr 11, 2013 at 12:23:32PM +0200, Philipp Zabel wrote:
> >>> The periph_clk2_sel mux can be set to pll3, pll1, or
> >>> osc/pll2-bypass/pll2_burn_in_clk.
> >> Looking at IMX6DQRM Rev. 0, 11/2012, I see
> >>
> >> 13?12 periph_clk2_sel: Selector for peripheral clk2 clock multiplexer
> >>
> >> 00 derive clock from pll3_sw_clk
> >> 01 derive clock from pll1_ref_clk
> >> 10 derive clock from pll2_burn_in_clk (default)
> >> 11 reserved
> >>
> >> Are you sure pll1_ref_clk actually means pll1_sys?
> >
> > No, pll1_sys indeed is pll1_sw_clk, not pll1_ref_clk.
> >
> >> I searched the
> >> document and word "pll1_ref_clk" occurs only once. But Figure 18-5. BUS
> >> clock generation on page 819 suggests it's OSC_CLK (24M).
> >
> > This is consistent (24 MHz osc is the pll1 reference), and thus might be
> > correct. I'll fix the patch to keep periph_clk2_sels[1] = "osc".
>
> Any update on this?
Thank you for the reminder, I've sent v2.
regards
Philipp
prev parent reply other threads:[~2013-04-17 10:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-11 10:23 [PATCH] ARM i.MX6q: Fix periph_clk2_sel and periph2_clk2_sel clocks Philipp Zabel
2013-04-12 3:02 ` Shawn Guo
2013-04-12 9:03 ` Philipp Zabel
2013-04-17 8:11 ` Dirk Behme
2013-04-17 10:06 ` Philipp Zabel [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=1366193179.4389.1.camel@pizza.hi.pengutronix.de \
--to=p.zabel@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).