From: "Pali Rohár" <pali@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "Gregory CLEMENT" <gregory.clement@bootlin.com>,
"Andrew Lunn" <andrew@lunn.ch>, "Marek Behún" <kabel@kernel.org>,
"Linux ARM" <linux-arm-kernel@lists.infradead.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] arm64: dts: marvell: armada-37xx: Remap IO space to bus address 0x0
Date: Thu, 10 Mar 2022 11:41:35 +0100 [thread overview]
Message-ID: <20220310104135.licbldjs2dvy2nm4@pali> (raw)
In-Reply-To: <CAK8P3a2Q5fVUMKHz=co0_D5suLBk0rCyGKz3g854fv-HS=G3Sw@mail.gmail.com>
On Thursday 10 March 2022 11:22:38 Arnd Bergmann wrote:
> On Thu, Mar 10, 2022 at 11:09 AM Pali Rohár <pali@kernel.org> wrote:
> > On Thursday 10 March 2022 11:05:00 Gregory CLEMENT wrote:
>
> > >
> > > This patch has been refused by Arnd so I removed it from the mvebu/fixes
> > > branch so you should not apply anything on top of it.
> >
> > Ok, so what is wrong with a change which increase size of IO space to 1 MB?
>
> It should not cause any harm, but there is really no point in this if no known
> devices use more than a few bytes, and Linux only maps the first 64KB of
> the I/O space for each host bridge. I don't actually see where we limit the
> size to 64KB, so maybe that changed recently.
>
> Arnd
Ok. Anyway, I was told that DTS should describe HW properties and not to
be bound with SW implementation or SW limitations, like case here if
Linux SW limits some sizes.
next prev parent reply other threads:[~2022-03-10 10:41 UTC|newest]
Thread overview: 22+ 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-19 11:34 ` Marek Behún
2022-02-19 21:00 ` Arnd Bergmann
2022-02-28 15:41 ` Gregory CLEMENT
2022-02-28 16:42 ` Gregory CLEMENT
2022-03-01 9:25 ` Pali Rohár
2022-03-02 13:06 ` Andrew Lunn
2022-03-02 13:15 ` Marek Behún
2022-03-02 13:25 ` Marek Behún
2022-03-02 13:25 ` Pali Rohár
2022-03-04 12:44 ` Pali Rohár
2022-03-04 16:30 ` [PATCH v2] " Pali Rohár
2022-03-08 11:41 ` Pali Rohár
2022-03-10 10:05 ` Gregory CLEMENT
2022-03-10 10:09 ` Pali Rohár
2022-03-10 10:22 ` Arnd Bergmann
2022-03-10 10:41 ` Pali Rohár [this message]
2022-03-10 10:23 ` Gregory CLEMENT
2022-03-10 10:47 ` Pali Rohár
2022-03-10 10:39 ` [PATCH v3] " Pali Rohár
2022-03-10 11:51 ` Arnd Bergmann
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=20220310104135.licbldjs2dvy2nm4@pali \
--to=pali@kernel.org \
--cc=andrew@lunn.ch \
--cc=arnd@arndb.de \
--cc=gregory.clement@bootlin.com \
--cc=kabel@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox