public inbox for linuxppc-dev@ozlabs.org
 help / color / mirror / Atom feed
From: Juergen Beisert <jbe@pengutronix.de>
To: linuxppc-dev@ozlabs.org
Cc: s104259@yahoo.it, Gary Thomas <gary@mlbassoc.com>,
	gianfranco.casanova@alice.it
Subject: Re: R: Installation on a MPC5200 based custom board
Date: Fri, 5 Dec 2008 18:36:50 +0100	[thread overview]
Message-ID: <200812051836.50960.jbe@pengutronix.de> (raw)
In-Reply-To: <47602D18F269934AB73B7E550804A1E002137985@FBCMST09V03.fbc.local>

On Freitag, 5. Dezember 2008, gianfranco.casanova@alice.it wrote:
> ========================================================
>
> Now plugging-in USB:
>
> ========================================================
>
> root@RadioNav: ~ #[   17.228078] hub 1-0:1.0: state 7 ports 2 chg 0000 evt
> 0004 root@RadioNav: ~ #[   17.233798] ppc-of-ohci f0001000.usb: GetStatus
> roothub.portstatus [1] = 0x00010101 CSC PPS CCS root@RadioNav: ~ #[  
> 17.242776] hub 1-0:1.0: port 2, status 0101, change 0001, 12 Mb/s
> root@RadioNav: ~ #[   17.374796] hub 1-0:1.0: debounce: port 2: total 100ms
> stable 100ms status 0x101 root@RadioNav: ~ #[   17.450780] ppc-of-ohci
> f0001000.usb: GetStatus roothub.portstatus [1] = 0x00100103 PRSC PPS PES
> CCS root@RadioNav: ~ #[   17.514787] usb 1-2: new full speed USB device
> using ppc-of-ohci and address 2 root@RadioNav: ~ #[   24.027842] usb 1-2:
> khubd timed out on ep0in len=0/64 root@RadioNav: ~ #[   29.199841] usb 1-2:
> khubd timed out on ep0in len=0/64 root@RadioNav: ~ #[   34.307841] usb 1-2:
> khubd timed out on ep0in len=0/64 root@RadioNav: ~ #[   34.382786]
> ppc-of-ohci f0001000.usb: GetStatus roothub.portstatus [1] = 0x00100103
> PRSC PPS PES CCS root@RadioNav: ~ #[   34.446789] usb 1-2: device
> descriptor read/64, error -110 root@RadioNav: ~ #
> root@RadioNav: ~ #cat /proc/interrupts
>            CPU0
> 134:       5689  MPC52xx Peripherals Edge      ohci_hcd:usb1
> 139:        207  MPC52xx Peripherals Edge      mpc52xx_psc_uart
> 143:          0  MPC52xx Peripherals Edge      i2c-mpc
> 144:          0  MPC52xx Peripherals Edge      i2c-mpc
> BAD:          0
> root@RadioNav: ~ #
>
> ========================================================
>
> we were thinking to some problem like:
>
> http://www.nabble.com/USB-support-on-mpc5200-broken-td19658810.html
>
> or
>
> http://www.nabble.com/MPC5200-PCI-interrupt-routing-p19608472.html

Sounds like a wrong or missed clock configuration. Is your "CDM 48 MHz 
Fractional Divider Configuration Register Field Descriptions (0x0210)" setup 
correctly?

Some kernel revisions guesses and fixes the setting, some other not.

Regards,
Juergen

-- 
 Dipl.-Ing. Juergen Beisert | http://www.pengutronix.de
 Pengutronix - Linux Solutions for Science and Industry
   Handelsregister:  Amtsgericht Hildesheim, HRA 2686
          Vertretung Sued/Muenchen, Germany
  Phone: +49-8766-939 228  | Fax: +49-5121-206917-5555

  reply	other threads:[~2008-12-05 17:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-05 10:47 Installation on a MPC5200 based custom board Angelo
2008-12-05 12:20 ` Gary Thomas
2008-12-05 13:00   ` R: " gianfranco.casanova
2008-12-05 17:36     ` Juergen Beisert [this message]
2008-12-05 19:33       ` Jon Smirl
2008-12-05 20:29         ` Angelo

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=200812051836.50960.jbe@pengutronix.de \
    --to=jbe@pengutronix.de \
    --cc=gary@mlbassoc.com \
    --cc=gianfranco.casanova@alice.it \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=s104259@yahoo.it \
    /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