From: Mark Brown <broonie@kernel.org>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Jiada Wang <jiada_wang@mentor.com>,
festevam@gmail.com, linux-spi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Applied "spi: imx: dynamic burst length adjust for PIO mode" to the spi tree
Date: Mon, 3 Jul 2017 16:12:34 +0100 [thread overview]
Message-ID: <20170703151234.q3fd7vehoyz62qu3@sirena.org.uk> (raw)
In-Reply-To: <20170630121433.piznjqtmhy35zty6@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 347 bytes --]
On Fri, Jun 30, 2017 at 02:14:33PM +0200, Sascha Hauer wrote:
> This is wrong. MX51_ECSPI_CTRL_MAX_BURST contains the burst length in
> bytes, but the register 'val' is written to takes the burst length in
> bits - 1, so this should be:
> val = MX51_ECSPI_CTRL_MAX_BURST * 8 - 1;
> instead.
Well, it breaks the build anyway so I'll revert.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-07-03 15:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 8:34 [PATCH linux-next v4 1/1] spi: imx: dynamic burst length adjust for PIO mode Jiada Wang
2017-06-30 12:00 ` Applied "spi: imx: dynamic burst length adjust for PIO mode" to the spi tree Mark Brown
2017-06-30 12:14 ` Sascha Hauer
2017-06-30 14:55 ` Jiada Wang
2017-07-03 15:12 ` Mark Brown [this message]
2017-07-07 12:53 ` Mark Brown
2017-07-07 12:58 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2017-08-10 4:50 [PATCH linux-next v5 1/1] spi: imx: dynamic burst length adjust for PIO mode Jiada Wang
2017-08-17 17:14 ` Applied "spi: imx: dynamic burst length adjust for PIO mode" to the spi tree Mark Brown
2017-05-01 10:31 [PATCH linux-next v2 1/1] spi: imx: dynamic burst length adjust for PIO mode jiada_wang
2017-05-15 8:04 ` Applied "spi: imx: dynamic burst length adjust for PIO mode" to the spi tree 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=20170703151234.q3fd7vehoyz62qu3@sirena.org.uk \
--to=broonie@kernel.org \
--cc=festevam@gmail.com \
--cc=jiada_wang@mentor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
/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).