From: Felipe Balbi <felipe.balbi@linux.intel.com>
To: Pierre LE MAGOUROU <plemagourou@softbankrobotics.com>,
Vivek Gautam <vivek.gautam@codeaurora.org>
Cc: Julien Massot <jmassot@softbankrobotics.com>,
Manu Gautam <mgautam@codeaurora.org>,
andy.gross@linaro.org, linux-soc@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
dianders@chromium.org, linux-usb@vger.kernel.org,
gregkh@linuxfoundation.org, bjorn.andersson@linaro.org
Subject: [v2] arm64: dts: msm8996: Use dwc3-qcom glue driver for USB
Date: Wed, 27 Jun 2018 12:27:30 +0300 [thread overview]
Message-ID: <87r2ksshod.fsf@linux.intel.com> (raw)
Hi,
Pierre LE MAGOUROU <plemagourou@softbankrobotics.com> writes:
>> > I have a branch that's based on 4.17. You can pick that.
>> > https://github.com/vivekgautam1/linux/commits/v4.17/db820c
>> >
>>
>> Thanks a lot,
>> I will test this branch.
>>
>>
> I just tested USB gadget with this branch on the db820c.
>
> If I activate a USB composite gadget device with EEM function, I can see
> the 'usb0' Ethernet interfaces on the device and on the host and I can ping
> the db820c from the host.
> When I create a USB composite gadget device with UAC2 function, I can see
> the audio cards on host and device but cannot play or record any sound.
>
> While looking at dwc3 traces with Ftrace, I noticed that the dwc3 driver is
> stuck on wait_event_lock_irq() in dwc3_gadget_ep_dequeue() function when I
> use UAC2 gadget.
can you share tracepoint data?
> *This email and any attachment thereto are confidential and intended
> solely for the use of the individual or entity to whom they are addressed.
>
> If you are not the intended recipient, please be advised that disclosing,
> copying, distributing or taking any action in reliance on the contents of
> this email is strictly prohibited. In such case, please immediately advise
> the sender, and delete all copies and attachment from your system.
> This
> email shall not be construed and is not tantamount to an offer, an
> acceptance of offer, or an agreement by SoftBank Robotics Europe on any
> discussion or contractual document whatsoever. No employee or agent is
> authorized to represent or bind SoftBank Robotics Europe to third parties
> by email, or act on behalf of SoftBank Robotics Europe by email, without
> express written confirmation by SoftBank Robotics Europe’ duly authorized
> representatives.
you need to talk to your company's IT about removing this footer. This
makes the life of those maintaining mailing list archives rather
difficult.
next reply other threads:[~2018-06-27 9:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 9:27 Felipe Balbi [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-07-10 15:03 [v2] arm64: dts: msm8996: Use dwc3-qcom glue driver for USB lemagoup
2018-06-27 12:30 Felipe Balbi
2018-06-26 9:37 Manu Gautam
2018-06-11 12:33 Julien Massot
2018-06-11 7:01 Vivek Gautam
2018-06-11 6:36 Julien Massot
2018-06-07 8:30 Vivek Gautam
2018-05-31 10:47 Manu Gautam
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=87r2ksshod.fsf@linux.intel.com \
--to=felipe.balbi@linux.intel.com \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=jmassot@softbankrobotics.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mgautam@codeaurora.org \
--cc=plemagourou@softbankrobotics.com \
--cc=vivek.gautam@codeaurora.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).