mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Christoph Fritz <chf.fritz@googlemail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>,
	Alexander Shiyan <shc_work@mail.ru>
Cc: barebox@lists.infradead.org
Subject: Re: Re[5]: Omap4 DSS clocks
Date: Fri, 15 Mar 2013 09:20:00 +0100	[thread overview]
Message-ID: <1363335600.13088.40.camel@mars> (raw)
In-Reply-To: <1363278551.867951799@f270.mail.ru>

On Thu, 2013-03-14 at 20:29 +0400, Alexander Shiyan wrote:
> > On Thu, 2013-03-14 at 14:46 +0100, Christoph Fritz wrote:
> > > On Thu, 2013-03-14 at 14:33 +0100, Sascha Hauer wrote:
> > 
> > > > I wouldn't expect a bug in the code. This would have been discovered
> > > > already.
> > > 
> > > Register CM_DSS_DSS_CLKCTRL (0x4a009120) reads 0x00070F02 and so the
> > > field [17:16] IDLEST reads 0x3 which means "Module is disabled and
> > > cannot be accessed". On linux, its 0x2 which means "functional".

Sascha, any comments on this?
 
> > I already asked about this on the TI E2E Community forum
> > http://e2e.ti.com/support/omap/f/849/t/251717.aspx but without gaining
> > success.
> > 
> > Overall, isn't it weird that DSS is offline (as indicated by IDLEST)?
> > 
> > I suppose in ./arch/arm/mach-omap/omap4_clock.c this check:
> > 
> > /* Check for DSS Clocks */
> > while ((__raw_readl(0x4A009100) & 0xF00) != 0xE00)
> > 	;
> > 
> > should get extended to also check for correct IDLEST ...which would
> > currently end in an endless loop :)
> 
> I revised commands/mem. All correct in the code, so problem is not here.

Thanks for pointing this out.

> About DSS: I cannot help you with this CPU, but here is one point from
> OMAP4430TRM:
> "The main access to all DSS registers is through the L3 interconnect.
> The access through the L4_PER interconnect is provided for back software
> compatibility."

I stumbled upon these lines too but have no clue what this means for
barebox command "md" concrete.

> Maybe it help you.

Thanks a lot for trying
 -- Christoph






_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2013-03-15  8:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-14 12:19 Christoph Fritz
2013-03-14 12:48 ` Alexander Shiyan
2013-03-14 12:51   ` Christoph Fritz
2013-03-14 13:02     ` Re[2]: " Alexander Shiyan
2013-03-14 13:11       ` Re[3]: " Alexander Shiyan
2013-03-14 13:23         ` Christoph Fritz
2013-03-14 13:33           ` Sascha Hauer
2013-03-14 13:46             ` Christoph Fritz
2013-03-14 15:06               ` Christoph Fritz
2013-03-14 16:29                 ` Re[5]: " Alexander Shiyan
2013-03-15  8:20                   ` Christoph Fritz [this message]
2013-03-15  8:40                     ` Re[7]: " Alexander Shiyan
2013-03-15 13:39                       ` [PATCH] [RFC] ARM OMAP4: enable DSS by default Christoph Fritz
2013-04-04  6:42                         ` Christoph Fritz
2013-04-05  6:39                           ` Re[2]: " Alexander Shiyan

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=1363335600.13088.40.camel@mars \
    --to=chf.fritz@googlemail.com \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shc_work@mail.ru \
    /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