[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdaoiYvcMVCyJJTSyvSZUMAj6QsCcGG3=s4or31r08=hdg@mail.gmail.com>
Date: Thu, 21 Nov 2019 14:47:36 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Rahul Tanwar <rahul.tanwar@...ux.intel.com>
Cc: Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>, Rob Herring <robh@...nel.org>,
Andriy Shevchenko <andriy.shevchenko@...el.com>,
qi-ming.wu@...el.com, yixin.zhu@...ux.intel.com,
cheol.yong.kim@...el.com
Subject: Re: [PATCH v8 1/2] pinctrl: Add pinmux & GPIO controller driver for a
new SoC
Hi Rahul,
On Fri, Nov 15, 2019 at 10:25 AM Rahul Tanwar
<rahul.tanwar@...ux.intel.com> wrote:
> Intel Lightning Mountain SoC has a pinmux controller & GPIO controller IP which
> controls pin multiplexing & configuration including GPIO functions selection &
> GPIO attributes configuration.
>
> This IP is not based on & does not have anything in common with Chassis
> specification. The pinctrl drivers under pinctrl/intel/* are all based upon
> Chassis spec compliant pinctrl IPs. So this driver doesn't fit & can not use
> pinctrl framework under pinctrl/intel/* and it requires a separate new driver.
>
> Add a new GPIO & pin control framework based driver for this IP.
>
> Signed-off-by: Rahul Tanwar <rahul.tanwar@...ux.intel.com>
Thanks a lot for quick iterations and hard work on getting this
driver in such a nice shape in such a short time!
Patch applied for kernel v5.5.
If there are any remaining issues I am sure we can fix them up
in-tree.
Yours,
Linus Walleij
Powered by blists - more mailing lists