From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Raag Jadav <raag.jadav@intel.com>,
hansg@kernel.org, ilpo.jarvinen@linux.intel.com,
linus.walleij@linaro.org, platform-driver-x86@vger.kernel.org,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 2/2] gpio: elkhartlake: Convert to auxiliary driver
Date: Wed, 29 Oct 2025 13:13:30 +0200 [thread overview]
Message-ID: <aQH22oSGllHuOkBI@smile.fi.intel.com> (raw)
In-Reply-To: <CAMRc=Mcz3df6KUx6q5MLGfB06jQhBTGfhCM7yovHBE3k1vn+nQ@mail.gmail.com>
On Wed, Oct 29, 2025 at 11:40:17AM +0100, Bartosz Golaszewski wrote:
> On Wed, Oct 29, 2025 at 7:21 AM Raag Jadav <raag.jadav@intel.com> wrote:
> >
> > Since PCI device should not be abusing platform device, MFD parent to
> > platform child path is no longer being pursued for this driver. Convert
> > it to auxiliary driver, which will be used by EHL PSE auxiliary device.
> >
> Are there build-time dependencies between this and patch 1/2?
There is a new header file which is shared IIUC. So, yes.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-10-29 11:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 6:20 [PATCH v1 0/2] Introduce Intel Elkhart Lake PSE I/O Raag Jadav
2025-10-29 6:20 ` [PATCH v1 1/2] platform/x86/intel: " Raag Jadav
2025-10-29 8:36 ` Andy Shevchenko
2025-10-31 9:34 ` Raag Jadav
2025-10-31 10:02 ` Andy Shevchenko
2025-10-31 11:59 ` Raag Jadav
2025-10-31 12:49 ` Andy Shevchenko
2025-10-29 6:20 ` [PATCH v1 2/2] gpio: elkhartlake: Convert to auxiliary driver Raag Jadav
2025-10-29 8:38 ` Andy Shevchenko
2025-10-29 10:40 ` Bartosz Golaszewski
2025-10-29 11:13 ` Andy Shevchenko [this message]
2025-10-29 11:16 ` Bartosz Golaszewski
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=aQH22oSGllHuOkBI@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=brgl@bgdev.pl \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=raag.jadav@intel.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;
as well as URLs for NNTP newsgroup(s).