From: Kukjin Kim <kgene.kim@samsung.com>
To: 'Doug Anderson' <dianders@chromium.org>,
broonie@kernel.org,
'Naveen Krishna Chatradhi' <ch.naveen@samsung.com>
Cc: linux-arm-kernel@lists.infradead.org,
spi-devel-general@lists.sourceforge.net,
'linux-samsung-soc' <linux-samsung-soc@vger.kernel.org>,
'Naveen Krishna' <naveenkrishna.ch@gmail.com>,
'Grant Likely' <grant.likely@secretlab.ca>,
'Jaswinder Singh' <jaswinder.singh@linaro.org>,
"'cpgs .'" <cpgs@samsung.com>,
devicetree@vger.kernel.org, 'Tomasz Figa' <t.figa@samsung.com>
Subject: RE: [PATCH 1/3 v5] spi: s3c64xx: fix broken "cs_gpios" usage in the driver
Date: Wed, 25 Jun 2014 20:29:42 +0900 [thread overview]
Message-ID: <03a101cf9068$c2378250$46a686f0$@samsung.com> (raw)
In-Reply-To: <CAD=FV=Ua+P0CBAfNj4SWWMWRKcEFdmh=akwy1-ZWoGOt2P9=cQ@mail.gmail.com>
Doug Anderson wrote:
>
> Mark or Kukjin,
>
Hi,
> On Thu, Jun 12, 2014 at 8:59 PM, Naveen Krishna Chatradhi
> <ch.naveen@samsung.com> wrote:
> > Since, (3146bee spi: s3c64xx: Added provision for dedicated cs pin)
> >
> > spi-s3c64xx.c driver expects
> > 1. chip select gpios from "cs-gpio"(singular) under the
> > "controller-data" node of the client/slave device of the SPI.
> >
> > 2. "cs-gpio"(singular) entry to be present in the SPI device node.
> >
> > Eg of current broken usage:
> > &spi_1 {
> > cs-gpio <>; /* this entry is checked during probe */
> > ...
> > slave_node {
> > controller-data {
> > cs-gpio <&gpioa2 5 0>;
> > /* This field is parsed during .setup() */
> > }
> > };
> > };
> >
> > The following dts files which were using this driver. But,
> > din't have the "cs-gpio" entry under SPI node.
> > -- arch/arm/boot/dts/exynos4210-smdkv310.dts
> > -- arch/arm/boot/dts/exynos4412-trats2.dts
> > -- arch/arm/boot/dts/exynos5250-smdk5250.dts
> >
> > Also, the SPI core and many drivers moved on to using "cs-gpios"
> > from SPI node and removed the gpio handling code from drivers
> > (including spi-s3c64xx.c).
> >
> > Hence, spi-s3c64xx.c is broken since "Jun 21 11:26:12 2013" and
> > considering the time with no compliants about the breakage.
> >
> > We are assuming it is safe to remove the "cs-gpio"(singular) usage
> > from device tree binding of spi-samsung.txt and makes appropriate
> > changes in the driver to use "cs-gpios"(plural) from
> > SPI device node.
> >
> > Signed-off-by: Naveen Krishna Chatradhi <ch.naveen@samsung.com>
> > Acked-by: Rob Herring <robh@kernel.org>
> > Reviewed-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
> > Tested-by: Doug Anderson <dianders@chromium.org>
> > Cc: Tomasz Figa <t.figa@samsung.com>
> > ---
> > Changes since v4:
> > 1. Added reviewed by from Javier and Tested by from Doug
> >
> > Changes since v3:
> > 1. Remove the sdd->cs_gpio and use gpio_is_valid(spi->cs_gpio) instead
> > 2. Keep cs->line only for Non-DT platforms and use spi->cs_gpio
> > for DT platforms
> >
> > .../devicetree/bindings/spi/spi-samsung.txt | 8 ++--
> > drivers/spi/spi-s3c64xx.c | 41 ++++++++------------
> > 2 files changed, 20 insertions(+), 29 deletions(-)
>
> Is one of you two planning to apply (parts 1 and 2)? I know that
> Kukjin needs to handle the part 3 (the .dts files)...
>
Once Mark takes spi driver related patches, I will pick DT related patches into
samsung tree.
> Ideally it seems like it could go to 3.16 since it is a bugfix...
>
I think so but it depends on Mark's comments ;-)
Thanks,
Kukjin
next prev parent reply other threads:[~2014-06-25 11:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 3:59 [PATCH 1/3 v5] spi: s3c64xx: fix broken "cs_gpios" usage in the driver Naveen Krishna Chatradhi
2014-06-13 3:59 ` [PATCH 2/3 v5] spi: s3c64xx: for DT platofrms always get the chipselect info from DT node Naveen Krishna Chatradhi
2014-06-13 3:59 ` [PATCH 3/3 v5] ARM: DTS: fix the chip select gpios definition in the SPI nodes Naveen Krishna Chatradhi
2014-06-20 21:18 ` [PATCH 1/3 v5] spi: s3c64xx: fix broken "cs_gpios" usage in the driver Doug Anderson
2014-06-21 9:51 ` Mark Brown
2014-06-21 17:23 ` Naveen Krishna Ch
2014-06-22 10:35 ` Mark Brown
2014-06-25 11:29 ` Kukjin Kim [this message]
2014-07-02 16:56 ` Mark Brown
2014-07-07 6:21 ` Naveen Krishna Ch
2014-07-07 7:32 ` Mark Brown
2014-07-07 8:31 ` Naveen Krishna Ch
2014-07-07 11:22 ` Javier Martinez Canillas
2014-07-11 11:04 ` Javier Martinez Canillas
2014-07-11 13:48 ` 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='03a101cf9068$c2378250$46a686f0$@samsung.com' \
--to=kgene.kim@samsung.com \
--cc=broonie@kernel.org \
--cc=ch.naveen@samsung.com \
--cc=cpgs@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=grant.likely@secretlab.ca \
--cc=jaswinder.singh@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=naveenkrishna.ch@gmail.com \
--cc=spi-devel-general@lists.sourceforge.net \
--cc=t.figa@samsung.com \
/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).