From: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
To: mbrugger@suse.com, u-boot@lists.denx.de, bmeng.cn@gmail.com,
marex@denx.de, 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: Wed, 13 May 2020 14:56:27 +0200 [thread overview]
Message-ID: <87d71fa371739486a19f17a6b3ca72d2315220d2.camel@suse.de> (raw)
In-Reply-To: <20200505162607.334-1-nsaenzjulienne@suse.de>
[-- Attachment #1: Type: text/plain, Size: 644 bytes --]
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.
>
> ---
Just for the record, here's the version of this in the Linux Kernel:
https://patchwork.kernel.org/cover/11529585/
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-05-13 12:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 16:26 [PATCH v3 0/2] usb: xhci: Load Raspberry Pi 4 VL805's firmware 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 ` Nicolas Saenz Julienne [this message]
2020-06-01 10:47 ` [PATCH v3 0/2] " Nicolas Saenz Julienne
2020-06-01 10:53 ` Marek Vasut
2020-06-01 11:09 ` Nicolas Saenz Julienne
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=87d71fa371739486a19f17a6b3ca72d2315220d2.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;
as well as URLs for NNTP newsgroup(s).