Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH 1/2] [RFC] ata: ahci: Respect bus DMA constraints
Date: Fri, 8 Mar 2019 08:18:10 +0100	[thread overview]
Message-ID: <20190308071810.GA11959@lst.de> (raw)
In-Reply-To: <a8b5b75f-2660-e216-033a-77808e2afb76@gmail.com>

On Thu, Mar 07, 2019@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..

  reply	other threads:[~2019-03-08  7:18 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 [this message]
2019-03-08 23:23           ` Marek Vasut
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=20190308071810.GA11959@lst.de \
    --to=hch@lst.de \
    /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