From: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
linux-kernel@vger.kernel.org,
Mathias Nyman <mathias.nyman@intel.com>
Cc: linux-usb@vger.kernel.org, linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
bcm-kernel-feedback-list@broadcom.com, f.fainelli@gmail.com,
gregkh@linuxfoundation.org, tim.gover@raspberrypi.org,
linux-pci@vger.kernel.org, wahrenst@gmx.net
Subject: Re: [PATCH v4 4/4] USB: pci-quirks: Add Raspberry Pi 4 quirk
Date: Mon, 09 Mar 2020 12:09:26 +0100 [thread overview]
Message-ID: <72e22c655f885bf37475b4fea3a1cc4866d05a39.camel@suse.de> (raw)
In-Reply-To: <b4fb58f0-6d51-657b-bcf6-5f4b0c798312@cogentembedded.com>
[-- Attachment #1: Type: text/plain, Size: 2628 bytes --]
On Sat, 2020-03-07 at 12:54 +0300, Sergei Shtylyov wrote:
> Hello!
>
> On 06.03.2020 14:43, Nicolas Saenz Julienne wrote:
>
> > On the Raspberry Pi 4, after a PCI reset, VL805's firmware may either be
> > loaded directly from an EEPROM or, if not present, by the SoC's
> > VideCore. Inform VideCore that VL805 was just reset.
> >
> > Also, as this creates a dependency between XHCI_PCI and VideoCore's
> > firmware interface, reflect that on the firmware interface Kconfg.
> >
> > Signed-off-by: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
> > ---
> >
> > Changes since v3:
> > - Add more complete error message.
> > - Add braces around if statement
> >
> > Changes since v1:
> > - Make RASPBERRYPI_FIRMWARE dependent on this quirk to make sure it
> > gets compiled when needed.
> >
> > drivers/firmware/Kconfig | 1 +
> > drivers/usb/host/pci-quirks.c | 16 ++++++++++++++++
> > 2 files changed, 17 insertions(+)
> [...]
> > diff --git a/drivers/usb/host/pci-quirks.c b/drivers/usb/host/pci-quirks.c
> > index beb2efa71341..452f5f12b042 100644
> > --- a/drivers/usb/host/pci-quirks.c
> > +++ b/drivers/usb/host/pci-quirks.c
> > @@ -16,6 +16,9 @@
> > #include <linux/export.h>
> > #include <linux/acpi.h>
> > #include <linux/dmi.h>
> > +
> > +#include <soc/bcm2835/raspberrypi-firmware.h>
> > +
> > #include "pci-quirks.h"
> > #include "xhci-ext-caps.h"
> >
> > @@ -1243,11 +1246,24 @@ static void quirk_usb_handoff_xhci(struct pci_dev
> > *pdev)
> >
> > static void quirk_usb_early_handoff(struct pci_dev *pdev)
> > {
> > + int ret;
> > +
> > /* Skip Netlogic mips SoC's internal PCI USB controller.
> > * This device does not need/support EHCI/OHCI handoff
> > */
> > if (pdev->vendor == 0x184e) /* vendor Netlogic */
> > return;
> > +
> > + if (pdev->vendor == PCI_VENDOR_ID_VIA && pdev->device == 0x3483) {
> > + ret = rpi_firmware_init_vl805(pdev);
> > + if (ret) {
> > + /* Firmware might be outdated, or something failed */
> > + dev_warn(&pdev->dev, "Failed to load VL805's firmware:
> > %d\n", ret);
> > + dev_warn(&pdev->dev, "Will continue to attempt to work,
> > "
> > + "but bad things might happen. You should fix
> > this...\n");
>
> Don't break up the long kernel messages (checkpatch.pl should not
> complain
> about them).
I generally don't, but in this specific case IMO it went way too long, as in
140 charaters long, so I figured it'd be better to split it. That said, I don't
really care, so I'll happily change it for v5.
Regards,
Nicolas
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-03-09 11:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 11:43 [PATCH v4 0/4] " Nicolas Saenz Julienne
2020-03-06 11:43 ` [PATCH v4 1/4] soc: bcm2835: Sync xHCI reset firmware property with downstream Nicolas Saenz Julienne
2020-03-06 11:43 ` [PATCH v4 2/4] firmware: raspberrypi: Introduce vl805 init routine Nicolas Saenz Julienne
2020-03-06 11:43 ` [PATCH v4 3/4] PCI: brcmstb: Wait for Raspberry Pi's firmware when present Nicolas Saenz Julienne
2020-03-07 9:55 ` Sergei Shtylyov
2020-03-09 10:55 ` Nicolas Saenz Julienne
2020-03-06 11:43 ` [PATCH v4 4/4] USB: pci-quirks: Add Raspberry Pi 4 quirk Nicolas Saenz Julienne
2020-03-07 9:54 ` Sergei Shtylyov
2020-03-09 11:09 ` 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=72e22c655f885bf37475b4fea3a1cc4866d05a39.camel@suse.de \
--to=nsaenzjulienne@suse.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=tim.gover@raspberrypi.org \
--cc=wahrenst@gmx.net \
/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®