From: Vivek Gautam <vivek.gautam@codeaurora.org>
To: Julien Massot <jmassot@softbankrobotics.com>
Cc: 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,
felipe.balbi@linux.intel.com, gregkh@linuxfoundation.org,
bjorn.andersson@linaro.org
Subject: [v2] arm64: dts: msm8996: Use dwc3-qcom glue driver for USB
Date: Mon, 11 Jun 2018 12:31:48 +0530 [thread overview]
Message-ID: <c13e4dae-aba3-727a-9242-a968af450794@codeaurora.org> (raw)
Hi,
On 6/11/2018 12:06 PM, Julien Massot wrote:
> Hi,
>
>> On 5/31/2018 4:17 PM, Manu Gautam wrote:
>>> Move from dwc3-of-simple to dwc3-qcom glue driver to
>>> support peripheral mode which requires qscratch wrapper
>>> programming on VBUS event.
> I would like to test usb otg as peripheral role, but that's not clear
> for me which patches
> are required on top of linux master branch or linaro qcom-lt
> integration branch, or a
> custom branch which integrate dt-binding phy or usb related patch.
>
> Can you point me the patches I need to apply, or a branch, to test
> peripheral feature ?
I have a branch that's based on 4.17. You can pick that.
https://github.com/vivekgautam1/linux/commits/v4.17/db820c
Thanks
Vivek
>
> Thanks,
> Julien
>
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2018-06-11 7:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 7:01 Vivek Gautam [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-27 9:27 Felipe Balbi
2018-06-26 9:37 Manu Gautam
2018-06-11 12:33 Julien Massot
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=c13e4dae-aba3-727a-9242-a968af450794@codeaurora.org \
--to=vivek.gautam@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=felipe.balbi@linux.intel.com \
--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 \
/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).