linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@codeaurora.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Peter Chen <Peter.Chen@nxp.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
	Sriram Dash <sriram.dash@nxp.com>
Subject: Re: [RESEND PATCH] usb: chipidea: Configure DMA properties and ops from DT
Date: Fri, 21 Oct 2016 10:38:27 -0700	[thread overview]
Message-ID: <20161021173827.GJ26139@codeaurora.org> (raw)
In-Reply-To: <1477069159-12399-1-git-send-email-bjorn.andersson@linaro.org>

On 10/21, Bjorn Andersson wrote:
> hcd_alloc_coherent() and usb_alloc_coherent() ends up allocating coherent
> memory on behalf of ci_hdrc driver. But as the ci_hdrc is instantiated manually
> it will not have any dma_mem or dma_ops assigned, which makes the
> dma_alloc_coherent() fail on some platforms (e.g. arm64). This patch solves
> this by assigning the dma_mem and dma_ops based on the parent's DeviceTree
> node.
> 
> Cc: Stephen Boyd <sboyd@codeaurora.org>
> Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
> ---
> 
> Hi Peter,
> 
> After (once more) debugging why USB doesn't work up on the 64-bit Qualcomm
> systems I realized that we never concluded on this patch. Unfortunately I can't
> find it in my mailbox either, so resending it to restart the discussion.
> 

I thought we were going to go down the route that Arnd has been
pushing[1]? That should work, but I haven't tried it yet and
there are some more fixes on top from Sriram. I think Sriram is
taking over the patch now?

[1] https://patchwork.kernel.org/patch/9319527/

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

  reply	other threads:[~2016-10-21 17:38 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-22  5:32 [PATCH] usb: chipidea: Configure DMA properties and ops from DT Bjorn Andersson
2016-02-22  6:02 ` Peter Chen
2016-02-22  6:14   ` Bjorn Andersson
2016-02-22 10:03 ` Srinivas Kandagatla
2016-02-22 22:07   ` Bjorn Andersson
2016-02-23  1:31     ` Peter Chen
2016-03-02 22:59     ` Li Yang
2016-03-08 19:52       ` Li Yang
2016-03-09  3:40         ` Bjorn Andersson
2016-03-09 23:16           ` Li Yang
2016-03-14 10:51             ` Peter Chen
2016-03-17 15:52               ` Arnd Bergmann
2016-03-18  1:54                 ` Peter Chen
2016-03-18  3:25                   ` Rajesh Bhagat
2016-03-18  7:28                   ` Arnd Bergmann
2016-03-18 10:56                   ` Russell King - ARM Linux
2016-03-25  4:02           ` Peter Chen
2016-03-25  4:39             ` [PATCH 1/1] usb: chipidea: add DMA mask configuration API kbuild test robot
2016-10-21 16:59 ` [RESEND PATCH] usb: chipidea: Configure DMA properties and ops from DT Bjorn Andersson
2016-10-21 17:38   ` Stephen Boyd [this message]
2016-10-21 17:53     ` Bjorn Andersson
2016-10-22  6:22     ` Sriram Dash

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=20161021173827.GJ26139@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=Peter.Chen@nxp.com \
    --cc=arnd@arndb.de \
    --cc=bjorn.andersson@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=sriram.dash@nxp.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).