From: naveenkrishna.ch@gmail.com (Naveen Krishna Ch)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3 v4] spi: s3c64xx: for DT platofrms always get the chipselect info from DT node
Date: Thu, 12 Jun 2014 21:39:06 +0530 [thread overview]
Message-ID: <CAHfPSqCHZbHug7rbxLSApue_kT9ZbxVBpnOBP_z-zynickbQMA@mail.gmail.com> (raw)
In-Reply-To: <5399B3FC.5030605@collabora.co.uk>
Hello Javier,
On 12 June 2014 19:36, Javier Martinez Canillas
<javier.martinez@collabora.co.uk> wrote:
> Hello Naveen,
>
> On 06/12/2014 03:13 PM, Naveen Krishna Chatradhi wrote:
>> Use controller_data structure only for the Non Device tree platforms.
>> For Device tree platforms, always derive the chipselect info from
>> DT node.
>>
>> Signed-off-by: Naveen Krishna Chatradhi <ch.naveen@samsung.com>
>> Cc: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
>> Cc: Doug Anderson <dianders@chromium.org>
>> Cc: Tomasz Figa <t.figa@samsung.com>
>> ---
>> drivers/spi/spi-s3c64xx.c | 11 ++++++-----
>> 1 file changed, 6 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/spi/spi-s3c64xx.c b/drivers/spi/spi-s3c64xx.c
>> index b888c66..f27e15d 100644
>> --- a/drivers/spi/spi-s3c64xx.c
>> +++ b/drivers/spi/spi-s3c64xx.c
>> @@ -795,14 +795,15 @@ static int s3c64xx_spi_setup(struct spi_device *spi)
>> int err;
>>
>> sdd = spi_master_get_devdata(spi->master);
>> - if (!cs && spi->dev.of_node) {
>> + if (spi->dev.of_node) {
>> cs = s3c64xx_get_slave_ctrldata(spi);
>> spi->controller_data = cs;
>> - }
>> -
>> - /* For the non-DT platforms derive chip selects from controller data */
>> - if (!spi->dev.of_node)
>> + } else {
>> + /* For the non-DT platforms derive chip
>> + * selects from controller data
>> + */
>> spi->cs_gpio = cs->line;
>> + }
>>
>> if (IS_ERR_OR_NULL(cs)) {
>> dev_err(&spi->dev, "No CS for SPI(%d)\n", spi->chip_select);
>>
>
> Personally I wouldn't have this change as a separate patch since it's too
> related to what you changed in Patch 1. But it's just a nitpick.
Patch 1/3 seems to be crowded with multiple changes.
Thought, this would keep the changes cleaner.
>
> Reviewed-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
Thanks
>
> Best regards,
> Javier
--
Shine bright,
(: Nav :)
next prev parent reply other threads:[~2014-06-12 16:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 13:13 [PATCH 1/3 v4] spi: s3c64xx: fix broken "cs_gpios" usage in the driver Naveen Krishna Chatradhi
2014-06-12 13:13 ` [PATCH 2/3 v4] spi: s3c64xx: for DT platofrms always get the chipselect info from DT node Naveen Krishna Chatradhi
2014-06-12 14:06 ` Javier Martinez Canillas
2014-06-12 16:09 ` Naveen Krishna Ch [this message]
2014-06-12 23:26 ` Doug Anderson
2014-06-12 13:13 ` [PATCH 3/3 v4] ARM: DTS: fix the chip select gpios definition in the SPI nodes Naveen Krishna Chatradhi
2014-06-12 14:07 ` Javier Martinez Canillas
2014-06-12 23:14 ` Doug Anderson
2014-06-12 14:00 ` [PATCH 1/3 v4] spi: s3c64xx: fix broken "cs_gpios" usage in the driver Javier Martinez Canillas
2014-06-12 16:06 ` Naveen Krishna Ch
2014-06-12 23:25 ` Doug Anderson
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=CAHfPSqCHZbHug7rbxLSApue_kT9ZbxVBpnOBP_z-zynickbQMA@mail.gmail.com \
--to=naveenkrishna.ch@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).