From: Tony Lindgren <tony@atomide.com>
To: Brian Swetland <swetland@google.com>
Cc: Linux-omap-open-source@linux.omap.com
Subject: Re: omap clock.h question
Date: Tue, 7 Feb 2006 13:27:12 -0800 [thread overview]
Message-ID: <20060207212712.GE27148@atomide.com> (raw)
In-Reply-To: <20060207211002.GB5897@localhost.localdomain>
* Brian Swetland <swetland@google.com> [060207 13:10]:
> [Tony Lindgren <tony@atomide.com>]
> > * Brian Swetland <swetland@google.com> [060207 11:06]:
> > >
> > > I'm trying to get the MMC driver working on OMAP730 -- currently it
> > > fails in probe because it can't obtain "mmc1_ck". clocks.h has a
> > > definition for this, but only for 1510/16xx/310. OMAP730 appears to use
> > > a different config register (PERSEUS_PCC_CONF) to enable this clock.
> > >
> > > What's the correct way to support this? Define another clock struct
> > > with the same name, but setup for 730?
> >
> > Yes, just add another clock for 730. BTW, the mmc driver is about to
> > change where you just request mmc_ick and mmc_fck on all omaps.
>
> The mach-omap1/clock.h has no reference to _ick or _fck clocks right
> now. This will be coming as part of the change?
Oh yeah, just call it mmc_ck. It will change to figure out the mmc 1 or
2 clock based on the dev entry.
Tony
next prev parent reply other threads:[~2006-02-07 21:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-07 18:59 omap clock.h question Brian Swetland
2006-02-07 20:52 ` Tony Lindgren
2006-02-07 21:10 ` Brian Swetland
2006-02-07 21:27 ` Tony Lindgren [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-07 21:41 Woodruff, Richard
2006-02-07 21:53 ` Tony Lindgren
2006-02-07 22:06 Woodruff, Richard
2006-02-07 22:29 ` Tony Lindgren
2006-02-07 22:57 Woodruff, Richard
2006-02-07 23:12 ` Tony Lindgren
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=20060207212712.GE27148@atomide.com \
--to=tony@atomide.com \
--cc=Linux-omap-open-source@linux.omap.com \
--cc=swetland@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.