[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAMRc=MeCM3iJ4wT6p3h7cxX5_2Kg-xgZUgyGLSscLa+jzH=8Ew@mail.gmail.com>
Date: Tue, 25 Jul 2023 12:01:38 +0200
From: Bartosz Golaszewski <brgl@...ev.pl>
To: Samuel Holland <samuel.holland@...ive.com>
Cc: Linus Walleij <linus.walleij@...aro.org>,
Andy Shevchenko <andy@...nel.org>,
Emil Renner Berthing <emil.renner.berthing@...onical.com>,
Rob Herring <robh+dt@...nel.org>,
Frank Rowand <frowand.list@...il.com>,
Palmer Dabbelt <palmer@...belt.com>,
Paul Walmsley <paul.walmsley@...ive.com>,
linux-gpio@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-riscv@...ts.infradead.org
Subject: Re: [PATCH v3 0/4] gpio: sifive: Module support
On Tue, Jul 25, 2023 at 2:40 AM Samuel Holland
<samuel.holland@...ive.com> wrote:
>
> With the call to of_irq_count() removed, the SiFive GPIO driver can be
> built as a module. This helps to minimize the size of a multiplatform
> kernel, and is required by some downstream distributions (Android GKI).
>
> This series removes the rest of the of_* API usage in the process.
>
> Changes in v3:
> - Use dev_fwnode() instead of member access
> - Mention the SIFIVE_GPIO_MAX check in the commit message
> - Keep the variable for the parent IRQ domain
> - Add a comment explaining why the IRQ data lookup will succeed
>
> Changes in v2:
> - Add 3 new patches removing of_* API usage
> - Add MODULE_AUTHOR and MODULE_DESCRIPTION
>
> Samuel Holland (4):
> gpio: sifive: Directly use the device's fwnode
> gpio: sifive: Look up IRQs only once during probe
> gpio: sifive: Get the parent IRQ's domain from its irq_data
> gpio: sifive: Allow building the driver as a module
>
> drivers/gpio/Kconfig | 2 +-
> drivers/gpio/gpio-sifive.c | 47 ++++++++++++++++----------------------
> 2 files changed, 21 insertions(+), 28 deletions(-)
>
> --
> 2.40.1
>
Applied, thanks!
Bartosz
Powered by blists - more mailing lists