From: Jan Luebbe <jlu@pengutronix.de>
To: Gregory Clement <gregory.clement@free-electrons.com>,
Andrew Lunn <andrew@lunn.ch>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Jason Cooper <jason@lakedaemon.net>
Cc: linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel@pengutronix.de,
Jan Luebbe <jlu@pengutronix.de>
Subject: [PATCH 0/2] fix 4GB DRAM window support on mvebu
Date: Mon, 28 Aug 2017 17:25:15 +0200 [thread overview]
Message-ID: <20170828152517.24506-1-jlu@pengutronix.de> (raw)
The current MBUS DRAM window calculation fails for 4GB windows because it
overflows. This is fixed in the first patch by using u64 instead of u32 to
store the size. The second excplicitly checks that we don't try to configure a
too large memory window in the pci driver.
As they don't depend on each other, they could also go in separatly.
Jan Luebbe (2):
bus: mbus: fix window size calculation for 4GB windows
PCI: mvebu: Check DRAM window size
drivers/bus/mvebu-mbus.c | 2 +-
drivers/pci/host/pci-mvebu.c | 27 ++++++++++++++++++++++-----
include/linux/mbus.h | 4 ++--
3 files changed, 25 insertions(+), 8 deletions(-)
--
2.11.0
next reply other threads:[~2017-08-28 15:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 15:25 Jan Luebbe [this message]
2017-08-28 15:25 ` [PATCH 1/2] bus: mbus: fix window size calculation for 4GB windows Jan Luebbe
2017-09-19 14:43 ` Gregory CLEMENT
2017-09-20 16:37 ` Uwe Kleine-König
2017-08-28 15:25 ` [PATCH 2/2] PCI: mvebu: Check DRAM window size Jan Luebbe
2017-09-25 23:56 ` Bjorn Helgaas
2017-10-05 21:16 ` Bjorn Helgaas
2017-11-06 19:17 ` Bjorn Helgaas
2017-08-28 15:30 ` [RFC] ARM: Orion: " Jan Luebbe
2017-08-28 15:51 ` Andrew Lunn
2017-08-30 20:07 ` [PATCH 0/2] fix 4GB DRAM window support on mvebu Bjorn Helgaas
2017-08-31 8:11 ` 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=20170828152517.24506-1-jlu@pengutronix.de \
--to=jlu@pengutronix.de \
--cc=andrew@lunn.ch \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=thomas.petazzoni@free-electrons.com \
/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;
as well as URLs for NNTP newsgroup(s).