From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Cosmo Chou <chou.cosmo@gmail.com>
Cc: badhri@google.com, gregkh@linuxfoundation.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
cosmo.chou@quantatw.com
Subject: Re: [PATCH v2] usb: typec: tcpm: Use configured PD revision for negotiation
Date: Tue, 13 May 2025 16:39:05 +0300 [thread overview]
Message-ID: <aCNLeX1k34BSgPOV@kuha.fi.intel.com> (raw)
In-Reply-To: <20250513130834.1612602-1-chou.cosmo@gmail.com>
On Tue, May 13, 2025 at 09:08:34PM +0800, Cosmo Chou wrote:
> Initialize negotiated_rev and negotiated_rev_prime based on the port's
> configured PD revision (rev_major) rather than always defaulting to
> PD_MAX_REV. This ensures ports start PD communication using their
> appropriate revision level.
>
> This allows proper communication with devices that require specific
> PD revision levels, especially for the hardware designed for PD 1.0
> or 2.0 specifications.
>
> Signed-off-by: Cosmo Chou <chou.cosmo@gmail.com>
> ---
> Change log:
>
> v2:
> - Add PD_CAP_REVXX macros and use switch-case for better readability.
>
> ---
> drivers/usb/typec/tcpm/tcpm.c | 29 +++++++++++++++++++++++++----
> 1 file changed, 25 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/usb/typec/tcpm/tcpm.c b/drivers/usb/typec/tcpm/tcpm.c
> index 8adf6f954633..48e9cfc2b49a 100644
> --- a/drivers/usb/typec/tcpm/tcpm.c
> +++ b/drivers/usb/typec/tcpm/tcpm.c
> @@ -313,6 +313,10 @@ struct pd_data {
> unsigned int operating_snk_mw;
> };
>
> +#define PD_CAP_REV10 0x1
> +#define PD_CAP_REV20 0x2
> +#define PD_CAP_REV30 0x3
> +
> struct pd_revision_info {
> u8 rev_major;
> u8 rev_minor;
> @@ -4665,6 +4669,25 @@ static void tcpm_set_initial_svdm_version(struct tcpm_port *port)
> }
> }
>
> +static void tcpm_set_initial_negotiated_rev(struct tcpm_port *port)
> +{
> + switch (port->pd_rev.rev_major) {
> + case PD_CAP_REV10:
> + port->negotiated_rev = PD_REV10;
> + break;
> + case PD_CAP_REV20:
> + port->negotiated_rev = PD_REV20;
> + break;
> + case PD_CAP_REV30:
> + port->negotiated_rev = PD_REV30;
> + break;
> + default:
> + port->negotiated_rev = PD_MAX_REV;
> + break;
> + }
> + port->negotiated_rev_prime = port->negotiated_rev;
> +}
Do we need this? Couldn't you just add one to rev_major?
port->negotiated_rev = port->pd_rev.rev_major + 1;
port->negotiated_rev_prime = port->pd_rev.rev_major + 1;
Or am I missing something?
thanks,
> static void run_state_machine(struct tcpm_port *port)
> {
> int ret;
> @@ -4782,8 +4805,7 @@ static void run_state_machine(struct tcpm_port *port)
> typec_set_pwr_opmode(port->typec_port, opmode);
> port->pwr_opmode = TYPEC_PWR_MODE_USB;
> port->caps_count = 0;
> - port->negotiated_rev = PD_MAX_REV;
> - port->negotiated_rev_prime = PD_MAX_REV;
> + tcpm_set_initial_negotiated_rev(port);
> port->message_id = 0;
> port->message_id_prime = 0;
> port->rx_msgid = -1;
> @@ -5048,8 +5070,7 @@ static void run_state_machine(struct tcpm_port *port)
> port->cc2 : port->cc1);
> typec_set_pwr_opmode(port->typec_port, opmode);
> port->pwr_opmode = TYPEC_PWR_MODE_USB;
> - port->negotiated_rev = PD_MAX_REV;
> - port->negotiated_rev_prime = PD_MAX_REV;
> + tcpm_set_initial_negotiated_rev(port);
> port->message_id = 0;
> port->message_id_prime = 0;
> port->rx_msgid = -1;
> --
> 2.43.0
--
heikki
next prev parent reply other threads:[~2025-05-13 13:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 13:08 [PATCH v2] usb: typec: tcpm: Use configured PD revision for negotiation Cosmo Chou
2025-05-13 13:39 ` Heikki Krogerus [this message]
2025-05-13 13:50 ` Heikki Krogerus
2025-05-13 14:14 ` Cosmo Chou
2025-05-14 8:12 ` Heikki Krogerus
2025-05-15 7:15 ` Amit Sunil Dhamne
2025-05-16 5:10 ` Badhri Jagan Sridharan
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=aCNLeX1k34BSgPOV@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=badhri@google.com \
--cc=chou.cosmo@gmail.com \
--cc=cosmo.chou@quantatw.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.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