All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Wesley Terpstra <wesley@sifive.com>
Cc: Christoph Hellwig <hch@lst.de>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Arnd Bergmann <arnd@arndb.de>,
	linux-pci@vger.kernel.org, linux-riscv@lists.infradead.org
Subject: Re: add support for Xilinx PCIe root ports on RISC-V v2
Date: Thu, 2 Aug 2018 09:14:14 +0200	[thread overview]
Message-ID: <20180802071414.GA11584@lst.de> (raw)
In-Reply-To: <CAMgXwThU2h3Grm+10S0Env1ZUYK5Q7pze+ckADjjyHEUVGs7=A@mail.gmail.com>

On Wed, Aug 01, 2018 at 04:02:34PM -0700, Wesley Terpstra wrote:
> FYI, I don't believe this solution is the one we intended to merge
> upstream. There is a different approach used in the riscv-linux tree
> from Palmer.

This is the solution I as the dma-mapping maintainer want for upstream,
and I'm trying to convince the PCI maintainers to agree with me.

What is in the RISC-V trees is a horribly bad idea that should have
never seen the light of day (copying dma_map_ops and patching them up).

WARNING: multiple messages have this Message-ID (diff)
From: hch@lst.de (Christoph Hellwig)
To: linux-riscv@lists.infradead.org
Subject: add support for Xilinx PCIe root ports on RISC-V v2
Date: Thu, 2 Aug 2018 09:14:14 +0200	[thread overview]
Message-ID: <20180802071414.GA11584@lst.de> (raw)
In-Reply-To: <CAMgXwThU2h3Grm+10S0Env1ZUYK5Q7pze+ckADjjyHEUVGs7=A@mail.gmail.com>

On Wed, Aug 01, 2018 at 04:02:34PM -0700, Wesley Terpstra wrote:
> FYI, I don't believe this solution is the one we intended to merge
> upstream. There is a different approach used in the riscv-linux tree
> from Palmer.

This is the solution I as the dma-mapping maintainer want for upstream,
and I'm trying to convince the PCI maintainers to agree with me.

What is in the RISC-V trees is a horribly bad idea that should have
never seen the light of day (copying dma_map_ops and patching them up).

  reply	other threads:[~2018-08-02  8:59 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-01 15:14 add support for Xilinx PCIe root ports on RISC-V v2 Christoph Hellwig
2018-08-01 15:14 ` Christoph Hellwig
2018-08-01 15:14 ` [PATCH 1/3] PCI: add a callback to struct pci_host_bridge for adding a new device Christoph Hellwig
2018-08-01 15:14   ` Christoph Hellwig
2018-08-02 16:54   ` Lorenzo Pieralisi
2018-08-02 16:54     ` Lorenzo Pieralisi
2018-08-04 10:11     ` Christoph Hellwig
2018-08-04 10:11       ` Christoph Hellwig
2018-08-15 19:52     ` Bjorn Helgaas
2018-08-15 19:52       ` Bjorn Helgaas
2018-08-16 20:59       ` Bjorn Helgaas
2018-08-16 20:59         ` Bjorn Helgaas
2018-08-16 21:04         ` Arnd Bergmann
2018-08-16 21:04           ` Arnd Bergmann
2018-08-17 15:25           ` Lorenzo Pieralisi
2018-08-17 15:25             ` Lorenzo Pieralisi
2018-08-17 15:47             ` Arnd Bergmann
2018-08-17 15:47               ` Arnd Bergmann
2018-08-01 15:14 ` [PATCH 2/3] PCI/xilinx: Work-around for hardware DMA limit (32 bits) Christoph Hellwig
2018-08-01 15:14   ` Christoph Hellwig
2018-08-01 15:14 ` [PATCH 3/3] PCI/xilinx: Depend on OF instead of the ARCH Christoph Hellwig
2018-08-01 15:14   ` Christoph Hellwig
2018-08-02 16:56   ` Lorenzo Pieralisi
2018-08-02 16:56     ` Lorenzo Pieralisi
2018-08-04 10:12     ` Christoph Hellwig
2018-08-04 10:12       ` Christoph Hellwig
2018-08-01 23:02 ` add support for Xilinx PCIe root ports on RISC-V v2 Wesley Terpstra
2018-08-01 23:02   ` Wesley Terpstra
2018-08-02  7:14   ` Christoph Hellwig [this message]
2018-08-02  7:14     ` Christoph Hellwig

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=20180802071414.GA11584@lst.de \
    --to=hch@lst.de \
    --cc=arnd@arndb.de \
    --cc=bhelgaas@google.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=palmer@dabbelt.com \
    --cc=wesley@sifive.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 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.