From: Michael Welling <mwelling-EkmVulN54Sk@public.gmane.org>
To: broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] spi: omap2-mcspi: Add support for GPIO chipselects
Date: Mon, 13 Apr 2015 15:45:21 -0500 [thread overview]
Message-ID: <20150413204521.GA2873@deathray> (raw)
In-Reply-To: <1428528961-7838-1-git-send-email-mwelling-EkmVulN54Sk@public.gmane.org>
I noticed a response to my message on the mailing lists that did not appear in
my mailbox. Not sure where it went.
Sorry about the over 80 characters in the commit log.
As for the question about the uninitialized GPIOs, it is taken care in the
core SPI driver.
The cs_gpio struct member is initialized to -ENOENT in spi_alloc_device:
http://lxr.free-electrons.com/source/drivers/spi/spi.c#L353
If there are GPIOs specified in the devicetree the value is updated:
http://lxr.free-electrons.com/source/drivers/spi/spi.c#L440
On Wed, Apr 08, 2015 at 04:36:01PM -0500, Michael Welling wrote:
> This patch allows for GPIOs specified in the devicetree to be used as SPI chipselects
> on TI OMAP2 SoCs.
>
> Tested on the AM3354.
>
> Signed-off-by: Michael Welling <mwelling-EkmVulN54Sk@public.gmane.org>
> ---
> drivers/spi/spi-omap2-mcspi.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/drivers/spi/spi-omap2-mcspi.c b/drivers/spi/spi-omap2-mcspi.c
> index 4df8942..464dec9 100644
> --- a/drivers/spi/spi-omap2-mcspi.c
> +++ b/drivers/spi/spi-omap2-mcspi.c
> @@ -35,6 +35,7 @@
> #include <linux/gcd.h>
>
> #include <linux/spi/spi.h>
> +#include <linux/gpio.h>
>
> #include <linux/platform_data/spi-omap2-mcspi.h>
>
> @@ -246,6 +247,9 @@ static void omap2_mcspi_force_cs(struct spi_device *spi, int cs_active)
> {
> u32 l;
>
> + if (gpio_is_valid(spi->cs_gpio))
> + gpio_set_value(spi->cs_gpio, (cs_active) ? 0 : 1);
> +
This may need to be changed to reflect the value of the spi->mode SPI_CS_HIGH
bit. It seems that I assumed that the chipselects are active low above.
> l = mcspi_cached_chconf0(spi);
> if (cs_active)
> l |= OMAP2_MCSPI_CHCONF_FORCE;
> @@ -1015,6 +1019,12 @@ static int omap2_mcspi_setup(struct spi_device *spi)
> if (ret < 0)
> return ret;
>
> + if (gpio_is_valid(spi->cs_gpio)) {
> + if (gpio_request(spi->cs_gpio, dev_name(&spi->dev)) == 0)
> + gpio_direction_output(spi->cs_gpio,
> + !(spi->mode & SPI_CS_HIGH));
> + }
> +
> ret = omap2_mcspi_setup_transfer(spi, NULL);
> pm_runtime_mark_last_busy(mcspi->dev);
> pm_runtime_put_autosuspend(mcspi->dev);
> --
> 1.7.9.5
>
--
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
prev parent reply other threads:[~2015-04-13 20:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 21:36 [PATCH] spi: omap2-mcspi: Add support for GPIO chipselects Michael Welling
[not found] ` <1428528961-7838-1-git-send-email-mwelling-EkmVulN54Sk@public.gmane.org>
2015-04-09 10:52 ` Mark Brown
2015-04-13 20:45 ` Michael Welling [this message]
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=20150413204521.GA2873@deathray \
--to=mwelling-ekmvuln54sk@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@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).