From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Bartosz Golaszewski <brgl@kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
Linus Walleij <linusw@kernel.org>,
Andy Shevchenko <andy@kernel.org>,
Peter Tyser <ptyser@xes-inc.com>,
Lixu Zhang <lixu.zhang@intel.com>,
Mika Westerberg <westeri@kernel.org>,
Israel Cepeda <israel.a.cepeda.lopez@intel.com>,
Hans de Goede <hansg@kernel.org>,
Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@intel.com>,
Alan Borzeszkowski <alan.borzeszkowski@linux.intel.com>
Subject: Re: [PATCH RFC] gpio: move intel drivers into their own directory
Date: Tue, 29 Sep 2026 22:53:40 +0300 [thread overview]
Message-ID: <arwXRBDZI5ottKmL@kekkonen.localdomain> (raw)
In-Reply-To: <CAHp75VcpK-Kv2tfR+fAuTWE15b2j34M8X+_UEkBGz_V=QJPbEA@mail.gmail.com>
Hi Andy, Bartosz,
On Tue, Sep 29, 2026 at 06:09:20PM +0300, Andy Shevchenko wrote:
> On Tue, Sep 29, 2026 at 5:05 PM Bartosz Golaszewski <brgl@kernel.org> wrote:
> > On Tue, Sep 29, 2026 at 3:31 PM Andy Shevchenko
> > <andy.shevchenko@gmail.com> wrote:
>
> > > > > Just send it now, in any case my series is blocked as I have not seen
> > > > > a consensus on what to do. Or do we? Bart, Sakari?
> > > >
> > > > If I didn't make myself clear: I would love it if there was a single source
> > > > of intel GPIO pull-requests (most likely Andy) for *all* intel GPIO drivers
> > > > even if they have additional reviewers. I'd also love for them to live in
> > > > a single subdirectory at drivers/gpio/intel/. Otherwise, it's still chaos like
> > > > right now, just worse.
> > > >
> > > > This is in line with pinctrl vendor directories. I also don't see a reason for
> > > > moving Kconfig options into their own vendor submenus if we keep the top-level
> > > > entries sorted by driver type.
> > >
> > > So, as of now it doesn't seem like an agreement among all parties. My
> > > opinion is that it's good to have PMIC be separated from the other
> > > code, although I don't know if the camera PMIC GPIO driver that is
> > > used with IPUx is good to go under the intel/pmic subfolder. I also
> > > believe that camera related drivers are the best to be handled by the
> > > media tree (as it's done, exempli gratia, for int3472).
> > >
> > > At the end of the day you will have a single PR from me, but it won't
> > > include camera stuff unless Sakari agrees to send a PR to me (which I
> > > think won't be the case).
That'd work, sure, but there are often dependencies between all three USBIO
related drivers (main, I²C and GPIO) so they'll all go typically via usb
tree in that case. Having them all be merged via the media tree would
require more discussions.
> >
> > I thought we agreed usbio would be moved out of drivers/gpio/ and into
> > media? That leaves intel/pmic as the only subdirectory IIUC.
>
> Hmm... I cited the int3472 MAINTAINERS record to point exactly on the
> variant where it's left under drivers/gpio. Also IIUC Hans' opinion is
> that GPIO drivers even being USB GPIO expanders for camera are still
> GPIOs.
Indeed.
--
Kind regards,
Sakari Ailus
next prev parent reply other threads:[~2026-09-29 19:53 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 10:22 Bartosz Golaszewski
2026-09-25 10:48 ` Andy Shevchenko
2026-09-25 11:42 ` Hans de Goede
2026-09-25 12:48 ` Andy Shevchenko
2026-09-25 14:39 ` Andy Shevchenko
2026-09-25 12:54 ` Mika Westerberg
2026-09-25 14:34 ` Andy Shevchenko
2026-09-26 10:07 ` Mika Westerberg
2026-09-28 8:15 ` Andy Shevchenko
2026-09-28 11:13 ` Bartosz Golaszewski
2026-09-28 11:34 ` Andy Shevchenko
2026-09-28 12:25 ` Bartosz Golaszewski
2026-09-28 13:12 ` Andy Shevchenko
2026-09-28 14:13 ` Bartosz Golaszewski
2026-09-28 14:33 ` Hans de Goede
2026-09-28 15:12 ` Andy Shevchenko
2026-09-28 17:06 ` Bartosz Golaszewski
2026-09-28 18:11 ` Andy Shevchenko
2026-09-28 12:34 ` Mika Westerberg
2026-09-28 13:13 ` Andy Shevchenko
2026-09-29 12:15 ` Alan Borzeszkowski
2026-09-29 12:45 ` Andy Shevchenko
2026-09-29 12:51 ` Bartosz Golaszewski
2026-09-29 13:31 ` Andy Shevchenko
2026-09-29 14:05 ` Bartosz Golaszewski
2026-09-29 15:09 ` Andy Shevchenko
2026-09-29 19:53 ` Sakari Ailus [this message]
2026-09-30 8:08 ` Andy Shevchenko
2026-09-30 8:10 ` Andy Shevchenko
2026-09-30 19:51 ` Bartosz Golaszewski
2026-09-28 12:35 ` Hans de Goede
2026-09-28 13:10 ` Andy Shevchenko
2026-09-28 21:20 ` Sakari Ailus
2026-09-25 16:17 ` Linus Walleij
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=arwXRBDZI5ottKmL@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=alan.borzeszkowski@linux.intel.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=andy@kernel.org \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=brgl@kernel.org \
--cc=hansg@kernel.org \
--cc=israel.a.cepeda.lopez@intel.com \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lixu.zhang@intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=ptyser@xes-inc.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--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 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®