From: Greg KH <gregkh@linuxfoundation.org>
To: Jim Lin <jilin@nvidia.com>
Cc: mathias.nyman@intel.com, thierry.reding@gmail.com,
jonathanh@nvidia.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
Petlozu Pravareshwar <petlozup@nvidia.com>,
JC Kuo <jckuo@nvidia.com>
Subject: Re: [PATCH v5 3/3] xhci: tegra: USB2 pad power controls
Date: Thu, 27 Oct 2022 16:00:17 +0200 [thread overview]
Message-ID: <Y1qO8cN4+kJVk2f5@kroah.com> (raw)
In-Reply-To: <20221027133127.27592-4-jilin@nvidia.com>
On Thu, Oct 27, 2022 at 09:31:27PM +0800, Jim Lin wrote:
> Program USB2 pad PD controls during port connect/disconnect, port
> suspend/resume, and test mode, to reduce power consumption on
> disconnect or suspend.
>
> Signed-off-by: Petlozu Pravareshwar <petlozup@nvidia.com>
> Signed-off-by: JC Kuo <jckuo@nvidia.com>
> Signed-off-by: Jim Lin <jilin@nvidia.com>
Who is the author here? These do not seem to be in the correct order if
you are the author, right?
>
> ---
> v2: Fix issue that wrong tegra->phys[] may be accessed on tegra124
> v3: No change on copyright
> v4: Remove hcd_to_tegra_xusb() function which is used only once.
> v5: Update .hub_control in tegra_xhci_overrides (xhci-tegra.c)
> Invoke xhci_hub_control() directly (xhci-tegra.c)
>
> drivers/usb/host/xhci-tegra.c | 131 +++++++++++++++++++++++++++++++++-
> 1 file changed, 130 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/usb/host/xhci-tegra.c b/drivers/usb/host/xhci-tegra.c
> index c8af2cd2216d..f685bb7459ba 100644
> --- a/drivers/usb/host/xhci-tegra.c
> +++ b/drivers/usb/host/xhci-tegra.c
> @@ -189,6 +189,13 @@ struct tegra_xusb_context_soc {
> } fpci;
> };
>
> +enum tegra_xhci_phy_type {
> + USB3_PHY,
> + USB2_PHY,
> + HSIC_PHY,
> + MAX_PHY_TYPES,
> +};
> +
> struct tegra_xusb_soc {
> const char *firmware;
> const char * const *supply_names;
> @@ -274,6 +281,7 @@ struct tegra_xusb {
>
> bool suspended;
> struct tegra_xusb_context context;
> + u32 enable_utmi_pad_after_lp0_exit;
This is a bitfield, how do we know it will fit in a u32? What is the
range you are putting in here?
thanks,
greg k-h
next prev parent reply other threads:[~2022-10-27 14:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 13:31 [PATCH v5 0/3] " Jim Lin
2022-10-27 13:31 ` [PATCH v5 1/3] xhci: hub: export symbol on xhci_hub_control Jim Lin
2022-10-27 13:58 ` Greg KH
2022-10-28 5:36 ` Jim Lin
2022-10-28 6:04 ` gregkh
2022-10-28 9:50 ` Thierry Reding
2022-10-28 10:37 ` gregkh
2022-10-28 11:08 ` Thierry Reding
2022-10-27 13:31 ` [PATCH v5 2/3] xhci: Add hub_control to xhci_driver_overrides Jim Lin
2022-10-27 13:31 ` [PATCH v5 3/3] xhci: tegra: USB2 pad power controls Jim Lin
2022-10-27 14:00 ` Greg KH [this message]
2022-10-28 3:11 ` Jim Lin
2022-10-28 6:07 ` gregkh
2022-10-28 11:03 ` Thierry Reding
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=Y1qO8cN4+kJVk2f5@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jckuo@nvidia.com \
--cc=jilin@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=petlozup@nvidia.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®