From: Marek Vasut <marek.vasut.n900@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] mx6: consolidating and extending anadig/analog/anatop register defs
Date: Tue, 14 Feb 2012 14:07:34 +0100 [thread overview]
Message-ID: <1329224854.5991.2.camel@konomi> (raw)
In-Reply-To: <4F3A5B25.80404@grandegger.com>
> Hi Marek,
>
> On 02/14/2012 01:37 PM, Marek Vasut wrote:
> > > Hi, Wolfgang,
> > >
> > > > -----Original Message-----
> > > > From: u-boot-bounces at lists.denx.de
> > > > [mailto:u-boot-bounces at lists.denx.de] On Behalf Of Wolfgang
> > > > Grandegger Sent: Monday, February 13, 2012 8:08 PM
> > > > To: U-Boot
> > > > Subject: [U-Boot] mx6: consolidating and extending
> > > > anadig/analog/anatop register defs
> > > >
> > > > Hello,
> > > >
> > > > for the USB support on MX6Q, I'm trying to consolidate and extend
> > > > the register definitions for the ANADIG registers. Unfortunately,
> > > > three different names are used for the same registers: ANADIG,
> > > > analog and ANATOP. Any idea what the names do stand for and what
> > > > would be the most appropriate one. Apart from that, we should have
> > > > a separate structure and header file for these registers.
> > > > Currently, they are added to the CCM regs.
> > >
> > > The register definition in the CCM according to the RM as followings:
> > > Addresses: CCM_analog_PLL_SYS is 0h base + 0h offset = 0000_0000h
> > > CCM_analog_PLL_SYS_SET is 0h base + 4h offset = 0000_0004h
> > > CCM_analog_PLL_SYS_CLR is 0h base + 8h offset = 0000_0008h
> > > CCM_analog_PLL_SYS_TOG is 0h base + Ch offset = 0000_000Ch
> > >
> > > Thus, I put the register definition into the CCM parts.
> >
> > This again resembles MX28 ... damn, can't we share some parts of MX28
> > for MX6Q ?
> >
> > Fabio, I think I'll need one too, this is getting weird ;-)
>
> Unfortunately, I did not get hold of a RM yet :(.
RM? Who's that?
It's still under NDA,
> I believe. Therefore I will postpone my "consolidation" activities for
> the time being.
Sorry, I don't intent to hinder your efforts, I'm just seeing a pattern :)
The USB support patch I sent does work, as Dirk
> confirmed, and therefore I suggest to apply it as intermediate solution.
Well ... All right then. Though my sense for perfect solution is hurting a lot ;-)
>
> Wolfgang.
next prev parent reply other threads:[~2012-02-14 13:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 12:07 [U-Boot] mx6: consolidating and extending anadig/analog/anatop register defs Wolfgang Grandegger
2012-02-13 12:34 ` Marek Vasut
2012-02-14 2:07 ` Liu Hui-R64343
2012-02-14 12:37 ` Marek Vasut
2012-02-14 13:01 ` Wolfgang Grandegger
2012-02-14 13:07 ` Marek Vasut [this message]
2012-02-14 13:13 ` Wolfgang Grandegger
2012-02-14 13:17 ` Stefano Babic
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=1329224854.5991.2.camel@konomi \
--to=marek.vasut.n900@gmail.com \
--cc=u-boot@lists.denx.de \
/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