[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD=FV=X4ZC9Nh2z6vtGwH1v3pGefGgeDw-JjA6R06XJmmvOFGQ@mail.gmail.com>
Date: Tue, 21 Oct 2014 09:32:11 -0700
From: Doug Anderson <dianders@...omium.org>
To: Linus Walleij <linus.walleij@...aro.org>,
Heiko Stuebner <heiko@...ech.de>
Cc: Chris Zhong <zyw@...k-chips.com>,
Sonny Rao <sonnyrao@...omium.org>,
linux-rockchip@...ts.infradead.org,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Doug Anderson <dianders@...omium.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/4] pinctrl: rockchip: Don't call pinctrl_gpio_direction_output()
in pin_config_set()
Hi,
On Mon, Oct 20, 2014 at 4:27 PM, Doug Anderson <dianders@...omium.org> wrote:
> @@ -959,9 +968,10 @@ static int rockchip_pinconf_set(struct pinctrl_dev *pctldev, unsigned int pin,
> return rc;
> break;
> case PIN_CONFIG_OUTPUT:
> - rc = rockchip_gpio_direction_output(&bank->gpio_chip,
> - pin - bank->pin_base,
> - arg);
> + rockchip_gpio_set(&bank->gpio_chip,
> + pin - bank->pin_base, arg);
> + rc = _rockchip_pmx_gpio_set_direction(&bank->gpio_chip,
> + pin - bank->pin_base, false);
I think something here is not quite right. I did more testing today
and noticed that I'm getting failures in some cases. I think I've got
the offset wrong, but I'm digging. Please hold off review of this
patch till the next version.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists