From: Mark Brown <broonie@kernel.org>
To: "Oskari Lemmelä" <oskari@lemmela.net>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] spi: ar934x: fix transfer size
Date: Wed, 22 Dec 2021 14:59:30 +0000 [thread overview]
Message-ID: <YcM9Ug3JhaxynLt0@sirena.org.uk> (raw)
In-Reply-To: <98a574a2-45c3-5d7c-6405-0cd279a81816@lemmela.net>
[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]
On Wed, Dec 22, 2021 at 04:27:36PM +0200, Oskari Lemmelä wrote:
> On 22.12.2021 14.32, Mark Brown wrote:
> > Does this actually materially affect what the hardware does? How much
> > data is transferred in an internal loop in the driver is completely
> > immaterial, bits per word only matters for formatting of the transferred
> > data.
> I don't have logic analyzator to verify what hardware actual does.
> I tested this with transferring 32bits to ATSAMD20J15 slave.
> Running loop in 8bits or 16bits, transfer is done correctly without
> any errors. When running loop in 24bits or 32bits directly I got
> error from spi_sync_transfer.
This doesn't inspire confidence TBH. Given the lack of any change in
the interaction with the hardware it doesn't seem likely that the word
length is being changed at any point. Possibly there's a bug somewhere
that needs fixing but it's been misdiagnosed.
Note also that the commit log is not good here, now I look at the code
the driver only supports 8 bits per word at the minute and the change
adds support for higher word lengths. If you are seeing an issue that
might point towards what it is.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-12-22 14:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 5:59 [PATCH 0/2] spi: ar934x: fix transfer size and delays Oskari Lemmela
2021-12-22 5:59 ` [PATCH 1/2] spi: ar934x: fix transfer size Oskari Lemmela
2021-12-22 12:32 ` Mark Brown
2021-12-22 14:27 ` Oskari Lemmelä
2021-12-22 14:59 ` Mark Brown [this message]
2021-12-22 15:55 ` Oskari Lemmelä
2021-12-22 5:59 ` [PATCH 2/2] spi: ar934x: fix transfer and word delays Oskari Lemmela
2021-12-22 14:04 ` (subset) [PATCH 0/2] spi: ar934x: fix transfer size and delays Mark Brown
2022-01-04 16:02 ` Mark Brown
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=YcM9Ug3JhaxynLt0@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=oskari@lemmela.net \
/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®