From: Felipe Balbi <felipe.balbi-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
To: Greg Kroah-Hartman
<gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>,
linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Cc: Thang Nguyen <tqnguyen-qTEPVZfXA3Y@public.gmane.org>,
Phong Vo <pvo-qTEPVZfXA3Y@public.gmane.org>,
Loc Ho <lho-qTEPVZfXA3Y@public.gmane.org>,
patches-qTEPVZfXA3Y@public.gmane.org
Subject: Re: [PATCH v3 1/2] usb:dwc3: Enable support for 64-bit system
Date: Wed, 30 Mar 2016 16:09:21 +0300 [thread overview]
Message-ID: <87pouci03i.fsf@intel.com> (raw)
In-Reply-To: <1457594332-7490-2-git-send-email-tqnguyen-qTEPVZfXA3Y@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1708 bytes --]
Hi,
"Thang Q. Nguyen" <tqnguyen-qTEPVZfXA3Y@public.gmane.org> writes:
> From: "Thang Q. Nguyen" <tqnguyen-qTEPVZfXA3Y@public.gmane.org>
>
> 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-qTEPVZfXA3Y@public.gmane.org>
> ---
> 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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Felipe Balbi <felipe.balbi@linux.intel.com>
To: "Thang Q. Nguyen" <tqnguyen@apm.com>,
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
Cc: Thang Nguyen <tqnguyen@apm.com>, Phong Vo <pvo@apm.com>,
Loc Ho <lho@apm.com>,
patches@apm.com
Subject: Re: [PATCH v3 1/2] usb:dwc3: Enable support for 64-bit system
Date: Wed, 30 Mar 2016 16:09:21 +0300 [thread overview]
Message-ID: <87pouci03i.fsf@intel.com> (raw)
In-Reply-To: <1457594332-7490-2-git-send-email-tqnguyen@apm.com>
[-- Attachment #1: Type: text/plain, Size: 1645 bytes --]
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2016-03-30 13:09 UTC|newest]
Thread overview: 37+ 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 ` 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 [this message]
2016-03-30 13:09 ` Felipe Balbi
2016-03-31 7:34 ` Thang Q. Nguyen
2016-03-31 8:04 ` Felipe Balbi
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:10 ` Felipe Balbi
2016-03-30 13:52 ` Grygorii Strashko
2016-03-30 13:52 ` Grygorii Strashko
2016-03-30 13:55 ` Felipe Balbi
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 7:39 ` Thang Q. Nguyen
2016-03-31 8:04 ` Felipe Balbi
2016-03-31 8:04 ` Felipe Balbi
2016-03-31 15:07 ` Grygorii Strashko
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 7:58 ` Felipe Balbi
2016-04-01 9:46 ` Grygorii Strashko
2016-04-01 9:46 ` Grygorii Strashko
[not found] ` <56FE4378.3030205-l0cyMroinI0@public.gmane.org>
2016-04-01 10:20 ` Felipe Balbi
2016-04-01 10:20 ` Felipe Balbi
[not found] ` <87shz58wbw.fsf-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-04-01 11:00 ` Grygorii Strashko
2016-04-01 11:00 ` Grygorii Strashko
[not found] ` <56FE54DB.5000201-l0cyMroinI0@public.gmane.org>
2016-04-01 11:57 ` Felipe Balbi
2016-04-01 11:57 ` Felipe Balbi
[not found] ` <878u0x8ru4.fsf-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-04-01 18:15 ` santosh shilimkar
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 6:28 ` Felipe Balbi
2016-04-04 16:11 ` santosh shilimkar
2016-04-05 5:18 ` Felipe Balbi
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=87pouci03i.fsf@intel.com \
--to=felipe.balbi-vuqaysv1563yd54fqh9/ca@public.gmane.org \
--cc=gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \
--cc=lho-qTEPVZfXA3Y@public.gmane.org \
--cc=linux-arm-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=patches-qTEPVZfXA3Y@public.gmane.org \
--cc=pvo-qTEPVZfXA3Y@public.gmane.org \
--cc=tqnguyen-qTEPVZfXA3Y@public.gmane.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 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.