public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: socfpga: Fix QSPI doesn't work on socdk board
Date: Wed, 23 Dec 2015 03:27:05 +0100	[thread overview]
Message-ID: <201512230327.05673.marex@denx.de> (raw)
In-Reply-To: <a52e392e-31b5-4aef-b79a-48d9f0c65d06@me.com>

On Wednesday, December 23, 2015 at 03:26:07 AM, ?? ? wrote:
> > From: Marek Vasut
> > Date: 2015-12-23 10:07
> > To: ShengjiangWu
> > CC: u-boot; clsee; dinguyen; dinh.linux; pavel; sr
> > Subject: Re: [PATCH] arm: socfpga: Fix QSPI doesn't work on socdk board
> > 
> > On Wednesday, December 23, 2015 at 03:02:10 AM, ShengjiangWu wrote:
> > > > -----Original Message-----
> > > > From: Marek Vasut [mailto:marex at denx.de]
> > > > Sent: Wednesday, December 23, 2015 9:25 AM
> > > > To: ?? ?
> > > > Cc: u-boot at lists.denx.de; clsee at altera.com;
> > > > dinguyen at opensource.altera.com; dinh.linux at gmail.com; pavel at denx.de;
> > > > sr at denx.de Subject: Re: [PATCH] arm: socfpga: Fix QSPI doesn't work
> > > > on socdk board
> > > > 
> > > > On Wednesday, December 23, 2015 at 02:22:49 AM, ?? ? wrote:
> > > > > On Dec 22, 2015, at 12:33 PM, Marek Vasut <marex@denx.de> wrote:
> > > > > 
> > > > > On Tuesday, December 22, 2015 at 09:19:16 PM, Marek Vasut wrote:
> > > > > 
> > > > > On Tuesday, December 22, 2015 at 10:18:09 AM, shengjiangwu wrote:
> > > > > > Updated pinmux group MIXED1IO[15-20] for QSPI.
> > > > > > Updated QSPI clock.
> > > > > > 
> > > > > > Signed-off-by: shengjiangwu <shengjiangwu@icloud.com>
> > > > > > Cc: Chin Liang See <clsee@altera.com>
> > > > > > Cc: Dinh Nguyen <dinguyen@opensource.altera.com>
> > > > > > Cc: Dinh Nguyen <dinh.linux@gmail.com>
> > > > > > Cc: Pavel Machek <pavel@denx.de>
> > > > > > Cc: Marek Vasut <marex@denx.de>
> > > > > > Cc: Stefan Roese <sr@denx.de>
> > > > > 
> > > > > Applied, thanks.
> > > > > 
> > > > > I will push your patches to [1] in a few hours, can you try and see
> > > > > if the CV SOCDK works fine for you? Thanks
> > > > > 
> > > > > [1] http://git.denx.de/?p=u-boot/u-boot-
> > > > > socfpga.git;a=shortlog;h=refs/heads/master
> > > > > 
> > > > > Pushed. Please let me know how SoCDK works for you now and if there
> > > > > are still some problems.
> > > > > 
> > > > > 
> > > > > Best regards,
> > > > > Marek Vasut
> > > > > 
> > > > > 
> > > > > Hi Marek,
> > > > > 
> > > > > Thank you for your help, I tested the master branch, emac1 and QSPI
> > > > > works. Below is log.
> > > > 
> > > > Good! so we're happy ? Can you give USB a spin too? I think it might
> > > > have some issues and I don't have the necessary cable here.
> > > > 
> > > > [...]
> > > > 
> > > > Best regards,
> > > > Marek Vasut
> > > 
> > > Hi Marek,
> > > 
> > > Yes, emac1 and qspi are working now. I'm afraid USB is not working,
> > > 
> > > => usb reset
> > > resetting USB...
> > > USB0: Core Release: 2.93a
> > > dwc_otg_core_host_init: Timeout!
> > > dwc_otg_core_host_init: Timeout!
> > > dwc_otg_core_host_init: Timeout!
> > > dwc_otg_core_host_init: Timeout!
> > > dwc_otg_core_host_init: Timeout!
> > > dwc_otg_core_host_init: Timeout!
> > > dwc_otg_core_host_init: Timeout!
> > > dwc_otg_core_host_init: Timeout!
> > > dwc_otg_core_host_init: Timeout!
> > > dwc_otg_core_host_init: Timeout!
> > > dwc_otg_core_host_init: Timeout!
> > > dwc_otg_core_host_init: Timeout!
> > > dwc_otg_core_host_init: Timeout!
> > > dwc_otg_core_host_init: Timeout!
> > > dwc_otg_core_host_init: Timeout!
> > > scanning bus 0 for devices... 1 USB Device(s) found
> > > => usb tree
> > > USB device tree:
> > > 1 Hub (480 Mb/s, 0mA)
> > > U-Boot Root Hub
> > 
> > Hm, darn. Can you or Chin check it ? It's either pinmux or wrong USB node
> > in DT in arch/arm/dts/socfpga_cyclone5_socdk.dts .
> 
> Hi Marek,
> 
> Pin mux settings has error, set EMACIO[1-8] [10-13] from 3 to 2, then usb
> works,
> 
> => usb start
> starting USB...
> USB0: Core Release: 2.93a
> scanning bus 0 for devices... 2 USB Device(s) found
> => usb tree
> USB device tree:
> 1 Hub (480 Mb/s, 0mA)
> 
> | U-Boot Root Hub
> 
> +-2 Mass Storage (480 Mb/s, 98mA)
> Generic USB Storage 000000000272

Cool, thanks! Patch please ;-)

  reply	other threads:[~2015-12-23  2:27 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-23  2:26 [U-Boot] [PATCH] arm: socfpga: Fix QSPI doesn't work on socdk board 圣江 吴
2015-12-23  2:27 ` Marek Vasut [this message]
2015-12-23  2:29   ` Chin Liang See
2015-12-23  2:38     ` Chin Liang See
2015-12-23  3:04       ` Marek Vasut
     [not found] <18c117d0-3bdb-4cf8-972a-35711ec3eacf@me.com>
2015-12-23  1:26 ` Marek Vasut
  -- strict thread matches above, loose matches on Subject: below --
2015-12-23  1:22 圣江 吴
2015-12-23  1:24 ` Marek Vasut
2015-12-23  2:02   ` ShengjiangWu
2015-12-23  2:07     ` Marek Vasut
2015-12-23  2:27       ` Chin Liang See
2015-12-22  9:18 shengjiangwu
2015-12-22  9:36 ` Chin Liang See
2015-12-22 20:19 ` Marek Vasut
2015-12-22 20:33   ` Marek Vasut
2015-12-21  7:33 圣江 吴
2015-12-21  9:37 ` Pavel Machek
2015-12-21  9:56   ` Chin Liang See
2015-12-21 10:12     ` Marek Vasut
2015-12-21 10:12   ` Marek Vasut
2015-12-21 10:41     ` Pavel Machek
2015-12-21 14:49       ` Marek Vasut
2015-12-18  7:57 圣江 吴
2015-12-18 12:37 ` Marek Vasut
2015-12-18  7:21 shengjiangwu
2015-12-18  7:44 ` Chin Liang See

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=201512230327.05673.marex@denx.de \
    --to=marex@denx.de \
    --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