From: "Arnd Bergmann" <arnd@arndb.de>
To: "Manikanta Guntupalli" <manikanta.guntupalli@amd.com>,
"git (AMD-Xilinx)" <git@amd.com>,
"Michal Simek" <michal.simek@amd.com>,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
"Frank Li" <Frank.Li@nxp.com>, "Rob Herring" <robh@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Przemysław Gaj" <pgaj@cadence.com>,
"Wolfram Sang" <wsa+renesas@sang-engineering.com>,
"tommaso.merciai.xr@bp.renesas.com"
<tommaso.merciai.xr@bp.renesas.com>,
"quic_msavaliy@quicinc.com" <quic_msavaliy@quicinc.com>,
"S-k, Shyam-sundar" <Shyam-sundar.S-k@amd.com>,
"Sakari Ailus" <sakari.ailus@linux.intel.com>,
"'billy_tsai@aspeedtech.com'" <billy_tsai@aspeedtech.com>,
"Kees Cook" <kees@kernel.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
"Jarkko Nikula" <jarkko.nikula@linux.intel.com>,
"Jorge Marques" <jorge.marques@analog.com>,
"linux-i3c@lists.infradead.org" <linux-i3c@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux-Arch <linux-arch@vger.kernel.org>,
"linux-hardening@vger.kernel.org"
<linux-hardening@vger.kernel.org>
Cc: "Pandey, Radhey Shyam" <radhey.shyam.pandey@amd.com>,
"Goud, Srinivas" <srinivas.goud@amd.com>,
"Datta, Shubhrajyoti" <shubhrajyoti.datta@amd.com>,
"manion05gk@gmail.com" <manion05gk@gmail.com>
Subject: Re: [PATCH V7 3/4] i3c: master: Add endianness support for i3c_readl_fifo() and i3c_writel_fifo()
Date: Wed, 24 Sep 2025 16:05:26 +0200 [thread overview]
Message-ID: <134c3a96-4023-47ab-8aa9-fd6ab75e5654@app.fastmail.com> (raw)
In-Reply-To: <DM4PR12MB6109E009DAC953525093FE808C1CA@DM4PR12MB6109.namprd12.prod.outlook.com>
On Wed, Sep 24, 2025, at 14:22, Guntupalli, Manikanta wrote:
>> @@ -55,7 +55,7 @@ static inline void i3c_readl_fifo(const void __iomem *addr, void
>> *buf,
>> if (nbytes & 3) {
>> u32 tmp;
>>
>> - tmp = readl(addr);
>> + readsl(addr, &tmp, 1);
>> memcpy(buf + (nbytes & ~3), &tmp, nbytes & 3);
>> }
>> }
>
> We have not observed any issue on little-endian systems in our testing
> so far (as I mentioned earlier in asm-generic/io.h: Add big-endian MMIO
> accessors).
Did you test the little-endian system with the 'endian' flag set
to I3C_FIFO_BIG_ENDIAN though? Your v7 code will still work on
little-endian kernels if that flag is set to I3C_FIFO_LITTLE_ENDIAN,
and it will also work on big-endian kernels if the flag is
set to I3C_FIFO_BIG_ENDIAN. But is broken for the other two:
- on little-endian kernels with I3C_FIFO_BIG_ENDIAN, the entire
data buffer is byteswapped in 32-bit chunks
- on big-endian kernels with I3C_FIFO_LITTLE_ENDIAN, you run into
the existing bug of the swapped tail word.
> That said, I understand your point about FIFO semantics being different
> from fixed-endian registers. To cover both cases, we considered using
> writesl() for little-endian and introducing a writesl_be() helper for
> big-endian, as shown below:
>
> static inline void i3c_writel_fifo(void __iomem *addr, const void *buf,
> int nbytes, enum i3c_fifo_endian endian)
> {
> if (endian)
> writesl_be(addr, buf, nbytes / 4);
> else
> writesl(addr, buf, nbytes / 4);
>
> if (nbytes & 3) {
> u32 tmp = 0;
>
> memcpy(&tmp, buf + (nbytes & ~3), nbytes & 3);
>
> if (endian)
> writesl_be(addr, &tmp, 1);
> else
> writesl(addr, &tmp, 1);
> }
> }
>
> With this approach, both little-endian and big-endian cases works as expected.
This version should fix the cases where you have a big-endian
kernel with either I3C_FIFO_BIG_ENDIAN or I3C_FIFO_LITTLE_ENDIAN,
as neither combination does any byte swaps.
However I'm fairly sure it's still broken for little-endian
kernels when a driver asks for a I3C_FIFO_BIG_ENDIAN conversion,
same as v7.
Arnd
next prev parent reply other threads:[~2025-09-24 14:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 15:45 [PATCH V7 0/4] Add AMD I3C master controller driver and bindings Manikanta Guntupalli
2025-09-23 15:45 ` [PATCH V7 1/4] dt-bindings: i3c: Add AMD I3C master controller support Manikanta Guntupalli
2025-09-23 15:45 ` [PATCH V7 2/4] asm-generic/io.h: Add big-endian MMIO accessors Manikanta Guntupalli
2025-09-23 18:38 ` Arnd Bergmann
2025-09-24 8:59 ` Guntupalli, Manikanta
2025-09-24 9:46 ` Arnd Bergmann
2025-09-24 10:12 ` Guntupalli, Manikanta
2025-09-23 18:43 ` Frank Li
2025-09-24 20:34 ` kernel test robot
2025-09-25 6:15 ` kernel test robot
2025-09-23 15:45 ` [PATCH V7 3/4] i3c: master: Add endianness support for i3c_readl_fifo() and i3c_writel_fifo() Manikanta Guntupalli
2025-09-23 18:45 ` Frank Li
2025-09-23 18:51 ` Arnd Bergmann
2025-09-24 9:00 ` Guntupalli, Manikanta
2025-09-24 10:00 ` Arnd Bergmann
2025-09-24 12:22 ` Guntupalli, Manikanta
2025-09-24 14:05 ` Arnd Bergmann [this message]
2025-09-24 15:23 ` Guntupalli, Manikanta
2025-09-24 15:42 ` Arnd Bergmann
2025-09-25 9:26 ` Guntupalli, Manikanta
2025-09-25 12:14 ` Arnd Bergmann
2025-09-25 16:37 ` Guntupalli, Manikanta
2025-09-25 16:50 ` Frank Li
2025-09-25 12:22 ` kernel test robot
2025-09-23 15:45 ` [PATCH V7 4/4] i3c: master: Add AMD I3C bus controller driver Manikanta Guntupalli
2025-09-23 19:22 ` Frank Li
2025-09-25 5:42 ` Guntupalli, Manikanta
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=134c3a96-4023-47ab-8aa9-fd6ab75e5654@app.fastmail.com \
--to=arnd@arndb.de \
--cc=Frank.Li@nxp.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=alexandre.belloni@bootlin.com \
--cc=billy_tsai@aspeedtech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=git@amd.com \
--cc=gustavoars@kernel.org \
--cc=jarkko.nikula@linux.intel.com \
--cc=jorge.marques@analog.com \
--cc=kees@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manikanta.guntupalli@amd.com \
--cc=manion05gk@gmail.com \
--cc=michal.simek@amd.com \
--cc=pgaj@cadence.com \
--cc=quic_msavaliy@quicinc.com \
--cc=radhey.shyam.pandey@amd.com \
--cc=robh@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=shubhrajyoti.datta@amd.com \
--cc=srinivas.goud@amd.com \
--cc=tommaso.merciai.xr@bp.renesas.com \
--cc=wsa+renesas@sang-engineering.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