All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
	linux-acpi@vger.kernel.org, Bartosz Golaszewski <brgl@bgdev.pl>,
	Mika Westerberg <westeri@kernel.org>,
	Hans de Goede <hdegoede@redhat.com>
Subject: Re: [PATCH v1 0/4] gpiolib: acpi: Split quirks to its own file
Date: Thu, 15 May 2025 11:34:51 +0300	[thread overview]
Message-ID: <20250515083451.GT88033@black.fi.intel.com> (raw)
In-Reply-To: <aCWgBp4ZD5aesvRw@smile.fi.intel.com>

On Thu, May 15, 2025 at 11:04:22AM +0300, Andy Shevchenko wrote:
> On Wed, May 14, 2025 at 06:59:55PM +0300, Mika Westerberg wrote:
> > On Tue, May 13, 2025 at 01:00:30PM +0300, Andy Shevchenko wrote:
> > > The GPIO ACPI helpers use a few quirks which consumes approximately 20%
> > > of the file. Besides that the necessary bits are sparse and being directly
> > > referred. Split them to a separate file. There is no functional change.
> > > 
> > > For the new file I used the Hans' authorship of Hans as he the author of
> > > all those bits (expect very tiny changes made by this series).
> > > 
> > > Hans, please check if it's okay and confirm, or suggest better alternative.
> > > 
> > > Andy Shevchenko (4):
> > >   gpiolib: acpi: Switch to use enum in acpi_gpio_in_ignore_list()
> > >   gpiolib: acpi: Handle deferred list via new API
> > >   gpiolib: acpi: Add acpi_gpio_need_run_edge_events_on_boot() getter
> > >   gpiolib: acpi: Move quirks to a separate file
> > > 
> > >  drivers/gpio/Makefile                         |   1 +
> > >  .../{gpiolib-acpi.c => gpiolib-acpi-core.c}   | 344 +----------------
> > >  drivers/gpio/gpiolib-acpi-quirks.c            | 363 ++++++++++++++++++
> > >  drivers/gpio/gpiolib-acpi.h                   |  15 +
> > 
> > All this -foo-core things look redundant to me. Why not just split it out
> > and call it gpiolib-quirks.c and put there all the quirks not just ACPI? I
> > Don't think we want to have gpiolib-of-quirks.c and gpiolog-swnode-quirks.c
> > and so on.
> 
> That's might be the next step to have for all of them, but these are ACPI
> specific. In any case they can't be put to gpiolib-quirks.c due to module
> parameters. If we do that we will need a dirty hack to support old module
> parameters (see 8250 how it's done there, and even author of that didn't like
> the approach).

Hmm, how does it affect module paremeters? I thought they are
gpiolib.something as all these object files are linked to it?

At least can we drop the gpiolib-acpi-core.c rename?

  reply	other threads:[~2025-05-15  8:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-13 10:00 [PATCH v1 0/4] gpiolib: acpi: Split quirks to its own file Andy Shevchenko
2025-05-13 10:00 ` [PATCH v1 1/4] gpiolib: acpi: Switch to use enum in acpi_gpio_in_ignore_list() Andy Shevchenko
2025-05-13 10:00 ` [PATCH v1 2/4] gpiolib: acpi: Handle deferred list via new API Andy Shevchenko
2025-05-13 10:00 ` [PATCH v1 3/4] gpiolib: acpi: Add acpi_gpio_need_run_edge_events_on_boot() getter Andy Shevchenko
2025-05-13 10:00 ` [PATCH v1 4/4] gpiolib: acpi: Move quirks to a separate file Andy Shevchenko
2025-05-14 10:14 ` [PATCH v1 0/4] gpiolib: acpi: Split quirks to its own file Hans de Goede
2025-05-14 15:59 ` Mika Westerberg
2025-05-15  7:21   ` Linus Walleij
2025-05-15  8:16     ` Andy Shevchenko
2025-05-15  8:04   ` Andy Shevchenko
2025-05-15  8:34     ` Mika Westerberg [this message]
2025-05-15  8:41       ` Andy Shevchenko
2025-05-15  8:47         ` Mika Westerberg
2025-05-15  8:58           ` Andy Shevchenko
2025-05-15  9:31             ` Mika Westerberg
2025-05-15 10:02               ` Andy Shevchenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250515083451.GT88033@black.fi.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=brgl@bgdev.pl \
    --cc=hdegoede@redhat.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=westeri@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.