All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
To: u-boot@lists.denx.de
Subject: [PATCH 2/2] usb: xhci: Load Raspberry Pi 4 VL805's firmware
Date: Wed, 29 Apr 2020 12:53:21 +0200	[thread overview]
Message-ID: <4473862791f8a38a472e7642e31184405cfed96a.camel@suse.de> (raw)
In-Reply-To: <CAEUhbmVjWEm=sEkZH_21KcTvNc62=-JuX2gq3cYH3+WyUtWqTw@mail.gmail.com>

Hi Bin,

On Wed, 2020-04-29 at 14:51 +0800, Bin Meng wrote:
> Hi Nicolas,
> 
> On Wed, Apr 29, 2020 at 1:45 AM Nicolas Saenz Julienne
> <nsaenzjulienne@suse.de> wrote:
> > When needed, RPi4's co-processor (called VideoCore) has to be instructed
> > to load VL805's firmware (the chip providing xHCI support). VideCore's
> > firmware expects the board's PCIe bus to be already configured in order
> > for it to load the xHCI chip firmware. So we have to make sure this
> > happens in between the PCIe configuration and xHCI startup.
> > 
> 
> I am a little bit confused. I thought we already solved the xHCI
> driver issuw on RPi4. What's this firmware used for?

This is not related to the issues Sylwester fixed. It builds on it (I should
have been more explicit in that regard). It relates to a design change the RPi
foundation did on newer revisions of boards. VL805, the xHCI chip, needs its
firmware loaded. On older revisions of the board -- the one most people have
right now -- this is achieved using an EEPROM that is rooted directly into
VL805. Newer board revisions removed the EEPROM and now let VideoCore (the
board co-processor) take care of loading the firmware into the VL805 chip.

All we have left from arm's perspective is a mailbox interface to VideoCore,
where we can trigger the VL805 firmware load. Which can only happen as long as
we've have properly configured the PCI bus.

Regards,
Nicolas

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200429/f6282a23/attachment.sig>

      reply	other threads:[~2020-04-29 10:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-28 17:44 [PATCH 0/2] Raspberry Pi 4 VL805 firmware load Nicolas Saenz Julienne
2020-04-28 17:44 ` [PATCH 1/2] arm: rpi: Add function to trigger VL805's " Nicolas Saenz Julienne
2020-04-28 17:44 ` [PATCH 2/2] usb: xhci: Load Raspberry Pi 4 VL805's firmware Nicolas Saenz Julienne
2020-04-28 17:59   ` Marek Vasut
2020-04-29 10:10     ` Nicolas Saenz Julienne
2020-04-29 12:05       ` Marek Vasut
2020-04-29 12:36         ` Nicolas Saenz Julienne
2020-04-29 12:37           ` Marek Vasut
2020-04-29 13:04             ` Nicolas Saenz Julienne
2020-04-29  6:18   ` Marek Szyprowski
2020-04-29 11:19     ` Nicolas Saenz Julienne
2020-04-29  6:51   ` Bin Meng
2020-04-29 10:53     ` Nicolas Saenz Julienne [this message]

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=4473862791f8a38a472e7642e31184405cfed96a.camel@suse.de \
    --to=nsaenzjulienne@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.