From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Loic Poulain <loic.poulain@oss.qualcomm.com>,
Robert Foss <rfoss@kernel.org>,
Andi Shyti <andi.shyti@kernel.org>
Cc: linux-i2c@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/7] i2c: qcom-cci: Factor out write command queue programming
Date: Wed, 21 Oct 2026 15:48:43 +0200 [thread overview]
Message-ID: <c2b5f9de-d1f0-4131-82f4-396579520515@oss.qualcomm.com> (raw)
In-Reply-To: <20261016-cci-imp-v3-1-5ee7ec1ea1a1@oss.qualcomm.com>
On 10/16/26 10:00 AM, Loic Poulain wrote:
> Factor out write-command queueing into a dedicated helper and replace
> the manual byte-to-word packing code with iowrite32_rep().
>
> The resulting code is easier to follow and will be reused by
> upcoming burst-write support.
>
> A command can only carry as many data bytes as fit in its words, so
> validate the length before building one, and do so where an error can
> still be returned. The I2C core already rejects a transfer longer than
> the limit advertised through the adapter quirks, so this is only a
> guard against building a command that would corrupt the queue.
>
> Signed-off-by: Loic Poulain <loic.poulain@oss.qualcomm.com>
> ---
> +static void cci_i2c_load_write(u8 *buf, u16 len, void __iomem *loadq)
> +{
> + u32 cmd[CCI_I2C_WRITE_WC] = { };
> +
> + cmd[0] = CCI_I2C_WRITE | len << 4;
> + memcpy((u8 *)cmd + 1, buf, len);
LLM says this is no longer big-endian friendly, but BE arm64
is going away anyway so I woouldn't really change it
> + iowrite32_rep(loadq, cmd, CCI_I2C_WRITE_NWORDS(len));
> +}
> +
> static int cci_i2c_write(struct cci *cci, u16 master,
> u16 addr, u8 *buf, u16 len)
> {
> - u8 queue = QUEUE_0;
> - u8 load[12] = { 0 };
> - int i = 0, j, ret;
> + void __iomem *loadq = cci->base + CCI_I2C_Mm_Qn_LOAD_DATA(master, QUEUE_0);
> + int ret;
> u32 val;
>
> + dev_dbg(cci->dev, "master %d write: len=%u\n", master, len);
> +
> + /* This condition should be guaranteed by the caller (i2c core) */
> + if (WARN_ON(len > cci->data->quirks.max_write_len))
> + return -EOPNOTSUPP;
Likewise LLM suggests this is an odd error to return and I agree EINVAL
could be better
with that:
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Konrad
next prev parent reply other threads:[~2026-10-21 13:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 8:00 [PATCH v3 0/7] i2c: qcom-cci: Runtime capability detection and improved read/write Loic Poulain
2026-10-16 8:00 ` [PATCH v3 1/7] i2c: qcom-cci: Factor out write command queue programming Loic Poulain
2026-10-21 13:48 ` Konrad Dybcio [this message]
2026-10-16 8:00 ` [PATCH v3 2/7] i2c: qcom-cci: Handle and report queue overflow/underflow interrupts Loic Poulain
2026-10-21 10:40 ` Konrad Dybcio
2026-10-16 8:00 ` [PATCH v3 3/7] i2c: qcom-cci: Detect capabilities from CCI_HW_VERSION at runtime Loic Poulain
2026-10-21 10:42 ` Konrad Dybcio
2026-10-16 8:00 ` [PATCH v3 4/7] i2c: qcom-cci: Add burst write support Loic Poulain
2026-10-21 10:45 ` Konrad Dybcio
2026-10-16 8:00 ` [PATCH v3 5/7] i2c: qcom-cci: Extend i2c read limits based on CCI revision Loic Poulain
2026-10-21 10:50 ` Konrad Dybcio
2026-10-16 8:00 ` [PATCH v3 6/7] i2c: qcom-cci: Add burst read support Loic Poulain
2026-10-21 11:01 ` Konrad Dybcio
2026-10-16 8:00 ` [PATCH v3 7/7] i2c: qcom-cci: Build command words with FIELD_PREP() Loic Poulain
2026-10-21 11:03 ` Konrad Dybcio
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=c2b5f9de-d1f0-4131-82f4-396579520515@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andi.shyti@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.poulain@oss.qualcomm.com \
--cc=rfoss@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
all inboxes | Powered by JetHome®