From: Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
To: Axel Lin <axel.lin-8E1dMatC8ynQT0dZR+AlfA@public.gmane.org>,
Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH RFC] spi: core: Use master->max_speed_hz as transfer speed when xfer->speed_hz > master->max_speed_hz
Date: Sun, 16 Mar 2014 20:54:19 -0700 [thread overview]
Message-ID: <532671EB.3010502@roeck-us.net> (raw)
In-Reply-To: <1395022092.30299.1.camel@phoenix>
On 03/16/2014 07:08 PM, Axel Lin wrote:
> When xfer->speed_hz is greater than master->max_speed_hz, it's generally safe
> to use master->max_speed_hz as transfer speed.
> Thus use master->max_speed_hz as transfer speed rather than return error when
> xfer->speed_hz > master->max_speed_hz.
>
> Signed-off-by: Axel Lin <axel.lin-8E1dMatC8ynQT0dZR+AlfA@public.gmane.org>
Tested-by: Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
Reviewed-by: Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
Guenter
> ---
> Hi Guenter,
> Does this patch fix the issue you encounter?
> Regards,
> Axel
> drivers/spi/spi.c | 14 ++++++--------
> 1 file changed, 6 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/spi/spi.c b/drivers/spi/spi.c
> index 454a523..26b331d 100644
> --- a/drivers/spi/spi.c
> +++ b/drivers/spi/spi.c
> @@ -1844,12 +1844,13 @@ static int __spi_validate(struct spi_device *spi, struct spi_message *message)
> message->frame_length += xfer->len;
> if (!xfer->bits_per_word)
> xfer->bits_per_word = spi->bits_per_word;
> - if (!xfer->speed_hz) {
> +
> + if (!xfer->speed_hz)
> xfer->speed_hz = spi->max_speed_hz;
> - if (master->max_speed_hz &&
> - xfer->speed_hz > master->max_speed_hz)
> - xfer->speed_hz = master->max_speed_hz;
> - }
> +
> + if (master->max_speed_hz &&
> + xfer->speed_hz > master->max_speed_hz)
> + xfer->speed_hz = master->max_speed_hz;
>
> if (master->bits_per_word_mask) {
> /* Only 32 bits fit in the mask */
> @@ -1878,9 +1879,6 @@ static int __spi_validate(struct spi_device *spi, struct spi_message *message)
> if (xfer->speed_hz && master->min_speed_hz &&
> xfer->speed_hz < master->min_speed_hz)
> return -EINVAL;
> - if (xfer->speed_hz && master->max_speed_hz &&
> - xfer->speed_hz > master->max_speed_hz)
> - return -EINVAL;
>
> if (xfer->tx_buf && !xfer->tx_nbits)
> xfer->tx_nbits = SPI_NBITS_SINGLE;
>
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-03-17 3:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-17 2:08 [PATCH RFC] spi: core: Use master->max_speed_hz as transfer speed when xfer->speed_hz > master->max_speed_hz Axel Lin
2014-03-17 2:21 ` Guenter Roeck
2014-03-17 3:54 ` Guenter Roeck [this message]
2014-03-17 15:46 ` 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=532671EB.3010502@roeck-us.net \
--to=linux-0h96xk9xttrk1umjsbkqmq@public.gmane.org \
--cc=axel.lin-8E1dMatC8ynQT0dZR+AlfA@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).