linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Radu Vele <raduvele@google.com>
To: Tzung-Bi Shih <tzungbi@kernel.org>
Cc: Benson Leung <bleung@chromium.org>,
	 Abhishek Pandit-Subedi <abhishekpandit@chromium.org>,
	Jameson Thies <jthies@google.com>,
	 Andrei Kuchynski <akuchynski@chromium.org>,
	chrome-platform@lists.linux.dev,  linux-kernel@vger.kernel.org
Subject: Re: (subset) [PATCH v2 1/2] platform/chrome: cros_ec_typec: Add role swap ops
Date: Mon, 14 Jul 2025 11:41:14 +0200	[thread overview]
Message-ID: <CACKy9TKdJ=2HBwxJ5AnMCm6xHA1fxtkv-Zqn=Xr4xt-7P0Pn+w@mail.gmail.com> (raw)
In-Reply-To: <aHCO3ZqIFYJu2YTn@google.com>

On Fri, Jul 11, 2025 at 6:11 AM Tzung-Bi Shih <tzungbi@kernel.org> wrote:
>
> On Fri, Jul 11, 2025 at 12:35:01AM +0000, Radu Vele wrote:
> > Add the pr_set and dr_set typec_operations to registered typec ports.
> > This enables sysfs to control power and data role when the port is
> > capable of doing so.
> >
> > [...]
>
> Applied to
>
>     https://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git for-next
>
> [1/2] platform/chrome: cros_ec_typec: Add role swap ops
>       commit: ab229c2b72c35739e8ffb70af11190ff40f38701
>
> Thanks!

Thanks, please note that in case of the power role swap I started a discussion
with the EC team to verify the assumption we introduce here (the resp.role
populated by `cros_ec_cmd` should be equal to the target role if the operation
is successful). During testing I saw that the `resp.role` was not equal
to the target role but the role swap operation was successful (I
verified in sysfs
that the power role is the expected one).

In case they advise that our assumption is not correct we should remove the
assert resp.role == target_role for the power role.

      reply	other threads:[~2025-07-14  9:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-11  0:35 [PATCH v2 1/2] platform/chrome: cros_ec_typec: Add role swap ops Radu Vele
2025-07-11  0:35 ` [PATCH v2 2/2] platform/chrome: cros_ec_typec: Add lock per-port Radu Vele
2025-07-11  4:11   ` Tzung-Bi Shih
2025-07-14  8:32     ` Radu Vele
2025-07-15  6:07       ` Tzung-Bi Shih
2025-07-16 11:39         ` Radu Vele
2025-07-17  7:46           ` Tzung-Bi Shih
2025-07-11  4:11 ` (subset) [PATCH v2 1/2] platform/chrome: cros_ec_typec: Add role swap ops Tzung-Bi Shih
2025-07-14  9:41   ` Radu Vele [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='CACKy9TKdJ=2HBwxJ5AnMCm6xHA1fxtkv-Zqn=Xr4xt-7P0Pn+w@mail.gmail.com' \
    --to=raduvele@google.com \
    --cc=abhishekpandit@chromium.org \
    --cc=akuchynski@chromium.org \
    --cc=bleung@chromium.org \
    --cc=chrome-platform@lists.linux.dev \
    --cc=jthies@google.com \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).