From: Roger Quadros <rogerq@ti.com>
To: "Kristo, Tero" <t-kristo@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Cc: "Menon, Nishanth" <nm@ti.com>,
"tony@atomide.com" <tony@atomide.com>,
Michael Trimarchi <michael@amarulasolutions.com>,
"Balbi, Felipe" <balbi@ti.com>,
George Cherian <george.cherian@ti.com>
Subject: omap USB_DPLL not configured as per manual
Date: Tue, 14 Oct 2014 13:47:33 +0300 [thread overview]
Message-ID: <543CFF45.4090202@ti.com> (raw)
Hi Tero,
The USB_DPLL doesn't have recommended M/N settings as per the TRM [1]
Thus the omapconf audit fails.
Any ideas of how we can fix this up? Should we add a new clock.ops structure for
USB_DPLL to make sure that we don't violate the TRM recommended settings?
or should we just add some flags in dpll_data? We would need a new compatible id for sure.
[1] - OMAP4460_ES1.x_NDA_TRM_vP.pdf - 3.6.3.9.5 DPLL_USB Preferred Settings
panda4460> omapconf audit dpll -d usb
|-------------------------------------------------------------------------------------|
| DPLL_USB AUDIT (@OPP OPP100, sysclk=38.4MHz) | Current Setting | Expected | STATUS |
|-------------------------------------------------------------------------------------|
| Status | Locked | Locked | Pass |
| Mode | Lock | Lock | Pass |
| Autoidle Mode | Auto LPST | Auto LPST | Pass |
| Low-Power Mode | Disabled | Disabled | Pass |
| REGM4XEN Mode | Disabled | Disabled | Pass |
| DCC Mode | Disabled | Disabled | Pass |
| M Divider | 25 | 400 | FAIL |
| N Divider | 0 | 15 | FAIL |
| Lock Frequency | 960.0MHz | 960.0MHz | Pass |
| M2 Divider | 2 | 2 | Pass |
| CLKOUT Output Rate | 480.0MHz | 480.0MHz | Pass |
| CLKDCOLDO Output Rate | 960.0MHz | 960.0MHz | Pass |
|-------------------------------------------------------------------------------------|
cheers,
-roger
next reply other threads:[~2014-10-14 10:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 10:47 Roger Quadros [this message]
2014-10-14 19:49 ` omap USB_DPLL not configured as per manual Tero Kristo
2014-10-15 8:22 ` Roger Quadros
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=543CFF45.4090202@ti.com \
--to=rogerq@ti.com \
--cc=balbi@ti.com \
--cc=george.cherian@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=michael@amarulasolutions.com \
--cc=nm@ti.com \
--cc=t-kristo@ti.com \
--cc=tony@atomide.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.