devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Jon Hunter <jonathanh@nvidia.com>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
	linux-tegra@vger.kernel.org
Subject: Re: [PATCH V5 0/5] Tegra USB device support updates
Date: Tue, 24 Jan 2023 14:57:40 +0100	[thread overview]
Message-ID: <Y8/j1HBwgEdd4Mp2@orome> (raw)
In-Reply-To: <20230119104208.28726-1-jonathanh@nvidia.com>

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

On Thu, Jan 19, 2023 at 10:42:03AM +0000, Jon Hunter wrote:
> This series adds USB device support for Tegra234. 3/5 patches were
> originally part of the series to add both USB host and device support
> for Tegra234 [0]. However, the series was getting quite large and so I
> have split this into a separate series but calling it 'V4' to indicate
> that this is not completely new either.
> 
> I have added two more patches in this version to fix DMA coherency for
> Tegra194.
> 
> [0] https://lore.kernel.org/linux-tegra/20221114124053.1873316-1-waynec@nvidia.com/
> 
> Jon Hunter (3):
>   dt-bindings: usb: tegra-xudc: Add dma-coherent for Tegra194
>   arm64: tegra: Add dma-coherent property for Tegra194 XUDC
>   arm64: tegra: Populate the XUDC node for Tegra234
> 
> Sing-Han Chen (1):
>   usb: gadget: tegra-xudc: Add Tegra234 support
> 
> Wayne Chang (1):
>   dt-bindings: usb: tegra-xudc: Add Tegra234 XUDC support
> 
>  .../bindings/usb/nvidia,tegra-xudc.yaml       | 15 ++++++++++++
>  arch/arm64/boot/dts/nvidia/tegra194.dtsi      |  1 +
>  arch/arm64/boot/dts/nvidia/tegra234.dtsi      | 23 +++++++++++++++++++
>  drivers/usb/gadget/udc/tegra-xudc.c           | 17 ++++++++++++++
>  4 files changed, 56 insertions(+)

I've picked up patches 2 and 5 of this series into the Tegra tree. Greg,
can you pick up patches 1, 3 and 4?

Thanks,
Thierry

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

  parent reply	other threads:[~2023-01-24 13:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-19 10:42 [PATCH V5 0/5] Tegra USB device support updates Jon Hunter
2023-01-19 10:42 ` [PATCH V5 1/5] dt-bindings: usb: tegra-xudc: Add dma-coherent for Tegra194 Jon Hunter
2023-01-22 14:12   ` Krzysztof Kozlowski
2023-01-24 13:58   ` Thierry Reding
2023-01-19 10:42 ` [PATCH V5 2/5] arm64: tegra: Add dma-coherent property for Tegra194 XUDC Jon Hunter
2023-01-19 10:42 ` [PATCH V5 3/5] dt-bindings: usb: tegra-xudc: Add Tegra234 XUDC support Jon Hunter
2023-01-24 13:58   ` Thierry Reding
2023-01-19 10:42 ` [PATCH V5 4/5] usb: gadget: tegra-xudc: Add Tegra234 support Jon Hunter
2023-01-24 13:58   ` Thierry Reding
2023-01-19 10:42 ` [PATCH V5 5/5] arm64: tegra: Populate the XUDC node for Tegra234 Jon Hunter
2023-01-24 13:57 ` Thierry Reding [this message]
2023-01-25 14:44   ` [PATCH V5 0/5] Tegra USB device support updates Greg Kroah-Hartman

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=Y8/j1HBwgEdd4Mp2@orome \
    --to=thierry.reding@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jonathanh@nvidia.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --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).