From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Junjie Cao <junjie.cao@linux.dev>
Cc: brgl@kernel.org, linusw@kernel.org, ptyser@xes-inc.com,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 3/5] gpio: Move Intel PCH type of GPIO drivers to the intel subfolder
Date: Sun, 4 Oct 2026 11:28:52 +0300 [thread overview]
Message-ID: <asIORD7gXY3VJ__Z@ashevche-desk.local> (raw)
In-Reply-To: <20261004054809.24211-1-junjie.cao@linux.dev>
On Sun, Oct 04, 2026 at 05:48:09AM +0000, Junjie Cao wrote:
> One small note: moving GPIO_ICH under "if PCI"
> also excludes its existing COMPILE_TEST &&
> HAS_IOPORT path when PCI=n.
>
> I checked that gpio-ich.o builds with W=1 in that
> configuration before the move. Could we keep
> GPIO_ICH outside the PCI conditional to preserve
> that coverage?
For what purpose? Yes, it might compile with PCI=n, but it makes no functional
sense. Note, that currently Kconfig puts (mistakenly!) this driver as memory
mapped GPIO driver, which is true, but not the whole picture. This is part of
MFD driver, that is solely PCI and never been anything else. My series rectifies
(or, if you wish, clarifies) this.
Also note, that having compile test enabled on PCI devices with PCI=n may lead
to build issues as PCI doesn't have full set of stubs (yet?). It's not directly
related to _this_ driver, but MFD parent one might be the case.
But, of course, it's not a big deal to add " || COMPILE_TEST" to that "if PCI".
I will consider doing that if we move forward with this series at all. Currently
there is no consensus on what to do with some drivers.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-10-04 8:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 15:57 [PATCH v1 0/5] gpio: Move most of the Intel GPIO to the dedicated folder Andy Shevchenko
2026-09-25 15:57 ` [PATCH v1 1/5] gpio: Move Intel GPIO drivers to the dedicated subfolder Andy Shevchenko
2026-09-26 5:42 ` Raag Jadav
2026-09-26 16:55 ` Andy Shevchenko
2026-09-25 15:57 ` [PATCH v1 2/5] gpio: Move Intel PMIC " Andy Shevchenko
2026-09-28 17:10 ` Bartosz Golaszewski
2026-09-28 18:07 ` Andy Shevchenko
2026-09-25 15:57 ` [PATCH v1 3/5] gpio: Move Intel PCH type of GPIO drivers to the intel subfolder Andy Shevchenko
2026-10-04 5:48 ` Junjie Cao
2026-10-04 8:28 ` Andy Shevchenko [this message]
2026-09-25 15:57 ` [PATCH v1 4/5] gpio: Move Intel Sodaville GPIO driver " Andy Shevchenko
2026-09-25 15:57 ` [PATCH v1 5/5] gpio: Move Intel vGPIO " 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=asIORD7gXY3VJ__Z@ashevche-desk.local \
--to=andriy.shevchenko@linux.intel.com \
--cc=brgl@kernel.org \
--cc=junjie.cao@linux.dev \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ptyser@xes-inc.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®