From: Ryan Mallon <rmallon@gmail.com>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
spi-devel-general@lists.sourceforge.net, mika.westerberg@iki.fi,
broonie@kernel.org, grant.likely@linaro.org
Subject: Re: [PATCH 3/8] spi: spi-ep93xx: always handle transfer specific settings
Date: Sat, 29 Jun 2013 09:17:46 +1000 [thread overview]
Message-ID: <51CE199A.4040606@gmail.com> (raw)
In-Reply-To: <201306281143.35130.hartleys@visionengravers.com>
On 29/06/13 04:43, H Hartley Sweeten wrote:
> __spi_async(), which starts every SPI message transfer, initializes
> the bits_per_word and max speed for every transfer in the message.
> Since the conditional test in ep93xx_spi_process_transfer() will
> always succeed just remove it and always call ep93xx_spi_chip_setup()
> to configure the hardware for each transfer in the message.
>
> Remove the redundant ep93xx_spi_chp_setup() in ep93xx_spi_process_transfer()
> which just initializes the hardware to the "default" based on the SPI
> device.
>
> Signed-off-by: H Hartley Sweeten <hsweeten@visionengravers.com>
> Cc: Ryan Mallon <rmallon@gmail.com>
> Cc: Mika Westerberg <mika.westerberg@iki.fi>
> Cc: Mark Brown <broonie@kernel.org>
> Cc: Grant Likely <grant.likely@linaro.org>
> ---
> + err = ep93xx_spi_calc_divisors(espi, chip, t->speed_hz);
> + if (err) {
> + dev_err(&espi->pdev->dev, "failed to adjust speed\n");
Printing out the speed it was trying to set might be useful here?
~Ryan
next prev parent reply other threads:[~2013-06-28 23:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 18:43 [PATCH 3/8] spi: spi-ep93xx: always handle transfer specific settings H Hartley Sweeten
2013-06-28 23:17 ` Ryan Mallon [this message]
[not found] ` <51CE199A.4040606-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-06-28 23:42 ` H Hartley Sweeten
[not found] ` <201306281143.35130.hartleys-3FF4nKcrg1dE2c76skzGb0EOCMrvLtNR@public.gmane.org>
2013-06-30 16:26 ` Mika Westerberg
2013-07-01 10:27 ` Mark Brown
2013-07-01 18:15 ` H Hartley Sweeten
2013-07-01 19:11 ` 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=51CE199A.4040606@gmail.com \
--to=rmallon@gmail.com \
--cc=broonie@kernel.org \
--cc=grant.likely@linaro.org \
--cc=hartleys@visionengravers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@iki.fi \
--cc=spi-devel-general@lists.sourceforge.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;
as well as URLs for NNTP newsgroup(s).