public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: jeffy <jeffy.chen@rock-chips.com>
Cc: Shawn Lin <shawn.lin@rock-chips.com>,
	linux-kernel@vger.kernel.org, broonie@kernel.org,
	Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org, briannorris@chromium.org,
	dianders@chromium.org, linux-spi@vger.kernel.org,
	linux-rockchip@lists.infradead.org,
	Rob Herring <robh+dt@kernel.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] spi: rockchip: add support for "cs-gpios" dts property
Date: Mon, 12 Jun 2017 10:36:38 +0200	[thread overview]
Message-ID: <4418523.E0t9k04HOG@diego> (raw)
In-Reply-To: <593E501F.5060906@rock-chips.com>

Am Montag, 12. Juni 2017, 16:26:07 CEST schrieb jeffy:
> Hi Shawn,
> 
> On 06/12/2017 03:15 PM, Shawn Lin wrote:
> > Hi Jeffy,
> > 
> > On 2017/6/12 14:14, Jeffy Chen wrote:
> >> Support using "cs-gpios" property to specify cs gpios.
> >> 
> >> Signed-off-by: Jeffy Chen <jeffy.chen@rock-chips.com>
> >> ---
> >> 
> >>   .../devicetree/bindings/spi/spi-rockchip.txt       |  2 +
> >>   drivers/spi/spi-rockchip.c                         | 52
> >> 
> >> ++++++++++++++++++++++
> >> 
> >>   2 files changed, 54 insertions(+)
> >> 
> >> diff --git a/Documentation/devicetree/bindings/spi/spi-rockchip.txt
> >> b/Documentation/devicetree/bindings/spi/spi-rockchip.txt
> >> index 83da493..02171b2 100644
> >> --- a/Documentation/devicetree/bindings/spi/spi-rockchip.txt
> >> +++ b/Documentation/devicetree/bindings/spi/spi-rockchip.txt
> > 
> > The changes for doc should be another patch, and...
> 
> but i saw others didn't separate them:
> cf9e478 spi: sh-msiof: Add slave mode support
> 23e291c spi: rockchip: support "sleep" pin configuration

it sometimes falls through the cracks, but having dt-binding patches
separate is meant to make it easier on DT-Maintainers to find
patches they need to look at.


> >> +    if (!data->cs_gpio_requested) {
> >> +        ret = gpio_request_one(spi->cs_gpio, flags,
> >> +                       dev_name(&spi->dev));
> >> +        if (!ret)
> >> +            data->cs_gpio_requested = 1;
> >> +    } else
> >> +        ret = gpio_direction_output(spi->cs_gpio, flags);
> > 
> > need brace around 'else' statement. Also I don't see data used
> > elsewhere, so you need these code above.
> 
> ok.
> and the cs_gpio_requested is to mark cs_gpio requested, because the
> setup func might be called multiple times, we only need to request gpio
> at the first time.

Aren't the gpiod* functions meant to be used for new things?
Also you might actually do a bit of error handling there, especially 
EPROBE_DEFER.


Heiko

  parent reply	other threads:[~2017-06-12  8:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-12  6:14 [PATCH 1/2] spi: rockchip: add support for "cs-gpios" dts property Jeffy Chen
2017-06-12  6:14 ` [PATCH 2/2] arm64: dts: rockchip: use cs-gpios for cros_ec_spi Jeffy Chen
2017-06-12  7:15 ` [PATCH 1/2] spi: rockchip: add support for "cs-gpios" dts property Shawn Lin
2017-06-12  8:18   ` Geert Uytterhoeven
2017-06-12  8:48     ` jeffy
2017-06-12 16:38     ` Mark Brown
2017-06-12  8:26   ` jeffy
2017-06-12  8:33     ` jeffy
2017-06-12  8:36     ` Heiko Stübner [this message]
2017-06-12  9:12       ` jeffy
2017-06-12  9:23         ` Heiko Stübner

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=4418523.E0t9k04HOG@diego \
    --to=heiko@sntech.de \
    --cc=briannorris@chromium.org \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=jeffy.chen@rock-chips.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=shawn.lin@rock-chips.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