From: Jon Hunter <jonathanh@nvidia.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Jameson Thies <jthies@google.com>,
heikki.krogerus@linux.intel.com, linux-usb@vger.kernel.org,
pmalani@chromium.org, bleung@google.com,
abhishekpandit@chromium.org, andersson@kernel.org,
fabrice.gasnier@foss.st.com, gregkh@linuxfoundation.org,
hdegoede@redhat.com, neil.armstrong@linaro.org,
rajaram.regupathy@intel.com, saranya.gopal@intel.com,
linux-kernel@vger.kernel.org, Benson Leung <bleung@chromium.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH v5 4/4] usb: typec: ucsi: Always set number of alternate modes
Date: Mon, 24 Jun 2024 16:52:53 +0100 [thread overview]
Message-ID: <bc9cd446-5e19-41c4-a316-9eb362f2d190@nvidia.com> (raw)
In-Reply-To: <CAA8EJprxHq65mAU6a9iGD6Yus-VB2x3WP5Z8JWN1oUwn+zQDfg@mail.gmail.com>
On 24/06/2024 15:33, Dmitry Baryshkov wrote:
> On Mon, 24 Jun 2024 at 16:42, Jon Hunter <jonathanh@nvidia.com> wrote:
>>
>>
>> On 24/06/2024 13:51, Jon Hunter wrote:
>>> Hi Jameson,
>>>
>>> On 10/05/2024 21:12, Jameson Thies wrote:
>>>> Providing the number of known alternate modes allows user space to
>>>> determine when device registration has completed. Always register a
>>>> number of known alternate modes for the partner and cable plug, even
>>>> when the number of supported alternate modes is 0.
>>>>
>>>> Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
>>>> Reviewed-by: Benson Leung <bleung@chromium.org>
>>>> Signed-off-by: Jameson Thies <jthies@google.com>
>>>> ---
>>>> Changes in V5:
>>>> - None.
>>>>
>>>> Changes in V4:
>>>> - None.
>>>>
>>>> Changes in V3:
>>>> - None.
>>>>
>>>> Changes in V2:
>>>> - None.
>>>>
>>>> drivers/usb/typec/ucsi/ucsi.c | 14 +++++++++++---
>>>> 1 file changed, 11 insertions(+), 3 deletions(-)
>>>>
>>>> diff --git a/drivers/usb/typec/ucsi/ucsi.c
>>>> b/drivers/usb/typec/ucsi/ucsi.c
>>>> index bb6e57064513d..52a14bfe4107e 100644
>>>> --- a/drivers/usb/typec/ucsi/ucsi.c
>>>> +++ b/drivers/usb/typec/ucsi/ucsi.c
>>>> @@ -812,10 +812,11 @@ static int ucsi_check_altmodes(struct
>>>> ucsi_connector *con)
>>>> /* Ignoring the errors in this case. */
>>>> if (con->partner_altmode[0]) {
>>>> num_partner_am = ucsi_get_num_altmode(con->partner_altmode);
>>>> - if (num_partner_am > 0)
>>>> - typec_partner_set_num_altmodes(con->partner,
>>>> num_partner_am);
>>>> + typec_partner_set_num_altmodes(con->partner, num_partner_am);
>>>> ucsi_altmode_update_active(con);
>>>> return 0;
>>>> + } else {
>>>> + typec_partner_set_num_altmodes(con->partner, 0);
>>>> }
>>>> return ret;
>>>> @@ -1138,7 +1139,7 @@ static int ucsi_check_connection(struct
>>>> ucsi_connector *con)
>>>> static int ucsi_check_cable(struct ucsi_connector *con)
>>>> {
>>>> u64 command;
>>>> - int ret;
>>>> + int ret, num_plug_am;
>>>> if (con->cable)
>>>> return 0;
>>>> @@ -1172,6 +1173,13 @@ static int ucsi_check_cable(struct
>>>> ucsi_connector *con)
>>>> return ret;
>>>> }
>>>> + if (con->plug_altmode[0]) {
>>>> + num_plug_am = ucsi_get_num_altmode(con->plug_altmode);
>>>> + typec_plug_set_num_altmodes(con->plug, num_plug_am);
>>>> + } else {
>>>> + typec_plug_set_num_altmodes(con->plug, 0);
>>>> + }
>>>> +
>>>> return 0;
>>>> }
Looking at this some more, the plug is only registered in
ucsi_check_cable() if UCSI_CAP_ALT_MODE_DETAILS is specified
for the Type C controller. The Cypress CCG explicitly clears
this flag.
The following will only call typec_plug_set_num_altmodes()
if the call to ucsi_register_plug() is successful ...
diff --git a/drivers/usb/typec/ucsi/ucsi.c b/drivers/usb/typec/ucsi/ucsi.c
index 134ef4e17d85..e268af88a7d2 100644
--- a/drivers/usb/typec/ucsi/ucsi.c
+++ b/drivers/usb/typec/ucsi/ucsi.c
@@ -1176,13 +1176,13 @@ static int ucsi_check_cable(struct ucsi_connector *con)
ret = ucsi_register_altmodes(con, UCSI_RECIPIENT_SOP_P);
if (ret < 0)
return ret;
- }
- if (con->plug_altmode[0]) {
- num_plug_am = ucsi_get_num_altmode(con->plug_altmode);
- typec_plug_set_num_altmodes(con->plug, num_plug_am);
- } else {
- typec_plug_set_num_altmodes(con->plug, 0);
+ if (con->plug_altmode[0]) {
+ num_plug_am = ucsi_get_num_altmode(con->plug_altmode);
+ typec_plug_set_num_altmodes(con->plug, num_plug_am);
+ } else {
+ typec_plug_set_num_altmodes(con->plug, 0);
+ }
}
return 0;
>> It is crashing because 'con->plug' is not initialised when
>> typec_plug_set_num_altmodes() is called. Do we need to add a check to
>> see if 'con->plug' is valid in ucsi_check_cable()?
>
> Yes. Either of con->calbe and con->plug can be NULL.
Thanks for confirming.
Jon
--
nvpublic
next prev parent reply other threads:[~2024-06-24 15:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 20:12 [PATCH v5 0/4] usb: typec: ucsi: Update UCSI alternate mode Jameson Thies
2024-05-10 20:12 ` [PATCH v5 1/4] usb: typec: ucsi: Fix null pointer dereference in trace Jameson Thies
2024-05-31 19:40 ` Dmitry Baryshkov
2024-05-10 20:12 ` [PATCH v5 2/4] usb: typec: Update sysfs when setting ops Jameson Thies
2024-05-31 19:41 ` Dmitry Baryshkov
2024-05-10 20:12 ` [PATCH v5 3/4] usb: typec: ucsi: Delay alternate mode discovery Jameson Thies
2024-05-31 19:42 ` Dmitry Baryshkov
2024-05-10 20:12 ` [PATCH v5 4/4] usb: typec: ucsi: Always set number of alternate modes Jameson Thies
2024-05-31 19:43 ` Dmitry Baryshkov
2024-06-24 12:51 ` Jon Hunter
2024-06-24 13:42 ` Jon Hunter
2024-06-24 14:33 ` Dmitry Baryshkov
2024-06-24 15:52 ` Jon Hunter [this message]
2024-06-24 16:32 ` Jameson Thies
2024-05-31 18:14 ` [PATCH v5 0/4] usb: typec: ucsi: Update UCSI alternate mode Jameson Thies
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=bc9cd446-5e19-41c4-a316-9eb362f2d190@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=abhishekpandit@chromium.org \
--cc=andersson@kernel.org \
--cc=bleung@chromium.org \
--cc=bleung@google.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=fabrice.gasnier@foss.st.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=jthies@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=pmalani@chromium.org \
--cc=rajaram.regupathy@intel.com \
--cc=saranya.gopal@intel.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