From: "Marek Behún" <kabel@kernel.org>
To: "Pali Rohár" <pali@kernel.org>
Cc: Andrew Lunn <andrew@lunn.ch>,
Gregory Clement <gregory.clement@bootlin.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: marvell: armada-37xx: Remap IO space to bus address 0x0
Date: Sat, 19 Feb 2022 12:34:45 +0100 [thread overview]
Message-ID: <20220219123445.14940a12@thinkpad> (raw)
In-Reply-To: <20220218212526.16021-1-pali@kernel.org>
On Fri, 18 Feb 2022 22:25:26 +0100
Pali Rohár <pali@kernel.org> wrote:
> Remap PCI I/O space to the bus address 0x0 in the Armada 37xx
> device-tree in order to support legacy I/O port based cards which have
> hardcoded I/O ports in low address space.
>
> Some legacy PCI I/O based cards do not support 32-bit I/O addressing.
>
> Since commit 64f160e19e92 ("PCI: aardvark: Configure PCIe resources from
> 'ranges' DT property") this driver can work with I/O windows which have
> a different address for CPU than for PCI bus (unless there is some
> conflict with other A37xx mapping), without needing additional support
> for this in the firmware.
>
> Note that DDR on A37xx is mapped to bus address 0x0 and that mapping of
> I/O space can be set to address 0x0 too because MEM space and I/O space
> are separate and so they do not conflict.
>
> Signed-off-by: Pali Rohár <pali@kernel.org>
> Reported-by: Arnd Bergmann <arnd@arndb.de>
Reviewed-by: Marek Behún <kabel@kernel.org>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: "Marek Behún" <kabel@kernel.org>
To: "Pali Rohár" <pali@kernel.org>
Cc: Andrew Lunn <andrew@lunn.ch>,
Gregory Clement <gregory.clement@bootlin.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: marvell: armada-37xx: Remap IO space to bus address 0x0
Date: Sat, 19 Feb 2022 12:34:45 +0100 [thread overview]
Message-ID: <20220219123445.14940a12@thinkpad> (raw)
In-Reply-To: <20220218212526.16021-1-pali@kernel.org>
On Fri, 18 Feb 2022 22:25:26 +0100
Pali Rohár <pali@kernel.org> wrote:
> Remap PCI I/O space to the bus address 0x0 in the Armada 37xx
> device-tree in order to support legacy I/O port based cards which have
> hardcoded I/O ports in low address space.
>
> Some legacy PCI I/O based cards do not support 32-bit I/O addressing.
>
> Since commit 64f160e19e92 ("PCI: aardvark: Configure PCIe resources from
> 'ranges' DT property") this driver can work with I/O windows which have
> a different address for CPU than for PCI bus (unless there is some
> conflict with other A37xx mapping), without needing additional support
> for this in the firmware.
>
> Note that DDR on A37xx is mapped to bus address 0x0 and that mapping of
> I/O space can be set to address 0x0 too because MEM space and I/O space
> are separate and so they do not conflict.
>
> Signed-off-by: Pali Rohár <pali@kernel.org>
> Reported-by: Arnd Bergmann <arnd@arndb.de>
Reviewed-by: Marek Behún <kabel@kernel.org>
next prev parent reply other threads:[~2022-02-19 11:36 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 21:25 [PATCH] arm64: dts: marvell: armada-37xx: Remap IO space to bus address 0x0 Pali Rohár
2022-02-18 21:25 ` Pali Rohár
2022-02-19 11:34 ` Marek Behún [this message]
2022-02-19 11:34 ` Marek Behún
2022-02-19 21:00 ` Arnd Bergmann
2022-02-19 21:00 ` Arnd Bergmann
2022-02-28 15:41 ` Gregory CLEMENT
2022-02-28 15:41 ` Gregory CLEMENT
2022-02-28 16:42 ` Gregory CLEMENT
2022-02-28 16:42 ` Gregory CLEMENT
2022-03-01 9:25 ` Pali Rohár
2022-03-01 9:25 ` Pali Rohár
2022-03-02 13:06 ` Andrew Lunn
2022-03-02 13:06 ` Andrew Lunn
2022-03-02 13:15 ` Marek Behún
2022-03-02 13:15 ` Marek Behún
2022-03-02 13:25 ` Marek Behún
2022-03-02 13:25 ` Marek Behún
2022-03-02 13:25 ` Pali Rohár
2022-03-02 13:25 ` Pali Rohár
2022-03-04 12:44 ` Pali Rohár
2022-03-04 12:44 ` Pali Rohár
2022-03-04 16:30 ` [PATCH v2] " Pali Rohár
2022-03-04 16:30 ` Pali Rohár
2022-03-08 11:41 ` Pali Rohár
2022-03-08 11:41 ` Pali Rohár
2022-03-10 10:05 ` Gregory CLEMENT
2022-03-10 10:05 ` Gregory CLEMENT
2022-03-10 10:09 ` Pali Rohár
2022-03-10 10:09 ` Pali Rohár
2022-03-10 10:22 ` Arnd Bergmann
2022-03-10 10:22 ` Arnd Bergmann
2022-03-10 10:41 ` Pali Rohár
2022-03-10 10:41 ` Pali Rohár
2022-03-10 10:23 ` Gregory CLEMENT
2022-03-10 10:23 ` Gregory CLEMENT
2022-03-10 10:47 ` Pali Rohár
2022-03-10 10:47 ` Pali Rohár
2022-03-10 10:39 ` [PATCH v3] " Pali Rohár
2022-03-10 10:39 ` Pali Rohár
2022-03-10 11:51 ` Arnd Bergmann
2022-03-10 11:51 ` Arnd Bergmann
2022-03-10 13:51 ` Gregory CLEMENT
2022-03-10 13:51 ` Gregory CLEMENT
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=20220219123445.14940a12@thinkpad \
--to=kabel@kernel.org \
--cc=andrew@lunn.ch \
--cc=gregory.clement@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pali@kernel.org \
/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.