public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: linux-omap@vger.kernel.org, Paul Walmsley <paul@pwsan.com>,
	Stanley Miao <stanley.miao@windriver.com>
Subject: Re: OMAP1: mcbsp clocks
Date: Fri, 23 Jan 2009 09:54:01 -0800	[thread overview]
Message-ID: <20090123175401.GU7172@atomide.com> (raw)
In-Reply-To: <20090123174249.GM26184@n2100.arm.linux.org.uk>

* Russell King - ARM Linux <linux@arm.linux.org.uk> [090123 09:43]:
> On Thu, Jan 22, 2009 at 05:17:28PM -0800, Tony Lindgren wrote:
> > Basically we currently cannot use virtual clocks because of this
> > and the fact that the parent of the virtual clock may not be known
> > as pointed out by Paul Walmsley.
> 
> One other thing I'd like to confirm is how the kernel treats the OMAP5912.
> OMAP5912 is interesting to me at the moment because it seems that all
> the information on it is freely available.  I don't know about the
> others.
> 
> However, it would be useful to know how the kernel treats this - iow,
> which of the four categories for OMAP1 SoCs - 310, 730, 1510, 1610.

5912 = 1611b = 16xx. Then 1710 is quite similar.

> Of course, if someone knows (or can send me, maybe Richard W?) where
> there's a similar document to spru751a for the clock architecture for
> these other CPUs (and OMAP2420, OMAP2430, OMAP3430, etc) it would be
> most useful.

I have some links on my webpage to the docs:

http://www.muru.com/linux/omap/

Still no public docs for 24xx :(

Tony

  reply	other threads:[~2009-01-23 17:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-22 23:55 OMAP1: mcbsp clocks Russell King - ARM Linux
2009-01-23  1:17 ` Tony Lindgren
2009-01-23 17:42   ` Russell King - ARM Linux
2009-01-23 17:54     ` Tony Lindgren [this message]
2009-01-23 19:03       ` Hunter, Jon
2009-01-23 19:17         ` Tony Lindgren
2009-01-23 19:26           ` Premi, Sanjeev
     [not found]           ` <b6ab3a160901231159xcfca2ebx3e7390e195bfa102@mail.gmail.com>
2009-01-23 20:02             ` Fwd: " Alejandro Blanca G.
2009-01-23 21:29               ` Hunter, Jon
     [not found]                 ` <b6ab3a160901231347n67feec99va7731328671925fe@mail.gmail.com>
2009-01-23 21:48                   ` Alejandro Blanca G.
2009-01-23 22:54                     ` Hunter, Jon
2009-01-24  4:28                       ` Alejandro Blanca G.
2009-01-23 17:18 ` Hunter, Jon
2009-01-23 17:31   ` Russell King - ARM Linux

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=20090123175401.GU7172@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=paul@pwsan.com \
    --cc=stanley.miao@windriver.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