From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Andrei Kuchynski <akuchynski@chromium.org>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Abhishek Pandit-Subedi <abhishekpandit@chromium.org>,
Benson Leung <bleung@chromium.org>,
Jameson Thies <jthies@google.com>,
Tzung-Bi Shih <tzungbi@kernel.org>,
linux-usb@vger.kernel.org, chrome-platform@lists.linux.dev,
Guenter Roeck <groeck@chromium.org>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
"Christian A. Ehrhardt" <lk@c--e.de>,
Venkat Jayaraman <venkat.jayaraman@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/5] usb: typec: Add mode_control field to port property
Date: Wed, 10 Sep 2025 15:30:05 +0200 [thread overview]
Message-ID: <2025091018-slather-dispose-015d@gregkh> (raw)
In-Reply-To: <20250905142206.4105351-2-akuchynski@chromium.org>
On Fri, Sep 05, 2025 at 02:22:02PM +0000, Andrei Kuchynski wrote:
> This new field in the port properties dictates whether the Platform Policy
> Manager (PPM) allows the OS Policy Manager (OPM) to change the currently
> active, negotiated alternate mode.
>
> Signed-off-by: Andrei Kuchynski <akuchynski@chromium.org>
> ---
> drivers/usb/typec/class.c | 9 ++++++---
> drivers/usb/typec/class.h | 2 ++
> include/linux/usb/typec.h | 2 ++
> 3 files changed, 10 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/usb/typec/class.c b/drivers/usb/typec/class.c
> index 67a533e35150..9f86605ce125 100644
> --- a/drivers/usb/typec/class.c
> +++ b/drivers/usb/typec/class.c
> @@ -457,11 +457,13 @@ static umode_t typec_altmode_attr_is_visible(struct kobject *kobj,
> struct attribute *attr, int n)
> {
> struct typec_altmode *adev = to_typec_altmode(kobj_to_dev(kobj));
> + struct typec_port *port = typec_altmode2port(adev);
>
> if (attr == &dev_attr_active.attr)
> - if (!is_typec_port(adev->dev.parent) &&
> - (!adev->ops || !adev->ops->activate))
> - return 0444;
> + if (!is_typec_port(adev->dev.parent)) {
> + if (!port->mode_control || !adev->ops || !adev->ops->activate)
> + return 0444;
> + }
>
> return attr->mode;
> }
> @@ -2681,6 +2683,7 @@ struct typec_port *typec_register_port(struct device *parent,
> }
>
> port->pd = cap->pd;
> + port->mode_control = !cap->no_mode_control;
>
> ret = device_add(&port->dev);
> if (ret) {
> diff --git a/drivers/usb/typec/class.h b/drivers/usb/typec/class.h
> index db2fe96c48ff..c53a04b9dc75 100644
> --- a/drivers/usb/typec/class.h
> +++ b/drivers/usb/typec/class.h
> @@ -80,6 +80,8 @@ struct typec_port {
> */
> struct device *usb2_dev;
> struct device *usb3_dev;
> +
> + bool mode_control;
Shouldn't this go up higher in this structure, to avoid the hole you
created, and to take advantage of the existing hole? Perhaps after
orientation?
thanks,
greg k-h
next prev parent reply other threads:[~2025-09-10 13:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 14:22 [PATCH v3 0/5] USB Type-C alternate mode priorities Andrei Kuchynski
2025-09-05 14:22 ` [PATCH v3 1/5] usb: typec: Add mode_control field to port property Andrei Kuchynski
2025-09-09 8:47 ` Heikki Krogerus
2025-09-10 13:30 ` Greg Kroah-Hartman [this message]
2025-09-10 19:34 ` Andrei Kuchynski
2025-09-05 14:22 ` [PATCH v3 2/5] platform/chrome: cros_ec_typec: Set no_mode_control flag Andrei Kuchynski
2025-09-08 3:57 ` Tzung-Bi Shih
2025-09-05 14:22 ` [PATCH v3 3/5] usb: typec: ucsi: " Andrei Kuchynski
2025-09-09 9:07 ` Heikki Krogerus
2025-09-09 9:22 ` Andrei Kuchynski
2025-09-10 19:36 ` Andrei Kuchynski
2025-09-05 14:22 ` [PATCH v3 4/5] usb: typec: Implement alternate mode priority handling Andrei Kuchynski
2025-09-09 8:50 ` Heikki Krogerus
2025-09-10 13:31 ` Greg Kroah-Hartman
2025-09-10 19:35 ` Andrei Kuchynski
2025-09-11 5:07 ` Greg Kroah-Hartman
2025-09-11 8:46 ` Andrei Kuchynski
2025-09-11 10:41 ` Greg Kroah-Hartman
2025-09-11 13:11 ` Andrei Kuchynski
2025-09-05 14:22 ` [PATCH v3 5/5] usb: typec: Expose alternate mode priority via sysfs Andrei Kuchynski
2025-09-10 13:27 ` Greg Kroah-Hartman
2025-09-10 19:34 ` Andrei Kuchynski
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=2025091018-slather-dispose-015d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=abhishekpandit@chromium.org \
--cc=akuchynski@chromium.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=groeck@chromium.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=jthies@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lk@c--e.de \
--cc=tzungbi@kernel.org \
--cc=venkat.jayaraman@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