From: Greg KH <gregkh@linuxfoundation.org>
To: Pramod Maurya <pramod.nexgen@gmail.com>
Cc: jacobsfeder@gmail.com, ovidiu.panait.oss@gmail.com,
gustavopiazdasilva2102@gmail.com, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: axis-fifo: use stream accessors for FIFO data transfers
Date: Tue, 7 Jul 2026 12:02:06 +0200 [thread overview]
Message-ID: <2026070725-submitter-mobster-1089@gregkh> (raw)
In-Reply-To: <20260523194009.195538-1-pramod.nexgen@gmail.com>
On Sat, May 23, 2026 at 03:40:09PM -0400, Pramod Maurya wrote:
> To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: Jacob Feder <jacobsfeder@gmail.com>
> Cc: Ovidiu Panait <ovidiu.panait.oss@gmail.com>
> Cc: Gustavo Piaz da Silva <gustavopiazdasilva2102@gmail.com>
> Cc: linux-staging@lists.linux.dev
> Cc: linux-kernel@vger.kernel.org
Again, why is this here?
>
> The driver uses iowrite32()/ioread32() to transfer payload data to and
> from the transmit (XLLF_TDFD_OFFSET) and receive (XLLF_RDFD_OFFSET)
> data FIFOs. On big-endian architectures iowrite32() maps to writel()
> and ioread32() maps to readl(), both of which perform CPU-to-device
> byte-swapping. For AXI-Stream FIFOs, which carry opaque byte streams,
> this byte-swapping silently corrupts the payload.
>
> Replace the per-word iowrite32()/ioread32() loops with writesl()/readsl(),
> which transfer data without byte-swapping, preserving memory byte order
> as required by AXI-Stream FIFO semantics.
>
> Also convert the err_flush_rx drain loop to use batched readsl() with
> min_t(unsigned int, ...) to match the types of words_available and
> READ_BUF_SIZE, reusing the existing local variable copy.
When you have to say "also", that's a huge hint this should be split up
into multiple changes. Please do that here.
thanks,
greg k-h
prev parent reply other threads:[~2026-07-07 10:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-23 19:40 [PATCH] staging: axis-fifo: use stream accessors for FIFO data transfers Pramod Maurya
2026-07-07 10:02 ` Greg KH [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=2026070725-submitter-mobster-1089@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=gustavopiazdasilva2102@gmail.com \
--cc=jacobsfeder@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=ovidiu.panait.oss@gmail.com \
--cc=pramod.nexgen@gmail.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