From: Vinod Koul <vkoul@kernel.org>
To: Christian Lamparter <chunkeey@gmail.com>
Cc: John Stultz <john.stultz@linaro.org>,
Mathias Nyman <mathias.nyman@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-arm-msm@vger.kernel.org,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
USB list <linux-usb@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v6 0/5] usb: xhci: Add support for Renesas USB controllers
Date: Sat, 25 Jan 2020 11:02:37 +0530 [thread overview]
Message-ID: <20200125053237.GG2841@vkoul-mobl> (raw)
In-Reply-To: <5878067.luYmtVZgP3@debian64>
On 24-01-20, 22:38, Christian Lamparter wrote:
> On Tuesday, 21 January 2020 21:26:34 CET Christian Lamparter wrote:
> > Hello,
> >
> > On Tue, Jan 21, 2020 at 7:46 AM Vinod Koul <vkoul@kernel.org> wrote:
> > >
> > > hey Christian,
> > >
> > > On 13-01-20, 21:33, Christian Lamparter wrote:
> > > > On Mon, Jan 13, 2020 at 9:10 PM John Stultz <john.stultz@linaro.org> wrote:
> > > > >
> > > > > On Mon, Jan 13, 2020 at 12:42 AM Vinod Koul <vkoul@kernel.org> wrote:
> > > > > >
> > > > > > This series add support for Renesas USB controllers uPD720201 and uPD720202.
> > > > > > These require firmware to be loaded and in case devices have ROM those can
> > > > > > also be programmed if empty. If ROM is programmed, it runs from ROM as well.
> > > > > >
> > > > > > This includes two patches from Christian which supported these controllers
> > > > > > w/o ROM and later my patches for ROM support and multiple firmware versions,
> > > > > > debugfs hook for rom erase and export of xhci-pci functions.
> > > > > >
> > > > >
> > > > > Thanks so much for updating these! They are working ok for me in my
> > > > > testing on db845c.
> > > > >
> > > > > Tested-by: John Stultz <john.stultz@linaro.org>
> > > >
> > > > Nice! I'll definitely give this series another try on my WNDR4700 too
> > > > (PowerPC Arch)
> > > > this weekend.
> > > >
> > > > and from me: Thanks!
> > >
> > > Did you get around to test these?
> >
> > Not yet, I was too optimistic that I could get current linux-usb with the
> > patches running on the WNDR4700 (due to APM82181) over the
> > weekend. Do you think that It still counts, if I'm going with 5.4.11 on
> > OpenWrt instead? Because then I just swap out the old patches from
> > my OpenWrt APM821XX branch:
> > <https://git.openwrt.org/?p=openwrt/staging/chunkeey.git;a=commit;h=4dd6f62a36a3724f0363d639cd9e29e04d7b62c0>
> >
> > and don't have to figure out what broke with linux-usb on the APM821xx.
>
> I could get 5.4.11 to boot on the Netgear WNDR4700 :-).
> (This has a APM82181 SoC (PowerPC 464))
>
> Here's faillog from the "plain xhci-pci" driver:
>
> [ 375.481868] xhci_hcd 0000:45:00.0: xHCI Host Controller
> [ 375.487149] xhci_hcd 0000:45:00.0: new USB bus registered, assigned bus number 1
> [ 385.494590] xhci_hcd 0000:45:00.0: can't setup: -110
> [ 385.499558] xhci_hcd 0000:45:00.0: USB bus 1 deregistered
> [ 385.504963] xhci_hcd 0000:45:00.0: init 0000:45:00.0 fail, -110
> [ 385.510889] xhci_hcd: probe of 0000:45:00.0 failed with error -110
>
> (Notice how it gets stuck for 10 seconds there).
>
> And this is the successlog from the xhci-pci-renesas module
>
> [ 391.555559] renesas xhci 0000:45:00.0: xHCI Host Controller
> [ 391.561171] renesas xhci 0000:45:00.0: new USB bus registered, assigned bus number 1
> [ 391.575068] renesas xhci 0000:45:00.0: hcc params 0x014051cf hci version 0x100 quirks 0x0000000101000090
> [ 391.586750] hub 1-0:1.0: USB hub found
> [ 391.592601] hub 1-0:1.0: 2 ports detected
> [ 391.597199] renesas xhci 0000:45:00.0: xHCI Host Controller
> [ 391.602797] renesas xhci 0000:45:00.0: new USB bus registered, assigned bus number 2
> [ 391.610537] renesas xhci 0000:45:00.0: Host supports USB 3.0 SuperSpeed
> [ 391.617719] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
> [ 391.626495] hub 2-0:1.0: USB hub found
> [ 391.630570] hub 2-0:1.0: 2 ports detected
>
> this is when I added the usb 3.0-stick:
>
> [ 775.403928] usb 2-2: new SuperSpeed Gen 1 USB device number 3 using renesas xhci
> [ 775.432684] usb-storage 2-2:1.0: USB Mass Storage device detected
> [ 775.439238] scsi host1: usb-storage 2-2:1.0
> [ 776.482556] scsi 1:0:0:0: Direct-Access SanDisk Ultra 1.00 PQ: 0 ANSI: 6
> [ 776.492181] sd 1:0:0:0: [sda] 60063744 512-byte logical blocks: (30.8 GB/28.6 GiB)
> [ 776.501193] sd 1:0:0:0: [sda] Write Protect is off
> [ 776.507047] sd 1:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
> [ 776.524893] sda: sda1 sda2
> [ 776.531062] sd 1:0:0:0: [sda] Attached SCSI removable disk
>
> root@(none):/dev# hdparm -t /dev/sda
>
> /dev/sda:
> Timing buffered disk reads: 466 MB in 3.01 seconds = 154.98 MB/sec
>
> and this is the log from my usb 2.0-memorystick:
>
> [ 1187.113650] usb 2-2: USB disconnect, device number 3
> [ 1195.867397] usb 1-2: new high-speed USB device number 2 using renesas xhci
> [ 1195.895171] usb-storage 1-2:1.0: USB Mass Storage device detected
> [ 1195.901848] scsi host1: usb-storage 1-2:1.0
> [ 1196.962583] scsi 1:0:0:0: Direct-Access SanDisk Cruzer Blade 1.00 PQ: 0 ANSI: 6
> [ 1196.978772] sd 1:0:0:0: [sda] 30031872 512-byte logical blocks: (15.4 GB/14.3 GiB)
> [ 1196.988529] sd 1:0:0:0: [sda] Write Protect is off
> [ 1196.994498] sd 1:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
> [ 1197.020407] sda: sda1
> [ 1197.030458] sd 1:0:0:0: [sda] Attached SCSI removable disk
>
> root@(none):/dev# hdparm -t /dev/sda
>
> /dev/sda:
> Timing buffered disk reads: 64 MB in 3.01 seconds = 21.28 MB/sec
>
> These speeds for usb3 and usb2 are within what the device can do.
> So, everything is working fine with the v6.
>
> Tested-by: Christian Lamparter <chunkeey@gmail.com>
Thanks a lot Christian for again testing this.
Mathias, any comments on this series..?
--
~Vinod
next prev parent reply other threads:[~2020-01-25 5:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 8:40 [PATCH v6 0/5] usb: xhci: Add support for Renesas USB controllers Vinod Koul
2020-01-13 8:40 ` [PATCH v6 1/5] usb: xhci: export few functions Vinod Koul
2020-01-13 8:40 ` [PATCH v6 2/5] usb: renesas-xhci: Add the renesas xhci driver Vinod Koul
2020-01-13 8:40 ` [PATCH v6 3/5] usb: renesas-xhci: Add ROM loader for uPD720201 Vinod Koul
2020-01-13 8:40 ` [PATCH v6 4/5] usb: renesas-xhci: allow multiple firmware versions Vinod Koul
2020-01-13 8:40 ` [PATCH v6 5/5] usb: xhci: provide a debugfs hook for erasing rom Vinod Koul
2020-01-13 20:09 ` [PATCH v6 0/5] usb: xhci: Add support for Renesas USB controllers John Stultz
2020-01-13 20:33 ` Christian Lamparter
2020-01-21 6:46 ` Vinod Koul
2020-01-21 20:26 ` Christian Lamparter
2020-01-24 21:38 ` Christian Lamparter
2020-01-25 5:32 ` Vinod Koul [this message]
2020-01-30 17:07 ` Mathias Nyman
2020-01-31 8:40 ` Vinod Koul
2020-02-04 16:33 ` Mathias Nyman
2020-03-12 6:56 ` Vinod Koul
2020-01-31 15:47 ` Alan Stern
2020-03-10 11:55 ` Vinod Koul
2020-01-26 0:11 ` Andreas Böhler
2020-01-26 13:07 ` Christian Lamparter
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=20200125053237.GG2841@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=chunkeey@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=john.stultz@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=yoshihiro.shimoda.uh@renesas.com \
/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;
as well as URLs for NNTP newsgroup(s).