From: grygorii.strashko@ti.com (Grygorii Strashko)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] spi: davinci: add support to configure gpio cs through dt
Date: Fri, 01 Aug 2014 18:28:02 +0300 [thread overview]
Message-ID: <53DBB202.1040509@ti.com> (raw)
In-Reply-To: <20140731193515.GO17528@sirena.org.uk>
Hi Mark,
On 07/31/2014 10:35 PM, Mark Brown wrote:
> On Thu, Jul 31, 2014 at 08:33:15PM +0300, Grygorii Strashko wrote:
>
>> + if (np && master->cs_gpios != NULL && spi->cs_gpio >= 0) {
>> + /* SPI core parse and update master->cs_gpio */
>> gpio_chipsel = true;
>> + gpio = spi->cs_gpio;
>> + } else if (pdata->chip_sel &&
>> + chip_sel < pdata->num_chipselect &&
>> + pdata->chip_sel[chip_sel] != SPI_INTERN_CS) {
>> + /* platform data defines chip_sel */
>> + gpio_chipsel = true;
>> + gpio = pdata->chip_sel[chip_sel];
>> + }
>
> This would all be a lot simpler and more direct if you were to arrange
> to use cs_gpio in the struct spi_device, and move you closer to
> converting to use more of the core functionality.
Unfortunately, I'm not sure this is good idea, because this part of
code is used by Davinci arch which is non-DT platform.
As result, this code was kept mostly unchanged.
I can try to rework it, but I'd like to do it as standalone patch.
Is it ok for you?
>
>> + if (np && (master->cs_gpios != NULL) && (spi->cs_gpio >= 0)) {
>> + retval =
>> + gpio_request(spi->cs_gpio, dev_name(&spi->dev));
>> + if (retval) {
>> + dev_err(&spi->dev,
>> + "GPIO %d request failed\n",
>> + spi->cs_gpio);
>> + return -ENODEV;
>> + }
>> + gpio_direction_output(spi->cs_gpio,
>> + !(spi->mode & SPI_CS_HIGH));
>> + internal_cs = false;
>
> It's much better to use gpio_request_one() rather than using
> gpio_request(), it's one function apart from anything else. The above
> is also discarding the return code of gpio_request() meaning it's broken
> for deferred probe. The error code should also appear in the error
> message.
>
Thanks, will update.
Regards,
-grygorii
next prev parent reply other threads:[~2014-08-01 15:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-31 17:33 [PATCH 0/2] spi: davinci: add support for gpio cs through dt Grygorii Strashko
2014-07-31 17:33 ` [PATCH 1/2] spi: davinci: fix to support more than 2 chip selects Grygorii Strashko
2014-07-31 19:35 ` Mark Brown
2014-07-31 17:33 ` [PATCH 2/2] spi: davinci: add support to configure gpio cs through dt Grygorii Strashko
2014-07-31 19:35 ` Mark Brown
2014-08-01 15:28 ` Grygorii Strashko [this message]
2014-08-01 17:29 ` Grygorii Strashko
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=53DBB202.1040509@ti.com \
--to=grygorii.strashko@ti.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).