From: Marek Vasut <marek.vasut@gmail.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Robin Murphy <robin.murphy@arm.com>,
linux-ide@vger.kernel.org, linux-nvme@lists.infradead.org,
Marek Vasut <marek.vasut+renesas@gmail.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Jens Axboe <axboe@fb.com>, Jens Axboe <axboe@kernel.dk>,
Keith Busch <keith.busch@intel.com>,
Sagi Grimberg <sagi@grimberg.me>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH 1/2] [RFC] ata: ahci: Respect bus DMA constraints
Date: Sat, 9 Mar 2019 00:23:15 +0100 [thread overview]
Message-ID: <a6b34982-9100-0e60-c3eb-6ed8fcbe9e93@gmail.com> (raw)
In-Reply-To: <20190308071810.GA11959@lst.de>
On 3/8/19 8:18 AM, Christoph Hellwig wrote:
> On Thu, Mar 07, 2019 at 12:14:06PM +0100, Marek Vasut wrote:
>>> Right, but whoever *interprets* the device masks after the driver has
>>> overridden them should be taking the (smaller) bus mask into account as
>>> well, so the question is where is *that* not being done correctly?
>>
>> Do you have a hint where I should look for that ?
>
> If this a 32-bit ARM platform it might the complete lack of support
> for bus_dma_mask in arch/arm/mm/dma-mapping.c..
It's an ARM 64bit platform, just the PCIe controller is limited to 32bit
address range, so the devices on the PCIe bus cannot read the host's
DRAM above the 32bit limit.
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2019-03-08 23:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-07 0:04 [PATCH 1/2] [RFC] ata: ahci: Respect bus DMA constraints marek.vasut
2019-03-07 0:04 ` [PATCH 2/2] [RFC] nvme-pci: " marek.vasut
2019-03-07 9:32 ` [PATCH 1/2] [RFC] ata: ahci: " Robin Murphy
2019-03-07 9:37 ` Marek Vasut
2019-03-07 9:48 ` Robin Murphy
2019-03-07 11:14 ` Marek Vasut
2019-03-08 7:18 ` Christoph Hellwig
2019-03-08 23:23 ` Marek Vasut [this message]
2019-03-13 18:30 ` Christoph Hellwig
2019-03-16 21:25 ` Marek Vasut
2019-03-16 23:04 ` Marek Vasut
2019-03-17 10:29 ` Geert Uytterhoeven
2019-03-17 23:36 ` Marek Vasut
2019-03-18 13:14 ` Robin Murphy
2019-03-18 23:25 ` Marek Vasut
2019-03-28 3:25 ` Marek Vasut
2019-04-09 12:16 ` Marek Vasut
2019-03-17 10:24 ` Geert Uytterhoeven
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=a6b34982-9100-0e60-c3eb-6ed8fcbe9e93@gmail.com \
--to=marek.vasut@gmail.com \
--cc=axboe@fb.com \
--cc=axboe@kernel.dk \
--cc=geert+renesas@glider.be \
--cc=hch@lst.de \
--cc=keith.busch@intel.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=marek.vasut+renesas@gmail.com \
--cc=robin.murphy@arm.com \
--cc=sagi@grimberg.me \
--cc=wsa+renesas@sang-engineering.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