From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: Girish K S <girishks2000-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH 3/4] spi: s3c64xx: add gpio quirk for controller
Date: Wed, 06 Feb 2013 10:40:00 +0000 [thread overview]
Message-ID: <20130206104000.98E803E1510@localhost> (raw)
In-Reply-To: <1360105784-12282-4-git-send-email-ks.giri-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
On Tue, 5 Feb 2013 15:09:43 -0800, Girish K S <girishks2000-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> This patch adds support for spi controllers with
> dedicated clk/miso/mosi/cs pins. It skips the gpio
> parsing and initialization for controllers that
> have dedicated pins.
>
> Signed-off-by: Girish K S <ks.giri-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
Instead of making this a quirk, you should use the presence/absense of a
cs-gpios property to determin whether or not a gpio is used to
manipulate the CS signal.
Also, are you certain that you want to make this change? Most SPI
controllers are actually unfriendly in that they insist on deasserting the
CS line if the FIFO runs empty. Does this driver correctly keep the CS
signal asserted when there are multiple transfers in a message?
g.
> ---
> drivers/spi/spi-s3c64xx.c | 39 +++++++++++++++++++++++++++++++--------
> 1 file changed, 31 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/spi/spi-s3c64xx.c b/drivers/spi/spi-s3c64xx.c
> index 90770bd..f06bbee 100644
> --- a/drivers/spi/spi-s3c64xx.c
> +++ b/drivers/spi/spi-s3c64xx.c
> @@ -36,6 +36,7 @@
>
> #define MAX_SPI_PORTS 3
> #define S3C64XX_SPI_QUIRK_POLL (1 << 0)
> +#define S3C64XX_SPI_QUIRK_GPIO (1 << 1)
>
> /* Registers and bit-fields */
>
> @@ -404,14 +405,16 @@ static inline void enable_cs(struct s3c64xx_spi_driver_data *sdd,
> if (sdd->tgl_spi != spi) { /* if last mssg on diff device */
> /* Deselect the last toggled device */
> cs = sdd->tgl_spi->controller_data;
> - gpio_set_value(cs->line,
> - spi->mode & SPI_CS_HIGH ? 0 : 1);
> + if (!(sdd->port_conf->quirks & S3C64XX_SPI_QUIRK_GPIO))
> + gpio_set_value(cs->line,
> + spi->mode & SPI_CS_HIGH ? 0 : 1);
> }
> sdd->tgl_spi = NULL;
> }
>
> cs = spi->controller_data;
> - gpio_set_value(cs->line, spi->mode & SPI_CS_HIGH ? 1 : 0);
> + if (!(sdd->port_conf->quirks & S3C64XX_SPI_QUIRK_GPIO))
> + gpio_set_value(cs->line, spi->mode & SPI_CS_HIGH ? 1 : 0);
>
> /* Start the signals */
> writel(0, sdd->regs + S3C64XX_SPI_SLAVE_SEL);
> @@ -503,7 +506,8 @@ static inline void disable_cs(struct s3c64xx_spi_driver_data *sdd,
> if (sdd->tgl_spi == spi)
> sdd->tgl_spi = NULL;
>
> - gpio_set_value(cs->line, spi->mode & SPI_CS_HIGH ? 0 : 1);
> + if (!(sdd->port_conf->quirks & S3C64XX_SPI_QUIRK_GPIO))
> + gpio_set_value(cs->line, spi->mode & SPI_CS_HIGH ? 0 : 1);
>
> /* Quiese the signals */
> writel(S3C64XX_SPI_SLAVE_SIG_INACT,
> @@ -842,7 +846,10 @@ static struct s3c64xx_spi_csinfo *s3c64xx_get_slave_ctrldata(
> return ERR_PTR(-ENOMEM);
> }
>
> - cs->line = of_get_named_gpio(data_np, "cs-gpio", 0);
> + /* In case of dedicated cs pin skip the gpio initialization */
> + if (!(sdd->port_conf->quirks & S3C64XX_SPI_QUIRK_GPIO))
> + cs->line = of_get_named_gpio(data_np, "cs-gpio", 0);
> +
> if (!gpio_is_valid(cs->line)) {
> dev_err(&spi->dev, "chip select gpio is not specified or "
> "invalid\n");
> @@ -883,7 +890,7 @@ static int s3c64xx_spi_setup(struct spi_device *spi)
> return -ENODEV;
> }
>
> - if (!spi_get_ctldata(spi)) {
> + if (!(sdd->port_conf->quirks & S3C64XX_SPI_QUIRK_GPIO)) {
> err = gpio_request_one(cs->line, GPIOF_OUT_INIT_HIGH,
> dev_name(&spi->dev));
> if (err) {
> @@ -892,9 +899,11 @@ static int s3c64xx_spi_setup(struct spi_device *spi)
> cs->line, err);
> goto err_gpio_req;
> }
> - spi_set_ctldata(spi, cs);
> }
>
> + if (!spi_get_ctldata(spi))
> + spi_set_ctldata(spi, cs);
> +
> sci = sdd->cntrlr_info;
>
> spin_lock_irqsave(&sdd->lock, flags);
> @@ -979,8 +988,11 @@ err_gpio_req:
> static void s3c64xx_spi_cleanup(struct spi_device *spi)
> {
> struct s3c64xx_spi_csinfo *cs = spi_get_ctldata(spi);
> + struct s3c64xx_spi_driver_data *sdd;
> +
> + sdd = spi_master_get_devdata(spi->master);
>
> - if (cs) {
> + if (!(sdd->port_conf->quirks & S3C64XX_SPI_QUIRK_GPIO) && cs) {
> gpio_free(cs->line);
> if (spi->dev.of_node)
> kfree(cs);
> @@ -1107,6 +1119,13 @@ static int s3c64xx_spi_parse_dt_gpio(struct s3c64xx_spi_driver_data *sdd)
> struct device *dev = &sdd->pdev->dev;
> int idx, gpio, ret;
>
> + /*
> + * If cs is not controlled by gpio, and
> + * the SoC uses internal dedicated pins
> + */
> + if (sdd->port_conf->quirks & S3C64XX_SPI_QUIRK_GPIO)
> + return 0;
> +
> /* find gpios for mosi, miso and clock lines */
> for (idx = 0; idx < 3; idx++) {
> gpio = of_get_gpio(dev->of_node, idx);
> @@ -1133,6 +1152,10 @@ free_gpio:
> static void s3c64xx_spi_dt_gpio_free(struct s3c64xx_spi_driver_data *sdd)
> {
> unsigned int idx;
> +
> + if (sdd->port_conf->quirks & S3C64XX_SPI_QUIRK_GPIO)
> + return;
> +
> for (idx = 0; idx < 3; idx++)
> gpio_free(sdd->gpios[idx]);
> }
> --
> 1.7.10.4
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Grant Likely, B.Sc, P.Eng.
Secret Lab Technologies, Ltd.
------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
next prev parent reply other threads:[~2013-02-06 10:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-05 23:09 [PATCH 0/4] Add polling support for 64xx spi controller Girish K S
[not found] ` <1360105784-12282-1-git-send-email-ks.giri-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2013-02-05 23:09 ` [PATCH 1/4] spi: s3c64xx: modified error interrupt handling and init Girish K S
[not found] ` <1360105784-12282-2-git-send-email-ks.giri-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2013-02-06 10:26 ` Grant Likely
2013-02-06 20:12 ` Girish KS
[not found] ` <CAKrE-KdX+Nxk0X4xdz6Dx3WVtOpV+ms+gPB-Dq-MwZwetyZ5Nw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-02-06 23:48 ` Grant Likely
[not found] ` <CACxGe6uOaoRbtuovEsA87d-MtCbGNd3KZCeHXbBQaEpp6NZ7fA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-02-07 0:33 ` Girish KS
2013-02-08 1:04 ` Girish KS
[not found] ` <CAKrE-KfvywLa4xTwCGzan9OfevzBdY8Z2EO2Mc2VaFm5y0XEzg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-02-08 8:16 ` Girish KS
2013-02-07 11:09 ` Tomasz Figa
2013-02-07 17:46 ` Girish KS
[not found] ` <CAKrE-KfyGCi_+FozSpGTy0A0VJP=Jq-1SHmvKJU02iJKWHcvLQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-02-08 8:33 ` Tomasz Figa
2013-02-08 8:58 ` Girish KS
[not found] ` <CAKrE-Kd-mNv=_YkM7GjicgDx=0hqbp5B6qwEvcRzhuSibRNaZA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-02-08 9:26 ` Girish KS
2013-02-05 23:09 ` [PATCH 3/4] spi: s3c64xx: add gpio quirk for controller Girish K S
[not found] ` <1360105784-12282-4-git-send-email-ks.giri-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2013-02-06 10:40 ` Grant Likely [this message]
2013-02-06 22:38 ` Girish KS
2013-02-07 11:55 ` Mark Brown
[not found] ` <20130207115546.GA3801-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-02-07 18:54 ` Girish KS
2013-02-08 13:17 ` Mark Brown
2013-02-05 23:09 ` [PATCH 4/4] spi: s3c64xx: add support for exynos5440 spi Girish K S
2013-02-05 23:09 ` [PATCH 2/4] spi: s3c64xx: added support for polling mode Girish K S
[not found] ` <1360105784-12282-3-git-send-email-ks.giri-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2013-02-06 10:35 ` Grant Likely
2013-02-06 22:04 ` Girish KS
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=20130206104000.98E803E1510@localhost \
--to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
--cc=girishks2000-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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).