From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: amitsd@google.com
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Badhri Jagan Sridharan <badhri@google.com>,
RD Babiera <rdbabiera@google.com>, Kyle Tso <kyletso@google.com>,
Sebastian Reichel <sebastian.reichel@collabora.com>,
Xu Yang <xu.yang_2@nxp.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] usb: typec: tcpm: fix state transition for SNK_WAIT_CAPABILITIES state in run_state_machine()
Date: Wed, 12 Mar 2025 13:38:20 +0200 [thread overview]
Message-ID: <Z9FyLNcHHczSvpAq@kuha.fi.intel.com> (raw)
In-Reply-To: <20250310-fix-snk-wait-timeout-v6-14-rc6-v1-1-5db14475798f@google.com>
On Mon, Mar 10, 2025 at 07:19:07PM -0700, Amit Sunil Dhamne via B4 Relay wrote:
> From: Amit Sunil Dhamne <amitsd@google.com>
>
> A subtle error got introduced while manually fixing merge conflict in
> tcpm.c for commit 85c4efbe6088 ("Merge v6.12-rc6 into usb-next"). As a
> result of this error, the next state is unconditionally set to
> SNK_WAIT_CAPABILITIES_TIMEOUT while handling SNK_WAIT_CAPABILITIES state
> in run_state_machine(...).
>
> Fix this by setting new state of TCPM state machine to `upcoming_state`
> (that is set to different values based on conditions).
>
> Cc: stable@vger.kernel.org
> Fixes: 85c4efbe60888 ("Merge v6.12-rc6 into usb-next")
> Signed-off-by: Amit Sunil Dhamne <amitsd@google.com>
> Reviewed-by: Badhri Jagan Sridharan <badhri@google.com>
Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> ---
> drivers/usb/typec/tcpm/tcpm.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/usb/typec/tcpm/tcpm.c b/drivers/usb/typec/tcpm/tcpm.c
> index 47be450d2be352698e9dee2e283664cd4db8081b..758933d4ac9e4e55d45940b068f3c416e7e51ee8 100644
> --- a/drivers/usb/typec/tcpm/tcpm.c
> +++ b/drivers/usb/typec/tcpm/tcpm.c
> @@ -5117,16 +5117,16 @@ static void run_state_machine(struct tcpm_port *port)
> */
> if (port->vbus_never_low) {
> port->vbus_never_low = false;
> - tcpm_set_state(port, SNK_SOFT_RESET,
> - port->timings.sink_wait_cap_time);
> + upcoming_state = SNK_SOFT_RESET;
> } else {
> if (!port->self_powered)
> upcoming_state = SNK_WAIT_CAPABILITIES_TIMEOUT;
> else
> upcoming_state = hard_reset_state(port);
> - tcpm_set_state(port, SNK_WAIT_CAPABILITIES_TIMEOUT,
> - port->timings.sink_wait_cap_time);
> }
> +
> + tcpm_set_state(port, upcoming_state,
> + port->timings.sink_wait_cap_time);
> break;
> case SNK_WAIT_CAPABILITIES_TIMEOUT:
> /*
>
> ---
> base-commit: 5c8c229261f14159b54b9a32f12e5fa89d88b905
> change-id: 20250310-fix-snk-wait-timeout-v6-14-rc6-7b4d9fb9bc99
>
> Best regards,
> --
> Amit Sunil Dhamne <amitsd@google.com>
>
--
heikki
prev parent reply other threads:[~2025-03-12 11:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 2:19 Amit Sunil Dhamne via B4 Relay
2025-03-12 11:38 ` Heikki Krogerus [this message]
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=Z9FyLNcHHczSvpAq@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=amitsd@google.com \
--cc=badhri@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=kyletso@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rdbabiera@google.com \
--cc=sebastian.reichel@collabora.com \
--cc=stable@vger.kernel.org \
--cc=xu.yang_2@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®