[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VcoiCVrdEMDrDC8qVZZwYgLTdi50tBxB4BQk=tWQWyOBA@mail.gmail.com>
Date: Wed, 13 Jul 2022 19:50:54 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Conor.Dooley@...rochip.com
Cc: Lewis.Hanly@...rochip.com,
"open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
linux-riscv <linux-riscv@...ts.infradead.org>,
Linus Walleij <linus.walleij@...aro.org>,
Bartosz Golaszewski <brgl@...ev.pl>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Palmer Dabbelt <palmer@...belt.com>,
Marc Zyngier <maz@...nel.org>, Daire.McNamara@...rochip.com
Subject: Re: [PATCH v2 1/1] gpio: mpfs: add polarfire soc gpio support
On Wed, Jul 13, 2022 at 7:44 PM <Conor.Dooley@...rochip.com> wrote:
> On 13/07/2022 12:59, Andy Shevchenko wrote:
> > EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
...
> >> +#define BYTE_BOUNDARY 0x04
> >
> > Without namespace?
>
> Does byte_boundary even need to be defined?
> is incrementing an address by 0x4 not kinda obvious on its own
> as to what it is doing?
The less magic is the better.
Btw, have you considered gpio-regmap? Can it be utilized here?
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists