mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Rolf Evers-Fischer <embedded24@evers-fischer.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: New driver crashes with "unable to handle paging request"
Date: Wed, 30 Apr 2014 16:08:04 +0200 (CEST)	[thread overview]
Message-ID: <1987921723.106566.1398866884871.open-xchange@email.1und1.de> (raw)
In-Reply-To: <1748480871.292241.1398329548811.open-xchange@email.1und1.de>

I have resolved the problem by enabling the USB clocks:
Write "2" to register "CM_PER_USB0_CLKCTRL" (address 0x44e0001c).

Kind regards,
 Rolf


> Rolf Evers-Fischer <embedded24@evers-fischer.de> hat am 24. April 2014 um
> 10:52 geschrieben:
>
>
>
> Hi Sascha,
>
> > Sascha Hauer <s.hauer@pengutronix.de> hat am 24. April 2014 um 08:58
> > geschrieben:
> >
> >
> > Hi Rolf,
> >
> > On Wed, Apr 23, 2014 at 06:09:40PM +0200, Rolf Evers-Fischer wrote:
> > > I'm just trying to port the USB driver "musb" (for the AM335x platform)
> > > from
> > > linux kernel to barebox.
> > > But whenever I want to read any address in the range
> > > 0x47401400-0x474017ff,
> > > the
> > > barebox crashes with "unable to handle paging request".
> > > I have already tried to invoke a "map_io_sections(0x0, 0x47400000,
> > > 0x2000)",
> > > but
> > > it didn't help.
> >
> > barebox creates a flat 1:1 mapping when the MMU is enabled. You won't
> > need any calls to map_io_sections or some ioremap correspondent
> > function.
> >
>
> Thank you. That's good to know.
>
> > It may be that you have to enable some bus clocks in order to access the
> > musb.
> >
>
> Maybe. I found this in TI's "Technical Reference Manual":
> "Prior to configuring the USB Module Registers, the USB SubSystem and PHY are
> required to be released
> from reset, enable interconnects and controllers clocks as well as configure
> the
> USB PHY with appropriate
> setting."
>
> Quite a lot of work, but I'll definitely have to check it.
>
> > To make sure you don't have MMU trouble could you post the output of
> > 'mmuinfo 0x47400000'?
> >
>
> PAR result for 0x47400000:
>  privileged read: 0x47400290
>   Physical Address [31:12]: 0x47400000
>   Reserved [11]:            0x0
>   Not Outer Shareable [10]: 0x0
>   Non-Secure [9]:           0x1
>   Impl. def. [8]:           0x0
>   Shareable [7]:            0x1
>   Inner mem. attr. [6:4]:   0x1 (0b001 Strongly-ordered)
>   Outer mem. attr. [3:2]:   0x0 (0b00 Non-cacheable)
>   SuperSection [1]:         0x0
>   Failure [0]:              0x0
>  privileged write: 0x47400290
>   Physical Address [31:12]: 0x47400000
>   Reserved [11]:            0x0
>   Not Outer Shareable [10]: 0x0
>   Non-Secure [9]:           0x1
>   Impl. def. [8]:           0x0
>   Shareable [7]:            0x1
>   Inner mem. attr. [6:4]:   0x1 (0b001 Strongly-ordered)
>   Outer mem. attr. [3:2]:   0x0 (0b00 Non-cacheable)
>   SuperSection [1]:         0x0
>   Failure [0]:              0x0
>
>
> Best regards,
>  Rolf

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

  reply	other threads:[~2014-04-30 14:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-23 16:09 Rolf Evers-Fischer
2014-04-24  6:58 ` Sascha Hauer
2014-04-24  8:52   ` Rolf Evers-Fischer
2014-04-30 14:08     ` Rolf Evers-Fischer [this message]
2014-05-01 22:50       ` Christoph Fritz
2014-05-05 12:13         ` Rolf Evers-Fischer
2014-05-12 12:57           ` Rolf Evers-Fischer
2014-05-13 11:03             ` Alexander Aring
2014-05-13 12:49               ` Christoph Fritz
2014-05-15 11:37                 ` Rolf Evers-Fischer

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=1987921723.106566.1398866884871.open-xchange@email.1und1.de \
    --to=embedded24@evers-fischer.de \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.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