From: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
To: Marek Vasut <marex@denx.de>,
mbrugger@suse.com, u-boot@lists.denx.de, bmeng.cn@gmail.com,
linux-kernel@vger.kernel.org
Cc: sjg@chromium.org, m.szyprowski@samsung.com,
s.nawrocki@samsung.com, mark.kettenis@xs4all.nl
Subject: Re: [PATCH v3 0/2] usb: xhci: Load Raspberry Pi 4 VL805's firmware
Date: Mon, 01 Jun 2020 13:09:37 +0200 [thread overview]
Message-ID: <9aea19124817a3d9fa004ec495ea6d1036d2dc8d.camel@suse.de> (raw)
In-Reply-To: <bf73b73e-c251-7ac8-c245-a3b3d2be2420@denx.de>
[-- Attachment #1: Type: text/plain, Size: 1870 bytes --]
On Mon, 2020-06-01 at 12:53 +0200, Marek Vasut wrote:
> On 6/1/20 12:47 PM, Nicolas Saenz Julienne wrote:
> > On Tue, 2020-05-05 at 18:26 +0200, Nicolas Saenz Julienne wrote:
> > > Newer revisions of the RPi4 need their xHCI chip, VL805, firmware to be
> > > loaded explicitly. Earlier versions didn't need that as they where using
> > > an EEPROM for that purpose. This series takes care of setting up the
> > > relevant infrastructure and run the firmware loading routine at the
> > > right moment.
> > >
> > > Note that this builds on top of Sylwester Nawrocki's "USB host support
> > > for Raspberry Pi 4 board" series.
> > >
> > > ---
> >
> > Please don't forget about this series. The new 8GB RPi4 contains this HW
> > design
> > change and USB will not work without it. See this discussion on the
> > downstream
> > kernel github, where other OS/bootloaders are hitting the issue:
> >
> > https://github.com/raspberrypi/firmware/issues/1402
> >
> > Otherwise, the Linux version of this is already in linux-next:
> >
> >
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/usb/host/pci-quirks.c?h=next-20200529&id=c65822fef4adc0ba40c37a47337376ce75f7a7bc
>
> We're already at 2020.07-rc3 , so unless this is a bugfix (does not look
> that way), this will have to wait for next release cycle.
Of course. As long as it eventually gets in I'm happy (not implying this
specific series is flawless, but the overall mechanism). I'm just worried this
gets lost.
> Also, it seems
> there was a lengthy ongoing discussion, is that already sorted out ?
Well, there was some discussion on how to incorporate the platform specific
callback into XCHI's code. Which this revision of the series addresses. But,
IIRC, that's pretty much it as far as discussion is concerned.
Regards,
Nicolas
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-06-01 11:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 16:26 Nicolas Saenz Julienne
2020-05-05 16:26 ` [PATCH v3 1/2] arm: rpi: Add function to trigger VL805's firmware load Nicolas Saenz Julienne
2020-05-06 5:33 ` Bin Meng
2020-05-06 8:31 ` Nicolas Saenz Julienne
2020-05-05 16:26 ` [PATCH v3 2/2] usb: xhci: Load Raspberry Pi 4 VL805's firmware Nicolas Saenz Julienne
2020-05-13 12:56 ` [PATCH v3 0/2] " Nicolas Saenz Julienne
2020-06-01 10:47 ` Nicolas Saenz Julienne
2020-06-01 10:53 ` Marek Vasut
2020-06-01 11:09 ` Nicolas Saenz Julienne [this message]
2020-06-01 11:12 ` Marek Vasut
2020-06-01 14:41 ` Nicolas Saenz Julienne
2020-06-01 15:27 ` Marek Vasut
2020-06-04 11:18 ` Nicolas Saenz Julienne
2020-06-04 11:52 ` Marek Vasut
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=9aea19124817a3d9fa004ec495ea6d1036d2dc8d.camel@suse.de \
--to=nsaenzjulienne@suse.de \
--cc=bmeng.cn@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=marex@denx.de \
--cc=mark.kettenis@xs4all.nl \
--cc=mbrugger@suse.com \
--cc=s.nawrocki@samsung.com \
--cc=sjg@chromium.org \
--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
all inboxes | Powered by JetHome®