linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Laight <David.Laight@ACULAB.COM>
To: 'Ronald Wahl' <ronald.wahl@raritan.com>,
	Miquel Raynal <miquel.raynal@bootlin.com>,
	Richard Weinberger <richard@nod.at>
Cc: Mark Brown <broonie@kernel.org>,
	linux-spi <linux-spi@vger.kernel.org>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Ryan Wanner <ryan.wanner@microchip.com>,
	stable <stable@vger.kernel.org>,
	"Richard Weinberger" <richard.weinberger@gmail.com>,
	David Woodhouse <dwmw2@infradead.org>
Subject: RE: [PATCH 1/2] spi: atmel: Do not cancel a transfer upon any signal
Date: Mon, 4 Dec 2023 12:19:51 +0000	[thread overview]
Message-ID: <b0070511200c4e11b3b57e3c77e05388@AcuMS.aculab.com> (raw)
In-Reply-To: <c7980bbf-04aa-4c52-9c6c-f3a1169e90f9@raritan.com>

...
> >> This calculation is actually wrong by factor 1000. A 20MHz SPI bus is not
> >> really slow and it will transfer ~2.5MB/s over a single lane.
> >> The calculation would be right for 20kHz but I think this is a more
> >> esoteric case, isn't it?
> >
> > Some of the sums are wrong, but the conclusion might be right.
> > A 4MB transfer at 20MHz only has 5 clocks/byte - seems low if it
> > is only using 1 data bit.
> 
> Can't really follow. Each data bit requires one clock on single wire
> SPI. Adressing and the like may require a bit of overhead but that
> should not be that much (12.5%?).

That is for 4MB in one second at 20MHz.

An SPI read transfer can be pretty much any length - you just keep
on clocking out data. The overhead is independent of the length.

A memory cell just reminded me that some SPI devices are made
of two (or more) memory blocks - and you can't do sequential
reads from one block to the next.
(It might be lying...)

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)

  parent reply	other threads:[~2023-12-04 12:20 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-27  9:58 [PATCH 1/2] spi: atmel: Do not cancel a transfer upon any signal Miquel Raynal
2023-11-27  9:58 ` [PATCH 2/2] spi: atmel: Drop unused defines Miquel Raynal
2023-11-27 15:10 ` [PATCH 1/2] spi: atmel: Do not cancel a transfer upon any signal Ronald Wahl
2023-11-27 17:54   ` Ronald Wahl
2023-11-29  8:49     ` Miquel Raynal
2023-11-29 11:05       ` Ronald Wahl
2023-11-30 12:46       ` Richard Weinberger
2023-11-30 18:26         ` Richard Weinberger
2023-11-30 18:36           ` Ronald Wahl
2023-11-30 20:15           ` Miquel Raynal
2023-11-30 20:43             ` Ronald Wahl
2023-11-30 20:58               ` Richard Weinberger
2023-12-01 11:13               ` David Laight
2023-12-01 13:38                 ` Ronald Wahl
2023-12-04 11:54                   ` Ronald Wahl
2023-12-04 12:26                     ` Mark Brown
2023-12-04 12:39                       ` Ronald Wahl
2023-12-04 12:19                   ` David Laight [this message]
2023-12-05  7:49               ` Miquel Raynal
2023-11-27 16:48 ` Mark Brown
2023-12-01 14:16 ` Mark Brown
2023-12-04 15:47 ` 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=b0070511200c4e11b3b57e3c77e05388@AcuMS.aculab.com \
    --to=david.laight@aculab.com \
    --cc=broonie@kernel.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=richard.weinberger@gmail.com \
    --cc=richard@nod.at \
    --cc=ronald.wahl@raritan.com \
    --cc=ryan.wanner@microchip.com \
    --cc=stable@vger.kernel.org \
    --cc=thomas.petazzoni@bootlin.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;
as well as URLs for NNTP newsgroup(s).