public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Raag Jadav <raag.jadav@intel.com>
Cc: gregkh@linuxfoundation.org, david.m.ertman@intel.com,
	ira.weiny@intel.com, andriy.shevchenko@linux.intel.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] mfd: core: Support auxiliary device
Date: Fri, 4 Apr 2025 16:35:52 +0100	[thread overview]
Message-ID: <20250404153552.GE372032@google.com> (raw)
In-Reply-To: <20250403110053.1274521-1-raag.jadav@intel.com>

On Thu, 03 Apr 2025, Raag Jadav wrote:

> Extend MFD subsystem to support auxiliary child device. This is useful for
> MFD usecases where parent device is on a discoverable bus and doesn't fit
> into the platform device criteria. Current support is limited to just PCI
> devices, but this can be further extended to support other types like USB
> in the future.
> 
> Signed-off-by: Raag Jadav <raag.jadav@intel.com>
> ---
> 
> I've been cooking this on my spare time during merge window. I'm not
> very confident about this but thought I'd share it. It might be
> controversial since I stole quite a bit from platform infrastructure,
> so please consider this an RFC and let's discuss how to approach this.
> 
> More discussion at [*].
> [*] https://lore.kernel.org/r/2025032609-query-limit-491b@gregkh
> 
> A few things that are still open,
> 
> 1. Since we're doing it for PCI devices (Greg's recommendation), how do
>    we force the existing ones to use their original platform path?
> 
> 2. Should we allow auxiliary drivers to manage their own resources
>    (MEM, IO, IRQ etc)?
> 
>  drivers/base/auxiliary.c      |  23 ++++++
>  drivers/mfd/mfd-core.c        | 137 +++++++++++++++++++++++++++++++---
>  include/linux/auxiliary_bus.h |   7 ++
>  3 files changed, 156 insertions(+), 11 deletions(-)

Honestly, I thought I was going to hate this more than I do.

Besides the obvious duplication of existing code, I think the premise is okay.

I have always viewed the auxiliary bus as an alternative to MFD, rather
than an alternative to platform, but I see where you're coming from with this.

-- 
Lee Jones [李琼斯]

      parent reply	other threads:[~2025-04-04 15:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-03 11:00 [PATCH v1] mfd: core: Support auxiliary device Raag Jadav
2025-04-03 14:02 ` Greg KH
2025-04-03 14:16   ` Andy Shevchenko
2025-04-03 14:19     ` Andy Shevchenko
2025-04-03 14:23       ` Greg KH
2025-04-03 14:26         ` Andy Shevchenko
2025-04-03 14:31           ` Raag Jadav
2025-04-04 11:36   ` Raag Jadav
2025-04-04 12:29     ` Andy Shevchenko
2025-04-04 12:35       ` Raag Jadav
2025-04-04 13:00         ` Andy Shevchenko
2025-04-04 13:39           ` Raag Jadav
2025-04-04 13:56             ` Andy Shevchenko
2025-04-04 14:47               ` Raag Jadav
2025-04-03 15:11 ` kernel test robot
2025-04-03 15:11 ` kernel test robot
2025-04-03 21:39 ` kernel test robot
2025-04-04 15:35 ` Lee Jones [this message]

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=20250404153552.GE372032@google.com \
    --to=lee@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=david.m.ertman@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=ira.weiny@intel.com \
    --cc=linux-kernel@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