From: JC Kuo <jckuo@nvidia.com>
To: Vinod Koul <vkoul@kernel.org>
Cc: Jim Lin <jilin@nvidia.com>,
thierry.reding@gmail.com, jonathanh@nvidia.com, balbi@kernel.org,
gregkh@linuxfoundation.org, bhsieh@nvidia.com,
linux-phy@lists.infradead.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH v2 1/2] phy: tegra: xusb: add utmi pad power on/down ops
Date: Wed, 14 Sep 2022 10:59:45 +0800 [thread overview]
Message-ID: <42ae1deb-bbdd-2a16-c671-0bc17d3e2647@nvidia.com> (raw)
In-Reply-To: <YyCVBVRQo+qPo5vH@matsya>
On 9/13/22 22:34, Vinod Koul wrote:
> On 06-09-22, 10:43, JC Kuo wrote:
>> Hi Vinod,
>
> Please _do_ _not_ _top_ _post_
>
>> Before the device or host is being attached, we can keep most of the
>> transceivers powered down (PD=1/PD_DR=1) to minimize power consumption. At this
>> stage, in .phy_power_on(), we enable only the single-ended receiver (PD_ZI=0)
>> for detecting connection. Upon detecting device's or host's connection, host or
>> controller driver will invoke tegra_phy_xusb_utmi_pad_power_on() to power on all
>> of the transceivers (PD=0/PD_DR=0) to equip full link functionality.
>
> Thanks for this explanation... It helps!
>
> Just a suggestion, can this be moved into phy_init() you have detected
> connection in phy_power_on(), the transceiver can be enabled in
> phy_int... Would that work?
> That would work, too. However, because Tegra USB has separate phys for USB3 SS
and USB2, I'd like to keep the USB2 phy operations as they are now, so that USB
host and device controller drivers do not have to distinguish the phy type and
invoke different phy stubs. Furthermore, PD_ZI=0 does really power on the USB2
phy, partially.
For example:
1. in .probe(),
for_each_usb_phy {
phy_init(phy);
}
for_each_usb3_phy {
phy_power_on(phy);
};
2. upon detecting connection,
phy_power_on(the_target_usb2_phy);
Thanks,
JC
next prev parent reply other threads:[~2022-09-14 3:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 8:23 [PATCH v2 0/2] usb: tegra: power down UTMI pad Jim Lin
2022-08-16 8:23 ` [PATCH v2 1/2] phy: tegra: xusb: add utmi pad power on/down ops Jim Lin
2022-09-04 14:45 ` Vinod Koul
2022-09-06 2:43 ` JC Kuo
2022-09-13 14:34 ` Vinod Koul
2022-09-14 2:59 ` JC Kuo [this message]
2022-09-20 6:33 ` Vinod Koul
2022-08-16 8:23 ` [PATCH v2 2/2] usb: gadget: tegra: Reduce pad power Jim Lin
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=42ae1deb-bbdd-2a16-c671-0bc17d3e2647@nvidia.com \
--to=jckuo@nvidia.com \
--cc=balbi@kernel.org \
--cc=bhsieh@nvidia.com \
--cc=gregkh@linuxfoundation.org \
--cc=jilin@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=thierry.reding@gmail.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