mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Hans de Goede <hansg@kernel.org>,
	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>,
	Alan Borzeszkowski <alan.borzeszkowski@linux.intel.com>,
	Mika Westerberg <westeri@kernel.org>,
	Israel Cepeda <israel.a.cepeda.lopez@intel.com>,
	Kuppuswamy Sathyanarayanan
	<sathyanarayanan.kuppuswamy@linux.intel.com>,
	linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
	Andy Shevchenko <andriy.shevchenko@intel.com>,
	Miguel Vadillo <miguel.vadillo@intel.com>
Subject: Re: [PATCH RFC] gpio: move intel drivers into their own directory
Date: Tue, 29 Sep 2026 00:20:12 +0300	[thread overview]
Message-ID: <arraDNEO5NuxgTz6@kekkonen.localdomain> (raw)
In-Reply-To: <CAHp75VeHupSXCBUyoUdPXY-GvBcupQ9kczhr-M3=WLkEzDKyvw@mail.gmail.com>

Hi Andy,

On Mon, Sep 28, 2026 at 04:10:41PM +0300, Andy Shevchenko wrote:
> On Mon, Sep 28, 2026 at 3:35 PM Hans de Goede <hansg@kernel.org> wrote:
> > On 28-Sep-26 13:34, Andy Shevchenko wrote:
> > > On Mon, Sep 28, 2026 at 2:13 PM Bartosz Golaszewski <brgl@kernel.org> wrote:
> > >> On Sat, 26 Sep 2026 12:07:27 +0200, Mika Westerberg
> > >> <mika.westerberg@linux.intel.com> said:
> > >>> On Fri, Sep 25, 2026 at 05:34:53PM +0300, Andy Shevchenko wrote:
> > >>>> On Fri, Sep 25, 2026 at 02:54:33PM +0200, Mika Westerberg wrote:
> > >>>>> On Fri, Sep 25, 2026 at 01:48:05PM +0300, Andy Shevchenko wrote:
> > >>>>>> On Fri, Sep 25, 2026 at 12:22:15PM +0200, Bartosz Golaszewski wrote:
> 
> ...
> 
> > >>>>>>>  drivers/gpio/{ => intel}/gpio-graniterapids.c   |  0
> > >>>>>>>  drivers/gpio/{ => intel}/gpio-novalake-events.c |  0
> > >>>>>>
> > >>>>>> These are interesting drivers, not sure where to put them
> > >>>>>
> > >>>>> IMHO they should be there too. We are maintaining them both.
> > >>>>
> > >>>> Do you send PRs to Bart or you just rely on him to take the patches?
> > >>>
> > >>> I don't expect these two drives to get too much attention, and they could
> > >>> be contained nicely inside intel folder and that would help Bart to
> > >>> identify that these are Intel drivers. So your bandwidth would not suffer
> > >>> even if these two are added there. Your call.
> > >>
> > >> I'd like to avoid a situation where we have Andy's Intel drivers under
> > >> drivers/gpio/intel/ and other Intel drivers under drivers/gpio/. I'd prefer
> > >> to move all of intel GPIO drivers into drivers/gpio/intel/ and have Andy
> > >> gather changes to them if he agrees.
> > >
> > > Okay, we have two parts missing:
> > > - Nova Lake driver (I would need Adam or Mika to step in as at least a
> > > designated reviewer for that)
> > > - USB IO (I think we need to agree which tree it will go through, my
> > > bet that media tree is the best), for that we need Hans' consent
> >
> > Routing the USBIO / LCJA GPIO drivers to the media-tree, with
> > Sakari likely doing the merging for both works for me.
> 
> Sure, Sakari, would it work for you?

Yes.

That being said, the USBIO driver(s) come in three parts, this one (GPIO),
I²C and the main USB USBIO driver. Patches (or at least the set they're in)
often touch more than one and then they're routed through the USB tree in
practice. It'd be practical all would be merged via the media tree, unless
there are dependencies to other parts of the respective tree.

Perhaps we should still do this to GPIO first and then think about the
rest.

Also cc Miguel.

-- 
Kind regards,

Sakari Ailus

  reply	other threads:[~2026-09-28 21:20 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
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 [this message]
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=arraDNEO5NuxgTz6@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=miguel.vadillo@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®