From: Stefan Agner <stefan@agner.ch>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: u-boot@lists.denx.de, Matthias Brugger <mbrugger@suse.com>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
Jaehoon Chung <jh80.chung@samsung.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Subject: Re: [PATCH] ARM: bcm283x: change the virtual address of the XHCI PCI device base
Date: Fri, 03 Sep 2021 16:23:00 +0200 [thread overview]
Message-ID: <86ccace661f55061a4e3562ee2120ed8@agner.ch> (raw)
In-Reply-To: <20210617092203.19825-1-m.szyprowski@samsung.com>
On 2021-06-17 11:22, Marek Szyprowski wrote:
> Move the XHCI PCI device base up in the virtual address space. This fixes
> initialization failure observed with newer Raspberry Pi firmware, later
> than 63b1922311 ("firmware: arm_loader: Update armstubs with those from
> PR 117). It looks that chosing 0xff800000 as the XHCI PCI device base
> conflicts with the updated ARM/VideoCore firmware.
>
> This also requires to reduce the size of the mapped PCI device region
> from 8MiB to 4MiB to fit into 32bit address space. This is still enough
> for the XHCI PCI device.
>
> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
> ---
> This fixes the issue observed on ARM 32bit after upgrading the RPi4
> firmware files, described some time ago here:
> https://lists.denx.de/pipermail/u-boot/2021-February/442317.html
This also fixes an issue we are seeing in Home Assistant:
https://github.com/home-assistant/operating-system/issues/1490
It does seem that it depends on the binary size (since USB enumeration
worked with 2021.04 at one point, but after enabling more configurations
it caused issues).
So:
Tested-by: Stefan Agner <stefan@agner.ch>
I've seen that this did not make it into master yet, which tree is this
expected to get merged through?
--
Stefan
> ---
> arch/arm/mach-bcm283x/init.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/mach-bcm283x/init.c b/arch/arm/mach-bcm283x/init.c
> index 49027ce0a2..9803499985 100644
> --- a/arch/arm/mach-bcm283x/init.c
> +++ b/arch/arm/mach-bcm283x/init.c
> @@ -14,7 +14,7 @@
> #include <asm/global_data.h>
>
> #define BCM2711_RPI4_PCIE_XHCI_MMIO_PHYS 0x600000000UL
> -#define BCM2711_RPI4_PCIE_XHCI_MMIO_SIZE 0x800000UL
> +#define BCM2711_RPI4_PCIE_XHCI_MMIO_SIZE 0x400000UL
>
> #ifdef CONFIG_ARM64
> #include <asm/armv8/mmu.h>
> @@ -148,7 +148,7 @@ int mach_cpu_init(void)
>
> #ifdef CONFIG_ARMV7_LPAE
> #ifdef CONFIG_TARGET_RPI_4_32B
> -#define BCM2711_RPI4_PCIE_XHCI_MMIO_VIRT 0xff800000UL
> +#define BCM2711_RPI4_PCIE_XHCI_MMIO_VIRT 0xffc00000UL
> #include <addr_map.h>
> #include <asm/system.h>
next prev parent reply other threads:[~2021-09-03 14:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210617092207eucas1p2fba39144e5d4890a23ba70f794a25b79@eucas1p2.samsung.com>
2021-06-17 9:22 ` [PATCH] ARM: bcm283x: change the virtual address of the XHCI PCI device base Marek Szyprowski
2021-06-17 21:44 ` Jaehoon Chung
2021-06-18 9:00 ` nicolas saenz julienne
2021-09-03 14:23 ` Stefan Agner [this message]
2021-09-15 11:22 ` Matthias Brugger
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=86ccace661f55061a4e3562ee2120ed8@agner.ch \
--to=stefan@agner.ch \
--cc=b.zolnierkie@samsung.com \
--cc=jh80.chung@samsung.com \
--cc=m.szyprowski@samsung.com \
--cc=mbrugger@suse.com \
--cc=nsaenzjulienne@suse.de \
--cc=s.nawrocki@samsung.com \
--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