devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Nagarjuna Kristam <nkristam@nvidia.com>
Cc: balbi@kernel.org, gregkh@linuxfoundation.org,
	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
Subject: Re: [PATCH V1 2/4] arm64: tegra: Add xudc node for Tegra194
Date: Tue, 28 Apr 2020 14:16:26 +0200	[thread overview]
Message-ID: <20200428121626.GL3592148@ulmo> (raw)
In-Reply-To: <1587022460-31988-3-git-send-email-nkristam@nvidia.com>

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

On Thu, Apr 16, 2020 at 01:04:18PM +0530, Nagarjuna Kristam wrote:
> Tegra194 has one XUSB device mode controller, which can be operated
> HS and SS modes. Add DT entry for XUSB device mode controller
> 
> Signed-off-by: Nagarjuna Kristam <nkristam@nvidia.com>
> ---
>  arch/arm64/boot/dts/nvidia/tegra194.dtsi | 18 ++++++++++++++++++
>  1 file changed, 18 insertions(+)

Looks good to me, I'll pick this up into the Tegra tree.

Thierry

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

  reply	other threads:[~2020-04-28 12:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-16  7:34 [PATCH V1 0/4] Tegra XUDC support on Tegra194 Soc Nagarjuna Kristam
2020-04-16  7:34 ` [PATCH V1 1/4] dt-bindings: usb: tegra-xudc: Add Tegra194 XUSB controller support Nagarjuna Kristam
2020-04-28 10:58   ` Thierry Reding
2020-04-28 16:39   ` Rob Herring
2020-04-16  7:34 ` [PATCH V1 2/4] arm64: tegra: Add xudc node for Tegra194 Nagarjuna Kristam
2020-04-28 12:16   ` Thierry Reding [this message]
2020-04-16  7:34 ` [PATCH V1 3/4] usb: gadget: tegra-xudc: Add Tegra194 support Nagarjuna Kristam
2020-04-28 12:21   ` Thierry Reding
2020-04-16  7:34 ` [PATCH V1 4/4] usb: gadget: tegra-xudc: add port_speed_quirk Nagarjuna Kristam
2020-04-28 12:25   ` Thierry Reding
2020-05-04  4:03     ` Nagarjuna Kristam

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=20200428121626.GL3592148@ulmo \
    --to=thierry.reding@gmail.com \
    --cc=balbi@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jonathanh@nvidia.com \
    --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 \
    /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).