From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Felipe Balbi <balbi@kernel.org>,
Kishon Vijay Abraham I <kishon@ti.com>,
Nagarjuna Kristam <nkristam@nvidia.com>,
jonathanh@nvidia.com, mark.rutland@arm.com, robh+dt@kernel.org,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Patch V10 0/8] Tegra XUSB gadget driver support
Date: Tue, 15 Oct 2019 19:58:20 +0200 [thread overview]
Message-ID: <20191015175820.GC1072965@kroah.com> (raw)
In-Reply-To: <20191014100257.GB419598@ulmo>
On Mon, Oct 14, 2019 at 12:02:57PM +0200, Thierry Reding wrote:
> On Mon, Sep 23, 2019 at 01:55:44PM +0530, Nagarjuna Kristam wrote:
> > Patches 1-3 are phy driver changes to add support for device
> > mode.
> > Patches 4-7 are changes related to XUSB device mode
> > controller driver.
> > Patch 8 is to enable drivers for XUDC support in defconfig
> >
> > Test Steps(USB 2.0):
> > - Enable "USB Gadget precomposed configurations" in defconfig
> > - Build, flash and boot Jetson TX1
> > - Connect Jetson TX1 and Ubuntu device using USB A to Micro B
> > cable
> > - After boot on Jetson TX1 terminal usb0 network device should be
> > enumerated
> > - Assign static ip to usb0 on Jetson TX1 and corresponding net
> > device on ubuntu
> > - Run ping test and transfer test(used scp) to check data transfer
> > communication
>
> Hi Felipe, Kishon, Greg,
>
> Patches 1-3 provide new API that is required by patch 7, so I think
> patches 1, 2, 3, 4 and 7 should probably all go through a single tree to
> avoid having to model the dependencies using stable branches.
>
> Kishon, patches 1-3 have gone through several rounds of review already,
> but do you have any remaining concerns on them? If not, it'd be great if
> you could ack them. Felipe and Greg could then pick them up along with
> patches 4 and 7 into the USB tree.
>
> Felipe, Greg, does that sound like a reasonable plan?
Fine with me.
> I should also mention that while waiting for review, Nagarjuna has been
> able to extend support for the XUDC driver to Tegra186 but has so far
> been holding back on sending them out so as to not needlessly hold up
> progress on this series. However, given the interdependencies, I've come
> to think that it may be preferable to merge everything in one go instead
> of revisiting this in a couple of weeks.
>
> If you guys prefer, Nagarjuna could send out v11 of the series and
> integrate Tegra186 support.
That's also fine.
thanks,
greg k-h
prev parent reply other threads:[~2019-10-15 17:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-23 8:25 [Patch V10 0/8] Tegra XUSB gadget driver support Nagarjuna Kristam
2019-09-23 8:25 ` Nagarjuna Kristam
2019-09-23 8:25 ` [Patch V10 1/8] phy: tegra: xusb: Add XUSB dual mode support on Tegra210 Nagarjuna Kristam
2019-09-23 8:25 ` Nagarjuna Kristam
2019-09-23 8:25 ` [Patch V10 2/8] phy: tegra: xusb: Add usb3 port fake " Nagarjuna Kristam
2019-09-23 8:25 ` Nagarjuna Kristam
2019-09-23 8:25 ` [Patch V10 3/8] phy: tegra: xusb: Add vbus override " Nagarjuna Kristam
2019-09-23 8:25 ` Nagarjuna Kristam
2019-09-23 8:25 ` [Patch V10 4/8] dt-bindings: usb: Add NVIDIA Tegra XUSB device mode controller binding Nagarjuna Kristam
2019-09-23 8:25 ` Nagarjuna Kristam
2019-09-23 8:25 ` [Patch V10 5/8] arm64: tegra: Add xudc node for Tegra210 Nagarjuna Kristam
2019-09-23 8:25 ` Nagarjuna Kristam
2019-09-23 8:25 ` [Patch V10 6/8] arm64: tegra: Enable xudc on Jetson TX1 Nagarjuna Kristam
2019-09-23 8:25 ` Nagarjuna Kristam
2019-09-23 8:25 ` [Patch V10 7/8] usb: gadget: Add UDC driver for tegra XUSB device mode controller Nagarjuna Kristam
2019-09-23 8:25 ` Nagarjuna Kristam
2019-10-14 9:51 ` Thierry Reding
2019-09-23 8:25 ` [Patch V10 8/8] arm64: defconfig: Enable tegra XUDC support Nagarjuna Kristam
2019-09-23 8:25 ` Nagarjuna Kristam
2019-09-26 9:04 ` [Patch V10 0/8] Tegra XUSB gadget driver support Thierry Reding
2019-10-14 10:02 ` Thierry Reding
2019-10-15 17:58 ` Greg Kroah-Hartman [this message]
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=20191015175820.GC1072965@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=balbi@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nkristam@nvidia.com \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.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 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.