[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdYuj8-q-LbKYCH7dfLzF_10oViLwF3rjxULgmuw6AXYRg@mail.gmail.com>
Date: Tue, 28 Mar 2017 11:40:57 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Neil Armstrong <narmstrong@...libre.com>
Cc: Kevin Hilman <khilman@...libre.com>,
Carlo Caione <carlo@...one.org>,
"open list:ARM/Amlogic Meson..." <linux-amlogic@...ts.infradead.org>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [RFT PATCH 5/6] pinctrl: meson: use gpio-ranges from DT
On Thu, Mar 23, 2017 at 5:27 PM, Neil Armstrong <narmstrong@...libre.com> wrote:
> When trying to add a gpio-hog, we enter a weird loop where the gpio-ranges
> is needed when gpiochip_add_data() is called but in the current implementation
> the ranges are added from the driver afterwards.
>
> A simple solution is to rely on the DR gpio-ranges attribute and remove the
> call to gpiochip_add_pin_range().
>
> Signed-off-by: Neil Armstrong <narmstrong@...libre.com>
Patch applied.
Yours,
Linus Walleij
Powered by blists - more mailing lists