From: Mark Brown <broonie@kernel.org>
To: Stefan Moring <stefan.moring@technolution.nl>
Cc: shawnguo@kernel.org,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
kernel@pengutronix.de, "festevam@gmail.com" <festevam@gmail.com>,
linux-imx@nxp.com, linux-spi@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] spi: Increase imx51 ecspi burst length based on transfer length
Date: Wed, 28 Jun 2023 12:54:43 +0100 [thread overview]
Message-ID: <d1227506-e9b0-4f75-a63b-e25e0c621c48@sirena.org.uk> (raw)
In-Reply-To: <CAB3BuKAVzXWNNiYDceNCpBqBmKyEykKA3rX=cfTyz+gWaJcnkA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 419 bytes --]
On Wed, Jun 28, 2023 at 10:41:27AM +0200, Stefan Moring wrote:
> ctrl |= (spi_imx->slave_burst * 8 - 1)
> << MX51_ECSPI_CTRL_BL_OFFSET;
> - else
> - ctrl |= (spi_imx->bits_per_word - 1)
> - << MX51_ECSPI_CTRL_BL_OFFSET;
> + else {
> + if (spi_imx->count >= 512)
> + ctrl |= 0xFFF << MX51_ECSPI_CTRL_BL_OFFSET;
Your patch is completely mangled and so can't be applied - please check
your setup for sending things.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next parent reply other threads:[~2023-06-28 11:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAB3BuKAVzXWNNiYDceNCpBqBmKyEykKA3rX=cfTyz+gWaJcnkA@mail.gmail.com>
2023-06-28 11:54 ` Mark Brown [this message]
2023-06-28 12:55 ` Stefan Moring
2023-06-28 12:54 Stefan Moring
2023-06-28 13:16 ` Fabio Estevam
2023-06-28 13:20 ` Stefan Moring
2024-06-18 11:58 ` Marc Kleine-Budde
2024-06-18 15:59 ` Marc Kleine-Budde
2024-06-18 16:02 ` Mark Brown
2024-06-18 16:06 ` Marc Kleine-Budde
2024-06-18 16:11 ` Mark Brown
2023-07-11 22:04 ` Mark Brown
2023-09-14 22:47 ` Sebastian Reichel
[not found] ` <CAB3BuKAEFewb6W5K=Z2ZX9Xx0gA+RW+XKY-Mkn-PfBOfq3eb+A@mail.gmail.com>
2023-09-16 23:53 ` Sebastian Reichel
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=d1227506-e9b0-4f75-a63b-e25e0c621c48@sirena.org.uk \
--to=broonie@kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=stefan.moring@technolution.nl \
/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®