[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VcXpXZ+Ue7Cz0ORupgUjLTCiEwFYb2cs9kePX6EbEs-+w@mail.gmail.com>
Date: Tue, 10 Apr 2018 21:08:39 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: "H. Nikolaus Schaller" <hns@...delico.com>
Cc: Kumar Gala <galak@...eaurora.org>,
Rob Herring <robh+dt@...nel.org>,
Pawel Moll <pawel.moll@....com>,
Mark Rutland <mark.rutland@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Linus Walleij <linus.walleij@...aro.org>,
Alexandre Courbot <gnurou@...il.com>,
devicetree <devicetree@...r.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Discussions about the Letux Kernel
<letux-kernel@...nphoenux.org>, kernel@...a-handheld.com
Subject: Re: [PATCH v3 1/4] gpio: pca953x: set the PCA_PCAL flag also when
matching by DT
On Tue, Apr 10, 2018 at 7:07 PM, H. Nikolaus Schaller <hns@...delico.com> wrote:
> The of_device_table is missing the PCA_PCAL flag so the
> pcal6524 would be operated in tca6424 compatibility mode which
> does not handle the new interrupt mask registers.
> + { .compatible = "nxp,pcal6524", .data = OF_953X(24, PCA_INT |
> + PCA_PCAL), },
> + { .compatible = "nxp,pcal9555a", .data = OF_953X(16, PCA_INT |
> + PCA_PCAL), },
Sorry didn't comment this earlier, though I think one line still
better to read disregard of 80 char limit.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists