public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jim Lin <jilin@nvidia.com>
To: Jonathan Hunter <jonathanh@nvidia.com>
Cc: "linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
	"mathias.nyman@intel.com" <mathias.nyman@intel.com>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: [PATCH v3] xhci: tegra: USB2 pad power controls
Date: Mon, 17 Oct 2022 09:36:39 +0000	[thread overview]
Message-ID: <cf9b9c605ed06e59edd3ae5deba914cfbfa55be3.camel@nvidia.com> (raw)
In-Reply-To: <37b168f2-049c-c01f-9f60-c119fabf8606@nvidia.com>

On Wed, 2022-10-12 at 12:45 +0100, Jon Hunter wrote:
> On 12/10/2022 11:25, 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: Jim Lin <jilin@nvidia.com>
> > ---
> > v2: Fix issue that wrong tegra->phys[] may be accessed on tegra124
> > v3: No change on copyright
> > 
> >   drivers/usb/host/xhci-tegra.c | 139
> > +++++++++++++++++++++++++++++++++-
> >   1 file changed, 138 insertions(+), 1 deletion(-)
> > 
> > diff --git a/drivers/usb/host/xhci-tegra.c b/drivers/usb/host/xhci-
> > tegra.c
> > index c8af2cd2216d..996182a1959f 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,9 +281,17 @@ struct tegra_xusb {
> >   
> >   	bool suspended;
> >   	struct tegra_xusb_context context;
> > +	u32 enable_utmi_pad_after_lp0_exit;
> >   };
> >   
> >   static struct hc_driver __read_mostly tegra_xhci_hc_driver;
> > +static int (*original_xhci_hub_control)(struct usb_hcd *hcd, u16
> > typeReq, u16 wValue, u16 wIndex,
> > +	    char *buf, u16 wLength);
> 
> Is it better to add this function pointer to the tegra_xusb
> structure?
> 
> Jon
> 
Do you mean removing variable "original_xhci_hub_control" and save
function pointer to the tegra_xusb structure ?

But that doesn't look possible over here to point to tegra_xusb
structure and save pointer (to tegra_xhci_hc_driver.hub_control) into
it.

"
static int __init tegra_xusb_init(void)
{
	xhci_init_driver(&tegra_xhci_hc_driver, &tegra_xhci_overrides);

	return platform_driver_register(&tegra_xusb_driver);
}
module_init(tegra_xusb_init);
"

--nvpublic

  reply	other threads:[~2022-10-17  9:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-12 10:25 [PATCH v3] xhci: tegra: USB2 pad power controls Jim Lin
2022-10-12 11:18 ` Greg KH
2022-10-12 11:43   ` Jon Hunter
2022-10-14  9:41     ` Jim Lin
2022-10-12 11:45 ` Jon Hunter
2022-10-17  9:36   ` Jim Lin [this message]
2022-10-17 20:17     ` Jon Hunter
2022-10-18  3:20       ` 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=cf9b9c605ed06e59edd3ae5deba914cfbfa55be3.camel@nvidia.com \
    --to=jilin@nvidia.com \
    --cc=gregkh@linuxfoundation.org \
    --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=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