From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Xu Yang <xu.yang_2@oss.nxp.com>
Cc: badhri@google.com, gregkh@linuxfoundation.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
imx@lists.linux.dev, jun.li@nxp.com,
RD Babiera <rdbabiera@google.com>
Subject: Re: [PATCH v2] usb: typec: tcpm: advance vdm_discovery_state on Discover Identity Not_Supported
Date: Tue, 22 Sep 2026 12:50:23 +0200 [thread overview]
Message-ID: <arJdb9kip_YCzjV2@black.igk.intel.com> (raw)
In-Reply-To: <20260916043957.3362995-1-xu.yang_2@oss.nxp.com>
+RD
On Wed, Sep 16, 2026 at 12:39:57PM +0800, Xu Yang wrote:
> From: Xu Yang <xu.yang_2@nxp.com>
>
> Commit Fixes: 205dc9cb39f5 ("usb: typec: tcpm: implement retry mechanism
> for Discover Identity VDMs") advances vdm_discovery_state to
> VDM_DISCOVERY_COMPLETE when a CMDT_RSP_NAK is received, but it does not
> advance the state when a non-modal port returns PD_CTRL_NOT_SUPP.
>
> This can re-arm another vdm_discovery_work if the port is going to
> respond with PD_CTRL_NOT_SUPP to the partner.
>
> tcpm_pd_handle_msg(port, PD_MSG_CTRL_NOT_SUPP, NONE_AMS);
> tcpm_queue_message();
> mod_tcpm_delayed_work();
> tcpm_state_machine_work()
> tcpm_send_queued_message() -> send PD_MSG_CTRL_NOT_SUPP
> run_state_machine()
> case SRC_READY:
> case SNK_READY:
> mod_vdm_discovery_delayed_work(port, 0);
>
> If both the port and its partner do not support modal operation, they
> will send DISCOVER_IDENTITY to each other infinitely.
>
> Advance vdm_discovery_state to VDM_DISCOVERY_COMPLETE in this path as
> well. In particular, update the state to VDM_DISCOVERY_COMPLETE if it comes
> from the port partner, and to VDM_DISCOVERY_CABLE_IDENT if it comes from a
> cable.
>
> Fixes: 205dc9cb39f5 ("usb: typec: tcpm: implement retry mechanism for Discover Identity VDMs")
> Signed-off-by: Xu Yang <xu.yang_2@nxp.com>
>
> ---
> Changes in v2:
> - cover a cable returns PD_CTRL_NOT_SUPP case reported by sashiko
> - kick off vdm_discovery work to continue working
> - correct previous wrong fix commit id
> ---
> drivers/usb/typec/tcpm/tcpm.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/drivers/usb/typec/tcpm/tcpm.c b/drivers/usb/typec/tcpm/tcpm.c
> index 2d6b14aa2085..5cea820e00c4 100644
> --- a/drivers/usb/typec/tcpm/tcpm.c
> +++ b/drivers/usb/typec/tcpm/tcpm.c
> @@ -3891,6 +3891,16 @@ static void tcpm_pd_ctrl_request(struct tcpm_port *port,
> case SRC_READY:
> case SNK_READY:
> if (port->vdm_state > VDM_STATE_READY) {
> + if (port->ams == DISCOVER_IDENTITY) {
> + if (rx_sop_type == TCPC_TX_SOP) {
> + tcpm_update_vdm_discovery_state(port,
> + VDM_DISCOVERY_COMPLETE);
> + } else if (rx_sop_type == TCPC_TX_SOP_PRIME) {
> + tcpm_update_vdm_discovery_state(port,
> + VDM_DISCOVERY_CABLE_IDENT);
> + mod_vdm_discovery_delayed_work(port, 0);
> + }
> + }
> port->vdm_state = VDM_STATE_DONE;
> if (tcpm_vdm_ams(port))
> tcpm_ams_finish(port);
> --
> 2.34.1
--
heikki
next prev parent reply other threads:[~2026-09-22 10:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 4:39 Xu Yang
2026-09-22 10:50 ` Heikki Krogerus [this message]
2026-09-24 17:34 ` RD Babiera
2026-09-28 12:58 ` Heikki Krogerus
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=arJdb9kip_YCzjV2@black.igk.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=badhri@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=imx@lists.linux.dev \
--cc=jun.li@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rdbabiera@google.com \
--cc=xu.yang_2@oss.nxp.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®