From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
Cc: linux-pci <linux-pci@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-rpi-kernel <linux-rpi-kernel@lists.infradead.org>,
devicetree <devicetree@vger.kernel.org>,
Rob Herring <robh@kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Bjorn Helgaas <helgaas@kernel.org>,
Robin Murphy <robin.murphy@arm.con>,
bcm-kernel-feedback-list <bcm-kernel-feedback-list@broadcom.com>
Subject: Re: RPi4 can't deal with 64 bit PCI accesses
Date: Mon, 22 Feb 2021 17:55:49 +0000 [thread overview]
Message-ID: <20210222175549.GO1463@shell.armlinux.org.uk> (raw)
In-Reply-To: <c188698ca0de3ed6c56a0cf7880e1578aa753077.camel@suse.de>
On Mon, Feb 22, 2021 at 04:47:22PM +0100, Nicolas Saenz Julienne wrote:
> [2] Things might get even weirder as the order in which the 32bit operations
> are performed might matter (low/high vs high/low).
Note that arm32 does not provide writeq() very purposely because it
is device specific whether writing high-then-low or low-then-high is
the correct approach. See linux/io-64-nonatomic-*.h
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
WARNING: multiple messages have this Message-ID (diff)
From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
Cc: Rob Herring <robh@kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>,
devicetree <devicetree@vger.kernel.org>,
linux-pci <linux-pci@vger.kernel.org>,
Bjorn Helgaas <helgaas@kernel.org>,
linux-rpi-kernel <linux-rpi-kernel@lists.infradead.org>,
bcm-kernel-feedback-list <bcm-kernel-feedback-list@broadcom.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Robin Murphy <robin.murphy@arm.con>
Subject: Re: RPi4 can't deal with 64 bit PCI accesses
Date: Mon, 22 Feb 2021 17:55:49 +0000 [thread overview]
Message-ID: <20210222175549.GO1463@shell.armlinux.org.uk> (raw)
In-Reply-To: <c188698ca0de3ed6c56a0cf7880e1578aa753077.camel@suse.de>
On Mon, Feb 22, 2021 at 04:47:22PM +0100, Nicolas Saenz Julienne wrote:
> [2] Things might get even weirder as the order in which the 32bit operations
> are performed might matter (low/high vs high/low).
Note that arm32 does not provide writeq() very purposely because it
is device specific whether writing high-then-low or low-then-high is
the correct approach. See linux/io-64-nonatomic-*.h
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-02-22 17:57 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 15:47 RPi4 can't deal with 64 bit PCI accesses Nicolas Saenz Julienne
2021-02-22 15:47 ` Nicolas Saenz Julienne
2021-02-22 16:18 ` Ard Biesheuvel
2021-02-22 16:18 ` Ard Biesheuvel
2021-02-22 16:36 ` Nicolas Saenz Julienne
2021-02-22 16:36 ` Nicolas Saenz Julienne
2021-02-22 16:56 ` Robin Murphy
2021-02-22 16:56 ` Robin Murphy
2021-02-24 16:55 ` Florian Fainelli
2021-02-24 16:55 ` Florian Fainelli
2021-02-24 20:25 ` Christoph Hellwig
2021-02-24 20:25 ` Christoph Hellwig
2021-02-24 20:35 ` Florian Fainelli
2021-02-24 20:35 ` Florian Fainelli
2021-02-25 10:29 ` Neil Armstrong
2021-02-25 10:29 ` Neil Armstrong
2021-02-25 11:10 ` Robin Murphy
2021-02-25 11:10 ` Robin Murphy
2021-02-25 11:35 ` Nicolas Saenz Julienne
2021-02-25 11:35 ` Nicolas Saenz Julienne
2021-02-26 5:32 ` Christoph Hellwig
2021-02-26 5:32 ` Christoph Hellwig
2021-02-25 10:41 ` David Woodhouse
2021-02-25 10:41 ` David Woodhouse
2021-02-22 17:55 ` Russell King - ARM Linux admin [this message]
2021-02-22 17:55 ` Russell King - ARM Linux admin
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=20210222175549.GO1463@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=helgaas@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=nsaenzjulienne@suse.de \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.con \
/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.