From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Anjelique Melendez <anjelique.melendez@oss.qualcomm.com>,
heikki.krogerus@linux.intel.com, gregkh@linuxfoundation.org
Cc: lumag@kernel.org, neil.armstrong@linaro.org,
johan+linaro@kernel.org, quic_bjorande@quicinc.com,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v4 2/2] usb: typec: ucsi_glink: Increase buffer size to support UCSI v2
Date: Thu, 25 Sep 2025 14:07:47 +0200 [thread overview]
Message-ID: <df671650-a5af-4453-a11d-e8e2a32bd1ab@oss.qualcomm.com> (raw)
In-Reply-To: <20250924232631.644234-3-anjelique.melendez@oss.qualcomm.com>
On 9/25/25 1:26 AM, Anjelique Melendez wrote:
> UCSI v2 specification has increased the MSG_IN and MSG_OUT size from
> 16 bytes to 256 bytes each for the message exchange between OPM and PPM
> This makes the total buffer size increase from 48 bytes to 528 bytes.
> Update the buffer size to support this increase.
>
> Signed-off-by: Anjelique Melendez <anjelique.melendez@oss.qualcomm.com>
> ---
[...]
> static int pmic_glink_ucsi_read(struct ucsi *__ucsi, unsigned int offset,
> @@ -131,18 +143,34 @@ static int pmic_glink_ucsi_read_message_in(struct ucsi *ucsi, void *val, size_t
> static int pmic_glink_ucsi_locked_write(struct pmic_glink_ucsi *ucsi, unsigned int offset,
> const void *val, size_t val_len)
> {
> - struct ucsi_write_buf_req_msg req = {};
> - unsigned long left;
> + struct ucsi_v2_write_buf_req_msg req = {};
> + unsigned long left, max_buf_len;
> + size_t req_len;
> int ret;
>
> + memset(&req, 0, sizeof(req));
= {} already zero-initializes the struct
> req.hdr.owner = PMIC_GLINK_OWNER_USBC;
> req.hdr.type = MSG_TYPE_REQ_RESP;
> req.hdr.opcode = UC_UCSI_WRITE_BUF_REQ;
> +
> + if (ucsi->ucsi->version >= UCSI_VERSION_2_0) {
> + req_len = sizeof(struct ucsi_v2_write_buf_req_msg);
> + max_buf_len = UCSI_BUF_V2_SIZE;
> + } else if (ucsi->ucsi->version) {
> + req_len = sizeof(struct ucsi_v1_write_buf_req_msg);
> + max_buf_len = UCSI_BUF_V1_SIZE;
> + } else {
> + return -EINVAL;
> + }
> +
> + if (offset + val_len > max_buf_len)
> + return -EINVAL;
> +
> memcpy(&req.buf[offset], val, val_len);
>
> reinit_completion(&ucsi->write_ack);
>
> - ret = pmic_glink_send(ucsi->client, &req, sizeof(req));
> + ret = pmic_glink_send(ucsi->client, &req, req_len);
This code keeps the 'reserved' field zeored out for v1, but it does so
in a fragile and implicit way :/
> if (ret < 0) {
> dev_err(ucsi->dev, "failed to send UCSI write request: %d\n", ret);
> return ret;
> @@ -216,12 +244,39 @@ static const struct ucsi_operations pmic_glink_ucsi_ops = {
>
> static void pmic_glink_ucsi_read_ack(struct pmic_glink_ucsi *ucsi, const void *data, int len)
> {
> - const struct ucsi_read_buf_resp_msg *resp = data;
> + u8 *buf = ((struct ucsi_v2_read_buf_resp_msg *)data)->buf;
> + u32 ret_code, max_len;
> + u32 buf_len = 0;
> +
> + if (ucsi->ucsi->version) {
> + if (ucsi->ucsi->version >= UCSI_VERSION_2_0)
> + buf_len = UCSI_BUF_V2_SIZE;
> + else
> + buf_len = UCSI_BUF_V1_SIZE;
> + } else if (!ucsi->ucsi_registered) {
> + /*
> + * If UCSI version is not known yet because device is not registered,
> + * choose buffer size which best fits incoming data
> + */
> + if (len > sizeof(struct pmic_glink_hdr) + UCSI_BUF_V2_SIZE)
> + buf_len = UCSI_BUF_V2_SIZE;
> + else
> + buf_len = UCSI_BUF_V1_SIZE;
> + }
>
> - if (resp->ret_code)
> + max_len = sizeof(struct pmic_glink_hdr) + buf_len + sizeof(u32);
> +
> + if (len > max_len)
> + return;
> +
> + if (buf_len > len - sizeof(struct pmic_glink_hdr) - sizeof(u32))
> + buf_len = len - sizeof(struct pmic_glink_hdr) - sizeof(u32);
Is this expected to happen?
Konrad
> +
> + memcpy(&ret_code, buf + buf_len, sizeof(u32));
> + if (ret_code)
> return;
>
> - memcpy(ucsi->read_buf, resp->buf, UCSI_BUF_SIZE);
> + memcpy(ucsi->read_buf, buf, buf_len);
> complete(&ucsi->read_ack);
> }
>
next prev parent reply other threads:[~2025-09-25 12:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 23:26 [PATCH v4 0/2] usb: typec: ucsi_glink: Add " Anjelique Melendez
2025-09-24 23:26 ` [PATCH v4 1/2] usb: typec: ucsi_glink: Update request/response buffers to be packed Anjelique Melendez
2025-09-24 23:26 ` [PATCH v4 2/2] usb: typec: ucsi_glink: Increase buffer size to support UCSI v2 Anjelique Melendez
2025-09-25 12:07 ` Konrad Dybcio [this message]
2025-09-25 21:43 ` Dmitry Baryshkov
2025-09-26 18:19 ` Anjelique Melendez
2025-09-26 22:07 ` Dmitry Baryshkov
2025-10-01 9:42 ` Konrad Dybcio
2025-09-26 0:50 ` kernel test robot
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=df671650-a5af-4453-a11d-e8e2a32bd1ab@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=anjelique.melendez@oss.qualcomm.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=johan+linaro@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lumag@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=quic_bjorande@quicinc.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
all inboxes | Powered by JetHome®