From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: "Christian A. Ehrhardt" <lk@c--e.de>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Anurag Bijea <icaliberdev@gmail.com>,
Christian Heusel <christian@heusel.eu>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Jameson Thies <jthies@google.com>,
Abhishek Pandit-Subedi <abhishekpandit@chromium.org>
Subject: Re: [PATCH v4] usb: typec: ucsi: Fix busy loop on ASUS VivoBooks
Date: Mon, 9 Sep 2024 12:33:14 +0300 [thread overview]
Message-ID: <Zt7A2lcW9v3ItKGm@kuha.fi.intel.com> (raw)
In-Reply-To: <20240906065853.637205-1-lk@c--e.de>
On Fri, Sep 06, 2024 at 08:58:53AM +0200, Christian A. Ehrhardt wrote:
> If the busy indicator is set, all other fields in CCI should be
> clear according to the spec. However, some UCSI implementations do
> not follow this rule and report bogus data in CCI along with the
> busy indicator. Ignore the contents of CCI if the busy indicator is
> set.
>
> If a command timeout is hit it is possible that the EVENT_PENDING
> bit is cleared while connector work is still scheduled which can
> cause the EVENT_PENDING bit to go out of sync with scheduled connector
> work. Check and set the EVENT_PENDING bit on entry to
> ucsi_handle_connector_change() to fix this.
>
> Finally, check UCSI_CCI_BUSY before the return code of ->sync_control.
> This ensures that the command is cancelled even if ->sync_control
> returns an error (most likely -ETIMEDOUT).
>
> Reported-by: Anurag Bijea <icaliberdev@gmail.com>
> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=219108
> Bisected-by: Christian Heusel <christian@heusel.eu>
> Tested-by: Anurag Bijea <icaliberdev@gmail.com>
> Fixes: de52aca4d9d5 ("usb: typec: ucsi: Never send a lone connector change ack")
> Cc: stable@vger.kernel.org
> Signed-off-by: Christian A. Ehrhardt <lk@c--e.de>
Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> ---
> drivers/usb/typec/ucsi/ucsi.c | 18 ++++++++++++------
> 1 file changed, 12 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/usb/typec/ucsi/ucsi.c b/drivers/usb/typec/ucsi/ucsi.c
> index 4039851551c1..d6d61606bbcf 100644
> --- a/drivers/usb/typec/ucsi/ucsi.c
> +++ b/drivers/usb/typec/ucsi/ucsi.c
> @@ -38,6 +38,10 @@
>
> void ucsi_notify_common(struct ucsi *ucsi, u32 cci)
> {
> + /* Ignore bogus data in CCI if busy indicator is set. */
> + if (cci & UCSI_CCI_BUSY)
> + return;
> +
> if (UCSI_CCI_CONNECTOR(cci))
> ucsi_connector_change(ucsi, UCSI_CCI_CONNECTOR(cci));
>
> @@ -107,15 +111,13 @@ static int ucsi_run_command(struct ucsi *ucsi, u64 command, u32 *cci,
> size = clamp(size, 0, 16);
>
> ret = ucsi->ops->sync_control(ucsi, command);
> - if (ret)
> - return ret;
> -
> - ret = ucsi->ops->read_cci(ucsi, cci);
> - if (ret)
> - return ret;
> + if (ucsi->ops->read_cci(ucsi, cci))
> + return -EIO;
>
> if (*cci & UCSI_CCI_BUSY)
> return -EBUSY;
> + if (ret)
> + return ret;
>
> if (!(*cci & UCSI_CCI_COMMAND_COMPLETE))
> return -EIO;
> @@ -1249,6 +1251,10 @@ static void ucsi_handle_connector_change(struct work_struct *work)
>
> mutex_lock(&con->lock);
>
> + if (!test_and_set_bit(EVENT_PENDING, &ucsi->flags))
> + dev_err_once(ucsi->dev, "%s entered without EVENT_PENDING\n",
> + __func__);
> +
> command = UCSI_GET_CONNECTOR_STATUS | UCSI_CONNECTOR_NUMBER(con->num);
>
> ret = ucsi_send_command_common(ucsi, command, &con->status,
> --
> 2.43.0
--
heikki
next prev parent reply other threads:[~2024-09-09 9:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 6:58 [PATCH v4] usb: typec: ucsi: Fix busy loop on ASUS VivoBooks Christian A. Ehrhardt
2024-09-09 9:33 ` Heikki Krogerus [this message]
2024-09-11 13:37 ` Greg Kroah-Hartman
2024-09-12 6:08 ` Christian A. Ehrhardt
2024-09-12 6:21 ` Dmitry Baryshkov
2024-09-12 6:53 ` Greg Kroah-Hartman
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=Zt7A2lcW9v3ItKGm@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=abhishekpandit@chromium.org \
--cc=christian@heusel.eu \
--cc=dmitry.baryshkov@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=icaliberdev@gmail.com \
--cc=jthies@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lk@c--e.de \
/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