linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: Caesar Wang <wxt@rock-chips.com>
Cc: linus.walleij@linaro.org, linux-rockchip@lists.infradead.org,
	linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH] pinctrl: rockchip: add support the get_direction
Date: Mon, 14 Mar 2016 23:36:55 +0100	[thread overview]
Message-ID: <2329775.GrlpyGFbsF@diego> (raw)
In-Reply-To: <1457935279-7881-1-git-send-email-wxt@rock-chips.com>

Hi Caesar,

Am Montag, 14. März 2016, 14:01:19 schrieb Caesar Wang:
> This patch adds the get_direction to support the gpio
> interface.
> 
> The gpio direction is not used on rockchip platform when use the gpio
> debugfs.
> 
> Tested on kylin board. (RK3036 SoCs)
> The repro steps:
> $/sys/class/gpio/
> echo 53 > export
> $/sys/class/gpio/gpio53# cat direction
> in
> In general, the gpio53 should be out value, but the direction is the
> default value 'in',  since the get_direction didn't supported in rockchip
> pinctrl.
> 
> So, we should add this patch to support it.
> 
> Reported-by: Jeffy Chen <jeffy.chen@rock-chips.com>
> Signed-off-by: Caesar Wang <wxt@rock-chips.com>
> Cc: Linus Walleij <linus.walleij@linaro.org>
> Cc: Heiko Stuebner <heiko@sntech.de>
> Cc: linux-gpio@vger.kernel.org
> Cc: linux-rockchip@lists.infradead.org
> 
> ---
> 
> Changes in RESEND:
> - Remove the change-id
> 
>  drivers/pinctrl/pinctrl-rockchip.c | 13 +++++++++++++
>  1 file changed, 13 insertions(+)
> 
> diff --git a/drivers/pinctrl/pinctrl-rockchip.c
> b/drivers/pinctrl/pinctrl-rockchip.c index bf032b9..f22a186 100644
> --- a/drivers/pinctrl/pinctrl-rockchip.c
> +++ b/drivers/pinctrl/pinctrl-rockchip.c
> @@ -1208,6 +1208,18 @@ static int rockchip_pmx_set(struct pinctrl_dev
> *pctldev, unsigned selector, return 0;
>  }
> 
> +static int rockchip_gpio_get_direction(struct gpio_chip *chip, unsigned
> offset) +{
> +	struct rockchip_pin_bank *bank = gpiochip_get_data(chip);
> +	int pin;
> +	u32 data;
> +
> +	pin = offset - chip->base;
> +	data = readl_relaxed(bank->reg_base + GPIO_SWPORT_DDR);
> +
> +	return !!(data & BIT(pin));

TRM (at least rk3288 and rk3036) says for the SWPORT_DDR register:
(data & BIT(pin)) = 0 = input
(data & BIT(pin)) = 1 = output

struct gpio_chip docs [0] says:
@get_direction: returns 0=out, 1=in,


So shouldn't that be
	return !(data & BIT(pin));
with only one "!" instead of two?
Or as happens sometimes, am I just blind? :-)


Thanks
Heiko

[0] http://lxr.free-electrons.com/source/include/linux/gpio/driver.h#L33

--
To unsubscribe from this list: send the line "unsubscribe linux-gpio" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2016-03-14 22:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-14  6:01 [RESEND PATCH] pinctrl: rockchip: add support the get_direction Caesar Wang
2016-03-14 22:36 ` Heiko Stübner [this message]

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=2329775.GrlpyGFbsF@diego \
    --to=heiko@sntech.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=wxt@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;
as well as URLs for NNTP newsgroup(s).