mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ivan T. Ivanov" <iivanov@mm-sol.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v2] spi: Ensure that CS line is in non-active state after spi_setup()
Date: Fri, 20 Mar 2015 18:14:49 +0200	[thread overview]
Message-ID: <1426868089.14974.12.camel@mm-sol.com> (raw)
In-Reply-To: <1426265029-12280-1-git-send-email-iivanov@mm-sol.com>


On Fri, 2015-03-13 at 18:43 +0200, Ivan T. Ivanov wrote:
> Some devices samples state of the chip select signal during power up
> and act differently based on this state, so SPI core should ensure
> that CS line is driven in non-active state after spi_setup().
> 
> Signed-off-by: Ivan T. Ivanov <iivanov@mm-sol.com>
> ---

Any comments on this one?

Forget to add changes since v1 [1].

CS is set to non-active state unconditionally before
spi->master->setup()

Regards,
Ivan

[1] http://www.spinics.net/lists/linux-spi/msg03056.html

>  drivers/spi/spi.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/spi/spi.c b/drivers/spi/spi.c
> index c64a3e5..4023cc9 100644
> --- a/drivers/spi/spi.c
> +++ b/drivers/spi/spi.c
> @@ -1893,6 +1893,8 @@ int spi_setup(struct spi_device *spi)
>         if (!spi->max_speed_hz)
>                 spi->max_speed_hz = spi->master->max_speed_hz;
> 
> +       spi_set_cs(spi, false);
> +
>         if (spi->master->setup)
>                 status = spi->master->setup(spi);
> 



  reply	other threads:[~2015-03-20 16:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-13 16:43 Ivan T. Ivanov
2015-03-20 16:14 ` Ivan T. Ivanov [this message]
2015-03-20 16:17   ` 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=1426868089.14974.12.camel@mm-sol.com \
    --to=iivanov@mm-sol.com \
    --cc=broonie@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.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

Powered by JetHome