From: <Thomas.Kopp@microchip.com>
To: <broonie@kernel.org>
Cc: <Tudor.Ambarus@microchip.com>, <linux-spi@vger.kernel.org>
Subject: RE: [PATCH v2] spi: atmel: Exposing effective spi speed
Date: Thu, 1 Oct 2020 06:50:08 +0000 [thread overview]
Message-ID: <DM6PR11MB428354FF073BCB8668D50DDFFB300@DM6PR11MB4283.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20200921071036.2091-1-thomas.kopp@microchip.com>
> This patch implements the reporting of the effectively used speed_hz for
> the transfer by setting xfer->effective_speed_hz.
>
> See the following patch, which adds this feature to the SPI core for more
> information:
> commit 5d7e2b5ed585 ("spi: core: allow reporting the effectivly used
> speed_hz for a transfer")
>
> Signed-off-by: Thomas Kopp <thomas.kopp@microchip.com>
> Reviewed-by: Tudor Ambarus <tudor.ambarus@microchip.com>
> ---
> drivers/spi/spi-atmel.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/spi/spi-atmel.c b/drivers/spi/spi-atmel.c
> index 2cfe6253a784..799229bc34e1 100644
> --- a/drivers/spi/spi-atmel.c
> +++ b/drivers/spi/spi-atmel.c
> @@ -859,6 +859,7 @@ static int atmel_spi_set_xfer_speed(struct
> atmel_spi *as,
> csr = spi_readl(as, CSR0 + 4 * chip_select);
> csr = SPI_BFINS(SCBR, scbr, csr);
> spi_writel(as, CSR0 + 4 * chip_select, csr);
> + xfer->effective_speed_hz = bus_hz / scbr;
>
> return 0;
> }
> --
> 2.25.1
Hi Mark,
I realized I only sent this to the list, not to you on to/cc. Can you consider
pulling this please?
Thanks,
Thomas
next prev parent reply other threads:[~2020-10-01 6:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 7:10 [PATCH v2] spi: atmel: Exposing effective spi speed Thomas Kopp
2020-10-01 6:50 ` Thomas.Kopp [this message]
2020-10-01 16:29 ` Mark Brown
2020-10-01 22: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=DM6PR11MB428354FF073BCB8668D50DDFFB300@DM6PR11MB4283.namprd11.prod.outlook.com \
--to=thomas.kopp@microchip.com \
--cc=Tudor.Ambarus@microchip.com \
--cc=broonie@kernel.org \
--cc=linux-spi@vger.kernel.org \
/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).