From: Marek Vasut <marex-ynQEQJNshbs@public.gmane.org>
To: Trent Piepho <tpiepho-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Fabio Estevam
<fabio.estevam-KZfg59tc24xl57MIdRCFDg@public.gmane.org>,
spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
Shawn Guo <shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: [PATCH V2 08/12] spi/mxs: Fix race in setup method
Date: Wed, 3 Apr 2013 04:27:41 +0200 [thread overview]
Message-ID: <201304030427.41297.marex@denx.de> (raw)
In-Reply-To: <CA+7tXigasUbSRD6hQH66m6XsDkzS9ubLSB24f4akB3pv9xrT=A@mail.gmail.com>
Dear Trent Piepho,
> On Tue, Apr 2, 2013 at 4:31 PM, Marek Vasut <marex-ynQEQJNshbs@public.gmane.org> wrote:
> >> static int mxs_spi_setup(struct spi_device *dev)
> >> {
> >>
> >> - int err = 0;
> >> -
> >>
> >> if (!dev->bits_per_word)
> >>
> >> dev->bits_per_word = 8;
> >>
> >> if (dev->mode & ~(SPI_CPOL | SPI_CPHA))
> >>
> >> return -EINVAL;
> >>
> >> - err = mxs_spi_setup_transfer(dev, NULL);
> >> - if (err) {
> >> - dev_err(&dev->dev,
> >> - "Failed to setup transfer, error = %d\n", err);
> >> - }
> >> + if (dev->bits_per_word != 8)
> >> + return -EINVAL;
> >
> > What's this new addition doing here?
>
> It's not new.
It is new in the context of this patch and it's not described in the commit
message.
> The only useful thing mxs_spi_setup_transfer() (which
> is no longer called) did in this instance was make that check.
>
> > btw. I was under the impression the MXS SSP block can handle other
> > word-widths than 8 bit, no ?
>
> In theory it can,
In practice too ;-)
> however the driver only supports 8-bits and will
> reject anything else.
Then please at least add a comment about this.
Best regards,
Marek Vasut
------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire
the most talented Cisco Certified professionals. Visit the
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
next prev parent reply other threads:[~2013-04-03 2:27 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 12:19 [PATCH V2 01/12] spi/mxs: Always set LOCK_CS Trent Piepho
[not found] ` <1364905195-24286-1-git-send-email-tpiepho-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-04-02 12:19 ` [PATCH V2 02/12] spi/mxs: Remove mxs_spi_enable and mxs_spi_disable Trent Piepho
2013-04-02 12:19 ` [PATCH V2 03/12] spi/mxs: Change flag arguments in txrx functions to bit flags Trent Piepho
[not found] ` <1364905195-24286-3-git-send-email-tpiepho-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-04-02 23:24 ` Marek Vasut
2013-04-02 12:19 ` [PATCH V2 04/12] spi/mxs: Fix extra CS pulses and read mode in multi-transfer messages Trent Piepho
2013-04-02 12:19 ` [PATCH V2 05/12] spi/mxs: Fix chip select control bits in DMA mode Trent Piepho
[not found] ` <1364905195-24286-5-git-send-email-tpiepho-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-04-02 23:29 ` Marek Vasut
2013-04-02 12:19 ` [PATCH V2 06/12] spi/mxs: Remove full duplex check, spi core already does it Trent Piepho
2013-04-02 12:19 ` [PATCH V2 07/12] spi/mxs: Remove bogus setting of ssp clk rate field Trent Piepho
2013-04-02 12:19 ` [PATCH V2 08/12] spi/mxs: Fix race in setup method Trent Piepho
[not found] ` <1364905195-24286-8-git-send-email-tpiepho-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-04-02 23:31 ` Marek Vasut
[not found] ` <201304030131.37782.marex-ynQEQJNshbs@public.gmane.org>
2013-04-03 2:12 ` Trent Piepho
2013-04-03 2:27 ` Marek Vasut [this message]
[not found] ` <201304030427.41297.marex-ynQEQJNshbs@public.gmane.org>
2013-04-03 6:08 ` Trent Piepho
[not found] ` <CA+7tXih2r6YFE80y7z7Nj7c0Ytvh+v56-SrbS+VQ7kCW3KBRXA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-04-03 6:50 ` Marek Vasut
[not found] ` <201304030850.31752.marex-ynQEQJNshbs@public.gmane.org>
2013-04-03 9:32 ` Trent Piepho
2013-04-02 12:19 ` [PATCH V2 09/12] spi/mxs: Remove check of spi mode bits Trent Piepho
2013-04-02 12:19 ` [PATCH V2 10/12] spi/mxs: Clean up setup_transfer function Trent Piepho
[not found] ` <1364905195-24286-10-git-send-email-tpiepho-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-04-02 23:35 ` Marek Vasut
2013-04-02 12:19 ` [PATCH V2 11/12] spi/mxs: Don't set clock for each xfer Trent Piepho
[not found] ` <1364905195-24286-11-git-send-email-tpiepho-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-04-02 23:38 ` Marek Vasut
2013-04-02 12:19 ` [PATCH V2 12/12] spi/mxs: Use u32 instead of uint32_t Trent Piepho
2013-04-02 23:18 ` [PATCH V2 01/12] spi/mxs: Always set LOCK_CS Marek Vasut
[not found] ` <201304030118.42976.marex-ynQEQJNshbs@public.gmane.org>
2013-07-10 13:49 ` Fabio Estevam
2013-07-10 15:29 ` Lothar Waßmann
[not found] ` <20957.32214.721252.361301-VjFSrY7JcPWvSplVBqRQBQ@public.gmane.org>
2013-07-18 1:08 ` Trent Piepho
2013-04-03 1:41 ` Shawn Guo
2013-04-14 18:01 ` Marek Vasut
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=201304030427.41297.marex@denx.de \
--to=marex-ynqeqjnshbs@public.gmane.org \
--cc=fabio.estevam-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=tpiepho-Re5JQEeQqe8AvxtiuMwx3w@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).