[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c5c95368-eac3-4250-b50a-50f0a526b753@sirena.org.uk>
Date: Mon, 26 Jun 2023 20:47:27 +0100
From: Mark Brown <broonie@...nel.org>
To: Xu Yilun <yilun.xu@...el.com>
Cc: Russ Weight <russell.h.weight@...el.com>,
gregkh@...uxfoundation.org, rafael@...nel.org,
linux-kernel@...r.kernel.org, matthew.gerlach@...ux.intel.com,
Jim Wylder <jwylder@...gle.com>
Subject: Re: [PATCH 1/1] regmap: spi-avmm: Fix regmap_bus max_raw_write
On Sun, Jun 25, 2023 at 12:26:31PM +0800, Xu Yilun wrote:
> IIUC, max_raw_write/read is the max batch *DATA* size that could be
> handled by the receiver. reg addr bytes are not counted in. I'm not 100%
> sure this is obeyed by all drivers. But see several examples:
There's clearly been some confusion in a bunch of drivers, those you've
identified below need fixing too for the new code from the looks of it.
I'm frankly unclear why some of the drivers you're pointing at are even
implementing raw buses.
> So I'm not sure if commit 3981514180c9 is actually necessary.
That's "regmap: Account for register length when chunking". It's
certainly a bit unclear now I go do another survey, though it's also
clear that things like the handling of padding are intermittent at best.
We probably would be safe reverting that.
Jim, where were you seeing the issue here?
Please include human readable descriptions of things like commits and
issues being discussed in e-mail in your mails, this makes them much
easier for humans to read especially when they have no internet access.
I do frequently catch up on my mail on flights or while otherwise
travelling so this is even more pressing for me than just being about
making things a bit easier to read.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists