linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Balbi <felipe.balbi@linux.intel.com>
To: Grygorii Strashko <grygorii.strashko@ti.com>,
	"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,
	Arnd Bergmann <arnd@arndb.de>, "Karicheri\,
	Muralidharan" <m-karicheri2@ti.com>,
	Peter Ujfalusi <peter.ujfalusi@ti.com>, Phong Vo <pvo@apm.com>,
	Loc Ho <lho@apm.com>, patches <patches@apm.com>,
	Santosh Shilimkar <ssantosh@kernel.org>,
	"Ben Dooks \(embedded platforms\)" <ben-linux@fluff.org>
Subject: Re: [PATCH v3 2/2] usb:dwc3: pass arch data to xhci-hcd child
Date: Fri, 01 Apr 2016 13:20:03 +0300	[thread overview]
Message-ID: <87shz58wbw.fsf@intel.com> (raw)
In-Reply-To: <56FE4378.3030205@ti.com>

[-- Attachment #1: Type: text/plain, Size: 1546 bytes --]


Hi,

Grygorii Strashko <grygorii.strashko@ti.com> writes:
>> if of_dma_configure() does what you want, why don't you just stick it in
>> dwc3-keystone.c and let the driver continue to copy things for now ?
>> Something like below, perhaps ?
>> 
>
> I know (and i have patch to fix that which I'm going to send) that DMA config 
>  in dwc3-keystone.c is not correct and we are good till now just 
> because dwc3_keystone is not used for DMA operations directly.
>
> Now about xhci and friends:
> dwc3_keystone *is created* from DT : of_platform_device_create() -> of_platform_device_create_pdata() -> of_dma_configure()
> |- dwc3 *is created* from DT : of_platform_device_create() -> of_platform_device_create_pdata() -> of_dma_configure()
>    |- [1] *creates* xhci dev manually : DMA configuration copied manually in dwc3_host_init()
>    |- [2] *creates* usb_gadget dev manually: DMA configuration copied manually in usb_add_gadget_udc_release()
>    |- *creates* usb_udc dev manually : not used for DMA operations directly (as I've checked)
>
> Now cases [1] & [2] introduces failures, because DMA configuration is not complete for
> these devices.

right, then we just copy whatever's missing, right ? Until there's a
generic way of copying these bits, I want to avoid introducing any of_*
specific methodologies and prefer to have the manual copy.

> I can confirm that if I fix [1] & [2] as above USB Device/Dual modes will start 
> working on K2E.

cool, I'd be happy to take both patches ;-)

-- 
balbi

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]

  reply	other threads:[~2016-04-01 10:22 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
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:52     ` Grygorii Strashko
2016-03-30 13:55       ` Felipe Balbi
2016-03-31  7:39         ` Thang Q. Nguyen
2016-03-31  8:04           ` Felipe Balbi
2016-03-31 15:07             ` Grygorii Strashko
2016-04-01  7:58               ` Felipe Balbi
2016-04-01  9:46                 ` Grygorii Strashko
2016-04-01 10:20                   ` Felipe Balbi [this message]
2016-04-01 11:00                     ` Grygorii Strashko
2016-04-01 11:57                       ` Felipe Balbi
2016-04-01 18:15                         ` santosh shilimkar
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=87shz58wbw.fsf@intel.com \
    --to=felipe.balbi@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=ben-linux@fluff.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=grygorii.strashko@ti.com \
    --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=m-karicheri2@ti.com \
    --cc=patches@apm.com \
    --cc=peter.ujfalusi@ti.com \
    --cc=pvo@apm.com \
    --cc=ssantosh@kernel.org \
    --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).