From: Vinod Koul <vkoul@kernel.org>
To: Wayne Chang <waynec@nvidia.com>
Cc: jonathanh@nvidia.com, thierry.reding@gmail.com, jckuo@nvidia.com,
kishon@kernel.org, gregkh@linuxfoundation.org,
linux-phy@lists.infradead.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2 1/2] phy: tegra: xusb: Add API to retrieve the port number of phy
Date: Fri, 5 Apr 2024 22:29:10 +0530 [thread overview]
Message-ID: <ZhAt3kPzn212vAH4@matsya> (raw)
In-Reply-To: <20240307030328.1487748-2-waynec@nvidia.com>
On 07-03-24, 11:03, Wayne Chang wrote:
> This patch introduces a new API, tegra_xusb_padctl_get_port_number,
> to the Tegra XUSB Pad Controller driver. This API is used to identify
> the USB port that is associated with a given PHY.
>
> The function takes a PHY pointer for either a USB2 PHY or USB3 PHY as input
> and returns the corresponding port number. If the PHY pointer is invalid,
> it returns -ENODEV.
Acked-by: Vinod Koul <vkoul@kernel.org>
--
~Vinod
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vkoul@kernel.org>
To: Wayne Chang <waynec@nvidia.com>
Cc: jonathanh@nvidia.com, thierry.reding@gmail.com, jckuo@nvidia.com,
kishon@kernel.org, gregkh@linuxfoundation.org,
linux-phy@lists.infradead.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2 1/2] phy: tegra: xusb: Add API to retrieve the port number of phy
Date: Fri, 5 Apr 2024 22:29:10 +0530 [thread overview]
Message-ID: <ZhAt3kPzn212vAH4@matsya> (raw)
In-Reply-To: <20240307030328.1487748-2-waynec@nvidia.com>
On 07-03-24, 11:03, Wayne Chang wrote:
> This patch introduces a new API, tegra_xusb_padctl_get_port_number,
> to the Tegra XUSB Pad Controller driver. This API is used to identify
> the USB port that is associated with a given PHY.
>
> The function takes a PHY pointer for either a USB2 PHY or USB3 PHY as input
> and returns the corresponding port number. If the PHY pointer is invalid,
> it returns -ENODEV.
Acked-by: Vinod Koul <vkoul@kernel.org>
--
~Vinod
next prev parent reply other threads:[~2024-04-05 16:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 3:03 [PATCH v2 0/2] Fix incorrect USB3 phy parsing in tegra-xudc Wayne Chang
2024-03-07 3:03 ` Wayne Chang
2024-03-07 3:03 ` [PATCH v2 1/2] phy: tegra: xusb: Add API to retrieve the port number of phy Wayne Chang
2024-03-07 3:03 ` Wayne Chang
2024-03-07 13:43 ` Jon Hunter
2024-03-07 13:43 ` Jon Hunter
2024-04-05 16:59 ` Vinod Koul [this message]
2024-04-05 16:59 ` Vinod Koul
2024-03-07 3:03 ` [PATCH v2 2/2] usb: gadget: tegra-xudc: Fix USB3 PHY retrieval logic Wayne Chang
2024-03-07 3:03 ` Wayne Chang
2024-03-07 13:43 ` Jon Hunter
2024-03-07 13:43 ` 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=ZhAt3kPzn212vAH4@matsya \
--to=vkoul@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jckuo@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=kishon@kernel.org \
--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=stable@vger.kernel.org \
--cc=thierry.reding@gmail.com \
--cc=waynec@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.