From: r.herring@freescale.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mx25: set GPT clock source to PER
Date: Tue, 06 Jul 2010 09:06:55 -0500 [thread overview]
Message-ID: <1278425215.4396.45.camel@ra7055-laptop> (raw)
In-Reply-To: <20100706073314.GJ26079@pengutronix.de>
On Tue, 2010-07-06 at 09:33 +0200, Sascha Hauer wrote:
> On Tue, Jul 06, 2010 at 09:35:11AM +0300, Baruch Siach wrote:
> > > In any case, we can't apply your patch because it would break other v2
> > > based architectures like i.MX35.
> >
> > What do you suggest then?
>
> Tell the timer code which clock to use with an argument to
> mxc_timer_init() and add the missing clocks to the clock.c file. You
> also have to pass this argument through from the board to
> mx25_clocks_init(). That's a lot of work and in the end we still do not
> know why some i.MX25 variants need the peripheral clock and others need
> the ipg clock. So what I really suggest is that you invest some
> research to find the source of this strangeness. Some things that could
> help you are:
>
> - the clko pin
> - Do both boards have identical i.MX25 tapeout versions?
> - Are the clocks initialized identically?
>
> I bricked my i.MX25 PDK so unfortunately I do not have any hardware to
> do some tests myself.
There are no Si issues with MX25 that would cause per_clk to not work.
There are 2 possible clocking configurations and it is not tied to v1
vs. v2 timer hardware:
ipg_clk and per_clk are same clock source - MX1, MX21, MX31
per_clk is independent clock - every other i.MX chip
The correct setup is to use per_clk as ipg_clk can change frequencies
for bus scaling in the latter case.
Rob
next prev parent reply other threads:[~2010-07-06 14:06 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 15:00 [PATCH 0/2] mx25: clock related fixes Baruch Siach
2010-01-21 15:00 ` [PATCH 1/2] mx25: remove unused mx25_clocks_init() argument Baruch Siach
2010-01-21 15:00 ` [PATCH 2/2] mx25: properly initialize clocks, fix time accounting Baruch Siach
2010-01-22 6:50 ` Baruch Siach
2010-01-22 7:57 ` Sascha Hauer
2010-01-25 10:54 ` Baruch Siach
2010-01-25 10:58 ` [PATCH 1/4] mx25: remove unused mx25_clocks_init() argument Baruch Siach
2010-01-25 10:58 ` [PATCH 2/4] mx25: properly initialize clocks Baruch Siach
2010-07-05 7:08 ` Uwe Kleine-König
2010-07-08 10:04 ` Baruch Siach
2010-01-25 10:58 ` [PATCH 3/4] mx25: fix time accounting Baruch Siach
2010-01-25 11:11 ` Lothar Waßmann
2010-01-25 15:01 ` Baruch Siach
2010-05-11 15:43 ` Sascha Hauer
2010-05-12 5:06 ` Baruch Siach
2010-05-12 9:46 ` Sascha Hauer
2010-05-12 10:45 ` Baruch Siach
2010-05-12 12:09 ` Sascha Hauer
2010-07-06 15:28 ` Rob Herring
2010-07-04 8:43 ` Baruch Siach
2010-07-04 8:47 ` [PATCH] mx25: set GPT clock source to PER Baruch Siach
2010-07-05 8:21 ` Sascha Hauer
2010-07-06 6:35 ` Baruch Siach
2010-07-06 7:33 ` Sascha Hauer
2010-07-06 14:06 ` Rob Herring [this message]
2010-07-07 8:00 ` Baruch Siach
2010-07-07 10:28 ` Sascha Hauer
2010-07-07 13:04 ` Baruch Siach
2010-07-05 11:18 ` [PATCH 3/4] mx25: fix time accounting Martin Fuzzey
2010-01-25 10:58 ` [PATCH 4/4] mx25: make the FEC AHB clk secondary of the IPG Baruch Siach
2010-01-22 7:58 ` [PATCH 2/2] mx25: properly initialize clocks, fix time accounting Sascha Hauer
2010-01-22 7:59 ` 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=1278425215.4396.45.camel@ra7055-laptop \
--to=r.herring@freescale.com \
--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