From: Raag Jadav <raag.jadav@intel.com>
To: Lee Jones <lee@kernel.org>, gregkh@linuxfoundation.org
Cc: david.m.ertman@intel.com, ira.weiny@intel.com,
andriy.shevchenko@linux.intel.com,
mika.westerberg@linux.intel.com, heikki.krogerus@linux.intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] mfd: core: Support auxiliary device
Date: Sat, 3 May 2025 01:01:17 +0300 [thread overview]
Message-ID: <aBVArb-zJ_aqicHW@black.fi.intel.com> (raw)
In-Reply-To: <20250501125028.GM1567507@google.com>
On Thu, May 01, 2025 at 01:50:28PM +0100, Lee Jones wrote:
> On Mon, 28 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. Purpose of this implementation is
> > to provide discoverable MFDs just enough infrastructure to register
> > independent child devices without abusing the platform device.
> >
> > Current support is limited to just PCI type MFDs, but this can be further
> > extended to support other types like USB in the future.
> >
> > Signed-off-by: Raag Jadav <raag.jadav@intel.com>
> > ---
> >
> > v2: Introduce a shared struct mfd_aux_device
> > Introduce auxiliary device opt-in flag
> >
> > v3: Fix device_type ABI breakage (Andy)
> > Aesthetic adjustments (Andy)
> >
> > v4: s/mfd_aux/maux
> > Allow num_resources for child device (Andy)
> > Fix build warning (Andy)
> >
> > drivers/mfd/Kconfig | 2 +-
> > drivers/mfd/Makefile | 2 +-
> > drivers/mfd/mfd-aux.c | 156 +++++++++++++++++++++++++++++++
>
> This looks like mostly duplicated platform device code.
>
> If you are _certain_ that it needs to exist, you need to push it out to
> the auxiliary subsystem and remove any traces of it being MFD related.
>
> If it's needed by MFD, it'll be needed by other auxiliary users. Even
> if not now, sometime in the future.
Greg, if you are okay with this, please let me know. Or perhaps suggest
a better alternative.
Raag
next prev parent reply other threads:[~2025-05-02 22:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 6:02 Raag Jadav
2025-05-01 12:50 ` Lee Jones
2025-05-02 22:01 ` Raag Jadav [this message]
2025-05-12 10:22 ` Raag Jadav
2025-05-12 10:36 ` Greg KH
2025-05-12 11:10 ` Raag Jadav
2025-05-12 11:21 ` Greg KH
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=aBVArb-zJ_aqicHW@black.fi.intel.com \
--to=raag.jadav@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=david.m.ertman@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=ira.weiny@intel.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.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
all inboxes | Powered by JetHome®