From: Felipe Balbi <felipe.balbi@linux.intel.com>
To: "Thang Q. Nguyen" <tqnguyen@apm.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-omap@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm@lists.infradead.org,
Phong Vo <pvo@apm.com>, Loc Ho <lho@apm.com>,
patches <patches@apm.com>
Subject: Re: [PATCH v3 1/2] usb:dwc3: Enable support for 64-bit system
Date: Thu, 31 Mar 2016 11:04:13 +0300 [thread overview]
Message-ID: <87mvpfgjk2.fsf@intel.com> (raw)
In-Reply-To: <CAKrQpSt3Tm4Bu02ujgDnYu+29zA8VuWQ18o-TFMU1HJ970CkSA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3275 bytes --]
Hi,
(please don't top-post)
"Thang Q. Nguyen" <tqnguyen@apm.com> writes:
> Hi Balbi,
> If CONFIG_DMA_CMA=y, dma mask is set properly. The issue just happen
> when CONFIG_DMA_CMA is not set. In this case, dma mask is not set and
> we need this code to check if dma mask should be manually set to 32 or
> 64.
Can you point me to the code which has this conditional ? Why would
DMA_CMA=n mean that dma_mask isn't initialized ? According to DMA_CMA's
help text (see below) that's supposed to allow drivers to *allocate*
large contiguous buffers, but that's not the case here.
config DMA_CMA
bool "DMA Contiguous Memory Allocator"
depends on HAVE_DMA_CONTIGUOUS && CMA
help
This enables the Contiguous Memory Allocator which allows drivers
to allocate big physically-contiguous blocks of memory for use with
hardware components that do not support I/O map nor scatter-gather.
You can disable CMA by specifying "cma=0" on the kernel's command
line.
For more information see <include/linux/dma-contiguous.h>.
If unsure, say "n".
>
> ----
> Thang
>
> On Wed, Mar 30, 2016 at 8:09 PM, Felipe Balbi
> <felipe.balbi@linux.intel.com> wrote:
>>
>> Hi,
>>
>> "Thang Q. Nguyen" <tqnguyen@apm.com> writes:
>>> From: "Thang Q. Nguyen" <tqnguyen@apm.com>
>>>
>>> Add 64-bit DMA operation support to the USB DWC3 driver.
>>> First attempt to set the coherent DMA mask for 64-bit DMA.
>>> If that failed, attempt again with 32-bit DMA.
>>>
>>> Changes from v2:
>>> - None.
>>>
>>> Changes from v1:
>>> - Remove WARN_ON if dma_mask is NULL
>>
>> these changes lines should be between the tearline (---) and diffstat
>> below.
>>
>>> Signed-off-by: Thang Q. Nguyen <tqnguyen@apm.com>
>>> ---
>>> drivers/usb/dwc3/core.c | 15 +++++++++++++++
>>> 1 file changed, 15 insertions(+)
>>>
>>> diff --git a/drivers/usb/dwc3/core.c b/drivers/usb/dwc3/core.c
>>> index de5e01f..2479c24 100644
>>> --- a/drivers/usb/dwc3/core.c
>>> +++ b/drivers/usb/dwc3/core.c
>>> @@ -831,6 +831,21 @@ static int dwc3_probe(struct platform_device *pdev)
>>> dwc->mem = mem;
>>> dwc->dev = dev;
>>>
>>> + /* Try to set 64-bit DMA first */
>>> + if (!pdev->dev.dma_mask)
>>> + /* Platform did not initialize dma_mask */
>>> + ret = dma_coerce_mask_and_coherent(&pdev->dev,
>>> + DMA_BIT_MASK(64));
>>> + else
>>> + ret = dma_set_mask_and_coherent(&pdev->dev, DMA_BIT_MASK(64));
>>> +
>>> + /* If seting 64-bit DMA mask fails, fall back to 32-bit DMA mask */
>>> + if (ret) {
>>> + ret = dma_set_mask_and_coherent(&pdev->dev, DMA_BIT_MASK(32));
>>> + if (ret)
>>> + return ret;
>>> + }
>>
>> Also, why is it so that you need this now ? glue layers are copying dma
>> mask from parent device and that should be set properly. This really
>> shouldn't be necessary in dwc3-core; it would mean that glue layer
>> didn't set this device up properly.
>>
>> --
>> balbi
>
>
>
> --
>
> Thang Q. Nguyen | Staff SW Eng.
>
> C: +849.7684.7606 | O: +848.3770.0640
>
> F: +848.3770.0641 | tqnguyen@apm.com
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2016-03-31 8:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 7:18 [PATCH v3 0/2] usb:dwc3: Enable USB DWC3 support for 64-bit system Thang Q. Nguyen
2016-03-10 7:18 ` [PATCH v3 1/2] usb:dwc3: Enable " Thang Q. Nguyen
[not found] ` <1457594332-7490-2-git-send-email-tqnguyen-qTEPVZfXA3Y@public.gmane.org>
2016-03-30 13:09 ` Felipe Balbi
2016-03-31 7:34 ` Thang Q. Nguyen
2016-03-31 8:04 ` Felipe Balbi [this message]
2016-03-10 7:18 ` [PATCH v3 2/2] usb:dwc3: pass arch data to xhci-hcd child Thang Q. Nguyen
2016-03-30 13:10 ` Felipe Balbi
2016-03-30 13:52 ` Grygorii Strashko
2016-03-30 13:55 ` Felipe Balbi
[not found] ` <87egashxz8.fsf-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-03-31 7:39 ` Thang Q. Nguyen
2016-03-31 8:04 ` Felipe Balbi
2016-03-31 15:07 ` Grygorii Strashko
[not found] ` <56FD3D2F.8070501-l0cyMroinI0@public.gmane.org>
2016-04-01 7:58 ` Felipe Balbi
2016-04-01 9:46 ` Grygorii Strashko
[not found] ` <56FE4378.3030205-l0cyMroinI0@public.gmane.org>
2016-04-01 10:20 ` Felipe Balbi
[not found] ` <87shz58wbw.fsf-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-04-01 11:00 ` Grygorii Strashko
[not found] ` <56FE54DB.5000201-l0cyMroinI0@public.gmane.org>
2016-04-01 11:57 ` Felipe Balbi
[not found] ` <878u0x8ru4.fsf-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-04-01 18:15 ` santosh shilimkar
[not found] ` <56FEBAC1.2040509-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2016-04-04 6:28 ` Felipe Balbi
2016-04-04 16:11 ` santosh shilimkar
2016-04-05 5:18 ` Felipe Balbi
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=87mvpfgjk2.fsf@intel.com \
--to=felipe.balbi@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=lho@apm.com \
--cc=linux-arm@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=patches@apm.com \
--cc=pvo@apm.com \
--cc=tqnguyen@apm.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).