[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6F87890CF0F5204F892DEA1EF0D77A59725BF44A@FMSMSX114.amr.corp.intel.com>
Date: Mon, 12 Jun 2017 09:14:16 +0000
From: "Mani, Rajmohan" <rajmohan.mani@...el.com>
To: Andy Shevchenko <andy.shevchenko@...il.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
Lee Jones <lee.jones@...aro.org>,
Linus Walleij <linus.walleij@...aro.org>,
"Alexandre Courbot" <gnurou@...il.com>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
"Len Brown" <lenb@...nel.org>
Subject: RE: [PATCH v2 2/3] gpio: Add support for TPS68470 GPIOs
Hi Andy,
> Subject: Re: [PATCH v2 2/3] gpio: Add support for TPS68470 GPIOs
>
> On Sun, Jun 11, 2017 at 9:09 AM, Rajmohan Mani
> <rajmohan.mani@...el.com> wrote:
> > This patch adds support for TPS68470 GPIOs.
> > There are 7 GPIOs and a few sensor related GPIOs.
> > These GPIOs can be requested and configured as appropriate.
>
> Main points (some I already told in an answer to Sakari's mail):
> 1. Consider 2 GPIO chips over 1.
I am looking into this.
> 2. Fix FIXME(s).
Leaving this on, until I see how this can be fixed.
> 3. If there is hardware bug we should work around it must be clarified.
Ack
If this is about initializing the GPIOs with zero, I have removed this code for now.
> 4. You missed Linus' comments here (switch to the data pointer inside GPIO
> chip and remove platform driver data stuff from the driver).
>
I have fixed this with v3
Powered by blists - more mailing lists