From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Abhishek Pandit-Subedi <abhishekpandit@chromium.org>
Cc: tzungbi@kernel.org, linux-usb@vger.kernel.org,
chrome-platform@lists.linux.dev, dmitry.baryshkov@linaro.org,
jthies@google.com, akuchynski@google.com, pmalani@chromium.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/7] usb: typec: Auto enter control for alternate modes
Date: Thu, 31 Oct 2024 16:33:04 +0200 [thread overview]
Message-ID: <ZyOVIKGlrlj7kc9-@kuha.fi.intel.com> (raw)
In-Reply-To: <20241030142833.v2.3.I439cffc7bf76d94f5850eb85980f1197c4f9154c@changeid>
On Wed, Oct 30, 2024 at 02:28:34PM -0700, Abhishek Pandit-Subedi wrote:
> Add controls for whether an alternate mode is automatically entered when
> a partner connects. The auto_enter control is only available on ports
> and applies immediately after a partner connects. The default behavior
> is to enable auto enter and drivers must explicitly disable it.
>
> Signed-off-by: Abhishek Pandit-Subedi <abhishekpandit@chromium.org>
> ---
>
> (no changes since v1)
>
> Documentation/ABI/testing/sysfs-bus-typec | 9 +++++++
> drivers/usb/typec/altmodes/displayport.c | 6 +++--
> drivers/usb/typec/altmodes/thunderbolt.c | 3 ++-
> drivers/usb/typec/class.c | 31 +++++++++++++++++++++++
> include/linux/usb/typec.h | 2 ++
> include/linux/usb/typec_altmode.h | 2 ++
> 6 files changed, 50 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/ABI/testing/sysfs-bus-typec b/Documentation/ABI/testing/sysfs-bus-typec
> index 205d9c91e2e1..f09d05727b82 100644
> --- a/Documentation/ABI/testing/sysfs-bus-typec
> +++ b/Documentation/ABI/testing/sysfs-bus-typec
> @@ -12,6 +12,15 @@ Description:
>
> Valid values are boolean.
>
> +What: /sys/bus/typec/devices/.../auto_enter
> +Date: September 2024
> +Contact: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> +Description:
> + Controls whether a mode will be automatically entered when a partner is
> + connected.
> +
> + This field is only valid and displayed on a port. Valid values are boolean.
So, why can't this be controlled with the "active" property of the
port altmode instead? That's why it's there.
Sorry if I missed something in v1 related to this question.
thanks,
--
heikki
next prev parent reply other threads:[~2024-10-31 14:33 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 21:28 [PATCH v2 0/7] Thunderbolt and DP altmode support for cros-ec-typec Abhishek Pandit-Subedi
2024-10-30 21:28 ` [PATCH v2 1/7] usb: typec: Add driver for Thunderbolt 3 Alternate Mode Abhishek Pandit-Subedi
2024-10-31 5:09 ` kernel test robot
2024-10-31 14:11 ` Heikki Krogerus
2024-10-31 23:02 ` Abhishek Pandit-Subedi
2024-11-01 13:16 ` Heikki Krogerus
2024-11-01 18:48 ` Abhishek Pandit-Subedi
2024-11-04 14:32 ` Heikki Krogerus
2024-11-07 19:21 ` Abhishek Pandit-Subedi
2024-10-30 21:28 ` [PATCH v2 2/7] usb: typec: Only use SVID for matching altmodes Abhishek Pandit-Subedi
2024-10-31 14:13 ` Heikki Krogerus
2024-10-30 21:28 ` [PATCH v2 3/7] usb: typec: Auto enter control for alternate modes Abhishek Pandit-Subedi
2024-10-31 14:33 ` Heikki Krogerus [this message]
2024-10-31 22:48 ` Abhishek Pandit-Subedi
2024-11-01 13:59 ` Heikki Krogerus
2024-11-01 16:53 ` Abhishek Pandit-Subedi
2024-11-04 14:14 ` Heikki Krogerus
2024-10-30 21:28 ` [PATCH v2 4/7] platform/chrome: cros_ec_typec: Update partner altmode active Abhishek Pandit-Subedi
2024-10-30 21:28 ` [PATCH v2 5/7] platform/chrome: cros_ec_typec: Displayport support Abhishek Pandit-Subedi
2024-10-31 17:48 ` kernel test robot
2024-10-31 18:54 ` Dmitry Baryshkov
2024-10-31 22:34 ` Abhishek Pandit-Subedi
2024-10-31 19:43 ` kernel test robot
2024-10-30 21:28 ` [PATCH v2 6/7] platform/chrome: cros_ec_typec: Thunderbolt support Abhishek Pandit-Subedi
2024-10-31 17:07 ` kernel test robot
2024-10-31 18:51 ` Dmitry Baryshkov
2024-10-31 22:23 ` Abhishek Pandit-Subedi
2024-10-30 21:28 ` [PATCH v2 7/7] platform/chrome: cros_ec_typec: Disable tbt auto_enter Abhishek Pandit-Subedi
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=ZyOVIKGlrlj7kc9-@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=abhishekpandit@chromium.org \
--cc=akuchynski@google.com \
--cc=chrome-platform@lists.linux.dev \
--cc=dmitry.baryshkov@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=jthies@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pmalani@chromium.org \
--cc=tzungbi@kernel.org \
/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