From: Felipe Balbi <me@felipebalbi.com>
To: "York, Jeffrey-P56387" <Jeff.York@gdc4s.com>
Cc: me@felipebalbi.com, linux-omap@vger.kernel.org
Subject: Re: FSUSB Register access
Date: Wed, 5 Nov 2008 03:11:42 +0200 [thread overview]
Message-ID: <20081105011142.GF4010@frodo> (raw)
In-Reply-To: <9D31108D62FAE54AA21AEF899D69931E0385AAF1@AZ25EXM04.gddsi.com>
On Tue, Nov 04, 2008 at 06:03:05PM -0700, York, Jeffrey-P56387 wrote:
> Balbi,
>
> Thanks for your help.
>
> See below for the answers.
>
> -----Original Message-----
> From: Felipe Balbi [mailto:me@felipebalbi.com]
> Sent: Tuesday, November 04, 2008 5:55 PM
> To: York, Jeffrey-P56387
> Cc: me@felipebalbi.com; linux-omap@vger.kernel.org
> Subject: Re: FSUSB Register access
>
> Hi,
>
> On Tue, Nov 04, 2008 at 05:38:28PM -0700, York, Jeffrey-P56387 wrote:
> > <JEFF SAYS: I did this and I do see logging now. It shows as
> expected
> > an external abort on non-linefetch when it tries to read from an FSUSB
> > register. As far as I can tell from the TI spec, I should only have
> to
> > enable the 48 MHz clock... And I know it is enabled via a read from
> the
> > CM_IDLEST_CKGEN register.>
>
> hmm.. yeah, looks like it's clock issue. Do you call:
>
> clk_get();
> clk_enable();
>
> before reading the register ?? Although, if CM_IDLEST_CKGEN says it's
> on, it should be.
>
> <JEFF SAYS: I do when trying to request the "usb_fck" and "usb_l4_ick".
> Not sure what the code is doing for the 48 MHz clock. That's done
> somewhere else in the Mobilinux kernel. Given that the register says
> its on, I was assuming that clock was good.>
still, you were getting the "unable to enable clock usb_fck after 1000000
tries" message, right ? But then again, the register says it's good.
So might be something elsewhere. Could you share your code ? It'd be
much simpler to say what's going on by looking at your code.
--
balbi
next prev parent reply other threads:[~2008-11-05 1:11 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 16:09 [REVIEW PATCH 0/9] DSS: Series description Tomi Valkeinen
2008-11-04 16:09 ` [REVIEW PATCH 1/9] DSS: Documentation for OMAP2/3 display subsystem Tomi Valkeinen
2008-11-05 7:56 ` [Linux-fbdev-devel] " Geert Uytterhoeven
2008-11-05 10:12 ` Tomi Valkeinen
2008-11-04 16:09 ` [REVIEW PATCH 2/9] DSS: New display subsystem driver for OMAP2/3 Tomi Valkeinen
2008-11-04 16:10 ` [REVIEW PATCH 3/9] DSS: RFBI support for OMAP2/3 DSS Tomi Valkeinen
2008-11-04 16:10 ` [REVIEW PATCH 4/9] DSS: TV-out " Tomi Valkeinen
2008-11-05 10:27 ` Jarkko Nikula
2008-11-04 16:10 ` [REVIEW PATCH 5/9] DSS: DSI " Tomi Valkeinen
2008-11-04 16:10 ` [REVIEW PATCH 6/9] DSS: OMAPFB: fb driver for new display subsystem Tomi Valkeinen
2008-11-04 16:10 ` [REVIEW PATCH 7/9] DSS: Add generic DVI panel Tomi Valkeinen
2008-11-04 16:10 ` [REVIEW PATCH 8/9] DSS: support for Beagle Board Tomi Valkeinen
2008-11-04 17:28 ` Koen Kooi
2008-11-05 10:05 ` Tomi Valkeinen
2008-11-05 21:15 ` Koen Kooi
2008-11-04 18:24 ` [Linux-fbdev-devel] " Tony Lindgren
2008-11-05 10:09 ` Tomi Valkeinen
2008-11-04 21:35 ` FSUSB Register access York, Jeffrey-P56387
2008-11-04 22:20 ` Felipe Balbi
2008-11-05 0:38 ` York, Jeffrey-P56387
2008-11-05 0:55 ` Felipe Balbi
2008-11-05 1:03 ` York, Jeffrey-P56387
2008-11-05 1:11 ` Felipe Balbi [this message]
2008-11-04 22:35 ` Woodruff, Richard
2008-11-05 10:27 ` [REVIEW PATCH 8/9] DSS: support for Beagle Board Jarkko Nikula
2008-11-05 23:21 ` David Brownell
2008-11-06 8:23 ` Tomi Valkeinen
2008-11-06 8:30 ` Koen Kooi
2008-11-04 16:10 ` [REVIEW PATCH 9/9] DSS: support for OMAP3 SDP board Tomi Valkeinen
2008-11-05 10:54 ` Jarkko Nikula
2008-11-10 4:03 ` [Linux-fbdev-devel] [REVIEW PATCH 0/9] DSS: Series description Shah, Hardik
2008-11-10 11:31 ` Tomi Valkeinen
2008-11-10 12:03 ` Shah, Hardik
2008-11-18 6:40 ` Shah, Hardik
2008-11-18 12:06 ` Tomi Valkeinen
2008-11-24 6:26 ` Arun KS
2008-11-24 6:30 ` Hiremath, Vaibhav
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=20081105011142.GF4010@frodo \
--to=me@felipebalbi.com \
--cc=Jeff.York@gdc4s.com \
--cc=linux-omap@vger.kernel.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