[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <CT0AXYC8EEP6.2PVKT3BWND8AN@burritosblues>
Date: Wed, 31 May 2023 09:58:32 +0200
From: "Esteban Blanc" <eblanc@...libre.com>
To: "Andy Shevchenko" <andy.shevchenko@...il.com>
Cc: <linus.walleij@...aro.org>, <lgirdwood@...il.com>,
<broonie@...nel.org>, <a.zummo@...ertech.it>,
<alexandre.belloni@...tlin.com>, <linux-kernel@...r.kernel.org>,
<linux-gpio@...r.kernel.org>, <linux-rtc@...r.kernel.org>,
<jpanis@...libre.com>, <jneanne@...libre.com>,
<aseketeli@...libre.com>, <u-kumar1@...com>
Subject: Re: [PATCH v5 2/3] pinctrl: tps6594: Add driver for TPS6594 pinctrl
and GPIOs
On Fri May 26, 2023 at 8:43 PM CEST, Andy Shevchenko wrote:
> On Thu, May 25, 2023 at 5:07 PM Esteban Blanc <eblanc@...libre.com> wrote:
> > On Tue May 23, 2023 at 9:14 PM CEST, wrote:
> > > Mon, May 22, 2023 at 06:31:14PM +0200, Esteban Blanc kirjoitti:
>
> ...
>
> > > > +// Used to compute register address of GPIO1_CONF to GPIO11_CONF
> > >
> > > This is good.
>
> Btw
>
> the register
Ah yes, thanks.
> and shouldn't it start from GPIO0_CONF (please, double check, my
> memory can do tricks on me)?
On Linux side it is GPIO0 but on datasheet side it is GPIO1_CONF to
GPIO11_CONF. I was referring to the "real" register names (datasheet
ones)
>
> --
> With Best Regards,
> Andy Shevchenko
Powered by blists - more mailing lists