From: Wayne Chang <waynec@nvidia.com>
To: Jonathan Hunter <jonathanh@nvidia.com>,
Greg KH <gregkh@linuxfoundation.org>
Cc: Mathias Nyman <mathias.nyman@intel.com>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"vkoul@kernel.org" <vkoul@kernel.org>,
Thierry Reding <treding@nvidia.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-phy@lists.infradead.org" <linux-phy@lists.infradead.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
Sing-Han Chen <singhanc@nvidia.com>
Subject: Re: [PATCH V4 5/6] usb: host: xhci-tegra: Add Tegra234 XHCI support
Date: Thu, 24 Nov 2022 12:30:12 +0000 [thread overview]
Message-ID: <7ea7739f-bade-985d-78eb-8129982eb138@nvidia.com> (raw)
In-Reply-To: <4e621d81-929d-3fe5-ee8d-00751f157e5c@nvidia.com>
On 11/23/22 22:20, Jon Hunter wrote:
>
> On 22/11/2022 16:07, Greg KH wrote:
>> On Fri, Nov 18, 2022 at 03:40:05PM +0000, Jon Hunter wrote:
>>> From: Sing-Han Chen <singhanc@nvidia.com>
>>>
>>> This change adds Tegra234 XUSB host mode controller support.
>>>
>>> In Tegra234, some of the registers have moved to bar2 space.
>>> The new soc variable has_bar2 indicates the chip with bar2
>>> area. This patch adds new reg helper to let the driver reuse
>>> the same code for those chips with bar2 support.
>>>
>>> Signed-off-by: Sing-Han Chen <singhanc@nvidia.com>
>>> Co-developed-by: Wayne Chang <waynec@nvidia.com>
>>> Signed-off-by: Wayne Chang <waynec@nvidia.com>
>>> Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
>>
>> This is should be much slower with the additional redirection. Is it
>> noticable on this hardware platform with, and without this change? Or
>> is the hardware slow enough that it doesn't even show up as a speed
>> decrease?
> Wayne, do we have any inputs on this?
>
> I know that we have been using this implementation now for some time on
> the kernels we ship and that would be tested on Tegra210, Tegar186,
> Tegra194 and Tegra234. So I assume that the performance there is good,
> but not sure about Tegra124.
>
Hi Jonathan and Greg,
Thanks for the review.
The implementation is out of the difference in hardware implementation
between old chips and tegra234.
Most of the read/write ops are one-time calls during initialization.
Even the mbox msg are seldom used and thus the redirection should not
cause any noticeable performance drop.
thanks,
Wayne.
> Jon
>
next prev parent reply other threads:[~2022-11-24 12:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 15:40 [PATCH V4 0/6] Enable USB host on Jetson AGX Orin Jon Hunter
2022-11-18 15:40 ` [PATCH V4 1/6] dt-bindings: usb: Add NVIDIA Tegra234 XUSB host controller binding Jon Hunter
2022-11-18 18:50 ` Rob Herring
2022-11-18 15:40 ` [PATCH V4 2/6] arm64: tegra: Enable XUSB host function on Jetson AGX Orin Jon Hunter
2022-11-18 15:40 ` [PATCH V4 3/6] phy: tegra: xusb: Disable trk clk when not in use Jon Hunter
2022-11-18 15:40 ` [PATCH V4 4/6] phy: tegra: xusb: Add Tegra234 support Jon Hunter
2022-11-18 15:40 ` [PATCH V4 5/6] usb: host: xhci-tegra: Add Tegra234 XHCI support Jon Hunter
2022-11-22 16:07 ` Greg KH
2022-11-23 14:20 ` Jon Hunter
2022-11-24 12:30 ` Wayne Chang [this message]
2022-11-18 15:40 ` [PATCH V4 6/6] dt-bindings: phy: tegra-xusb: Add support for Tegra234 Jon Hunter
2022-11-30 17:07 ` Rob Herring
2022-12-02 9:53 ` Jon Hunter
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=7ea7739f-bade-985d-78eb-8129982eb138@nvidia.com \
--to=waynec@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=robh+dt@kernel.org \
--cc=singhanc@nvidia.com \
--cc=treding@nvidia.com \
--cc=vkoul@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