From: Tzung-Bi Shih <tzungbi@kernel.org>
To: Radu Vele <raduvele@google.com>
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: [PATCH v1 1/2] platform/chrome: cros_ec_typec: Add role swap ops
Date: Thu, 10 Jul 2025 04:06:07 +0000 [thread overview]
Message-ID: <aG88L7QXa5IU7zPE@google.com> (raw)
In-Reply-To: <20250709132232.2475172-1-raduvele@google.com>
On Wed, Jul 09, 2025 at 01:22:31PM +0000, Radu Vele wrote:
> +static int cros_typec_perform_role_swap(struct typec_port *tc_port, int target_role, u8 swap_type)
> +{
> [...]
> + switch (swap_type) {
> + case USB_PD_CTRL_SWAP_DATA:
> + role = (resp.role & PD_CTRL_RESP_ROLE_DATA) ? TYPEC_HOST :
> + TYPEC_DEVICE;
> + break;
> + case USB_PD_CTRL_SWAP_POWER:
> + role = (resp.role & PD_CTRL_RESP_ROLE_POWER) ? TYPEC_SOURCE :
> + TYPEC_SINK;
> + break;
> + default:
> + dev_warn(data->dev, "Unsupported role swap type %d", swap_type);
Append a newline at the end of message?
> + return -EOPNOTSUPP;
> + }
> +
> + if (role == target_role)
> + return 0;
> +
> + req.swap = swap_type;
> + ret = cros_ec_cmd(data->ec, data->pd_ctrl_ver, EC_CMD_USB_PD_CONTROL,
> + &req, sizeof(req), &resp, sizeof(resp));
> +
> + if (ret < 0)
> + return ret;
> +
> + switch (swap_type) {
> + case USB_PD_CTRL_SWAP_DATA:
> + typec_set_data_role(tc_port, resp.role & PD_CTRL_RESP_ROLE_DATA ?
> + TYPEC_HOST :
> + TYPEC_DEVICE);
To improve the readability a bit, how about re-use `role` variable here:
role = resp.role & ... ? ... : ...;
Also I'm wondering doesn't it need to assert
(resp.role & ... ? ... : ...) == target_role here? Otherwise, could it just
use `target_role` as the parameter for typec_set_data_role()?
> + break;
> + case USB_PD_CTRL_SWAP_POWER:
> + typec_set_pwr_role(tc_port, resp.role & PD_CTRL_RESP_ROLE_POWER ?
> + TYPEC_SOURCE :
> + TYPEC_SINK);
Similar here.
> + break;
> + }
It already checks in previous code block. Not sure if some checkers would
find the swtich-case block doesn't have a default clause. How about still
add a default case, and have a comment to remind that should never execute?
> static const struct typec_operations cros_typec_usb_mode_ops = {
> - .enter_usb_mode = cros_typec_enter_usb_mode
> + .enter_usb_mode = cros_typec_enter_usb_mode,
> + .dr_set = cros_typec_dr_swap,
> + .pr_set = cros_typec_pr_swap
Leave a comma "," at the end of line?
prev parent reply other threads:[~2025-07-10 4:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 13:22 [PATCH v1 1/2] platform/chrome: cros_ec_typec: Add role swap ops Radu Vele
2025-07-09 13:22 ` [PATCH v1 2/2] platform/chrome: cros_ec_typec: Add lock per-port Radu Vele
2025-07-09 18:54 ` Benson Leung
2025-07-10 4:06 ` Tzung-Bi Shih
2025-07-09 18:45 ` [PATCH v1 1/2] platform/chrome: cros_ec_typec: Add role swap ops Benson Leung
2025-07-10 4:06 ` Tzung-Bi Shih [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=aG88L7QXa5IU7zPE@google.com \
--to=tzungbi@kernel.org \
--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=raduvele@google.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