From: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
To: Matthias Brugger <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
Subject: Re: [PATCH v2 2/2] usb: xhci: Load Raspberry Pi 4 VL805's firmware
Date: Tue, 05 May 2020 17:04:04 +0200 [thread overview]
Message-ID: <f28fb56ea214ff95c0a8c1b38cb28cc6390d166e.camel@suse.de> (raw)
In-Reply-To: <0ca001a3-75c3-e3ba-fc63-17c6b4982856@suse.com>
[-- Attachment #1: Type: text/plain, Size: 1897 bytes --]
On Tue, 2020-05-05 at 16:59 +0200, Matthias Brugger wrote:
[...]
> > > > > > +#ifdef CONFIG_BCM2711
> > > > >
> > > > > This won't work with rpi_arm64_defconfig.
> > > > > Can't we just evaluate at runtime if we need to do anything in
> > > > > xhci_pci_fixup.
> > > >
> > > > I can't see why, who is going to call xhci_pci_probe() in RPi3?
> > > >
> > >
> > > If you do make rpi_arm64_defconfig and inspect the .config, you will see
> > > that
> > > CONFIG_BCM2711 is not defined, so this code won't be called on RPi4.
> >
> > Oh! Understood.
> >
> > Well, given that only xhci_pci_probe() is called if we're running on RPi4, I
> > think I can disregard those defines altogether. I'll double-check that.
> >
>
> Yes but from my understanding we only need to call the function on newer
> revisions of RPi4. Does it have any side effect on older revisions, e.g. we
> get
> error messages (see below)?
The firmware quirk supports older rpi4s and simply does nothing. Note that the
downstream Linux implementation runs this on all rpi4s.
> [...]>>>> I wonder if the newer RPi4 have also a newer revision ID (see
> > > > > get_board_rev).
> > > > > If
> > > > > so we could add another bool to struct rpi_model which will indicate
> > > > > us if
> > > > > we
> > > > > need to notify VideoCore about vl805's firmware.
> > > > >
> > > > > > +void xhci_pci_fixup(struct udevice *dev)
> > > > > > +{
> > > > > > + int ret;
> > > > > > +
> > > > > > + ret = bcm2711_notify_vl805_reset();
> > > > > > + if (ret)
> > > > > > + printf("RPI: Failed to notify VideoCore about vl805's
> > > > > > firmware\n");
>
> We already have
> printf("bcm2711: Faild to load vl805's firmware, %d\n", ret); in
> bcm2711_notify_vl805_reset(). Do we really need two error messages?
Agree, it's a little redundant. I'll get rid of it.
Regards,
Nicolas
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-05-05 15:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 13:04 [PATCH v2 0/2] Raspberry Pi 4 VL805 firmware load Nicolas Saenz Julienne
2020-04-30 13:04 ` [PATCH v2 1/2] arm: rpi: Add function to trigger VL805's " Nicolas Saenz Julienne
2020-04-30 13:31 ` Mark Kettenis
2020-04-30 13:33 ` Nicolas Saenz Julienne
2020-04-30 13:04 ` [PATCH v2 2/2] usb: xhci: Load Raspberry Pi 4 VL805's firmware Nicolas Saenz Julienne
2020-05-05 12:15 ` Matthias Brugger
2020-05-05 12:35 ` Peter Robinson
2020-05-05 12:53 ` Nicolas Saenz Julienne
2020-05-05 13:39 ` Matthias Brugger
2020-05-05 13:47 ` Nicolas Saenz Julienne
2020-05-05 14:59 ` Matthias Brugger
2020-05-05 15:04 ` 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=f28fb56ea214ff95c0a8c1b38cb28cc6390d166e.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=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®