linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: okaya@codeaurora.org (Sinan Kaya)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] arm64: Allow for different DMA and CPU bus offsets
Date: Wed, 18 May 2016 14:59:25 -0400	[thread overview]
Message-ID: <573CBB8D.4020409@codeaurora.org> (raw)
In-Reply-To: <1463576010-115428-1-git-send-email-agraf@suse.de>

On 5/18/2016 8:53 AM, Alexander Graf wrote:
> ---
> 
> This patch may conflict with another patch titled "swiotlb: prefix dma_to_phys
> and phys_to_dma functions" which is in flight, but hasn't seen an update since
> March.

Thanks for the heads up. Due to missing API in DMA API, I couldn't make progress
with the series.

I need dma_map_resource API to get merged. After that one of the drivers
that actually uses dma_to_phys need to be changed to use dma_map_resource. 

Then the rest of the series can come.

-- 
Sinan Kaya
Qualcomm Technologies, Inc. on behalf of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project

      parent reply	other threads:[~2016-05-18 18:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-18 12:53 [PATCH v2] arm64: Allow for different DMA and CPU bus offsets Alexander Graf
2016-05-18 13:05 ` Arnd Bergmann
2016-05-18 13:27 ` Catalin Marinas
2016-05-18 13:49   ` Alexander Graf
2016-05-18 14:26     ` Catalin Marinas
2016-05-18 14:34       ` Alexander Graf
2016-05-18 15:19         ` Catalin Marinas
2016-05-18 15:33           ` Alexander Graf
2016-05-18 16:08             ` Arnd Bergmann
2016-05-18 16:16               ` Alexander Graf
2016-05-18 17:18   ` Eric Anholt
2016-06-01  8:42   ` Catalin Marinas
2016-06-07 22:08     ` Eric Anholt
2016-05-18 18:59 ` Sinan Kaya [this message]

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=573CBB8D.4020409@codeaurora.org \
    --to=okaya@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).