All of lore.kernel.org
 help / color / mirror / Atom feed
From: Raag Jadav <raag.jadav@intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: david.m.ertman@intel.com, ira.weiny@intel.com, lee@kernel.org,
	andriy.shevchenko@linux.intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] mfd: core: Support auxiliary device
Date: Fri, 4 Apr 2025 14:36:41 +0300	[thread overview]
Message-ID: <Z-_ESekESYYvMHeR@black.fi.intel.com> (raw)
In-Reply-To: <2025040336-ethically-regulate-3594@gregkh>

On Thu, Apr 03, 2025 at 03:02:47PM +0100, Greg KH wrote:
> On Thu, Apr 03, 2025 at 04:30:53PM +0530, 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.

...

> > 2. Should we allow auxiliary drivers to manage their own resources
> >    (MEM, IO, IRQ etc)?
> 
> The resources are all shared by the "parent" device, that's what makes
> aux drivers work, they need to handle this as there is no unique way to
> carve up the resources here.
> 
> So I don't know how you would do this, sorry.

Perhaps we can carve it up in mfd_add_devices() using start and end members
and error out if they overlap.

Can't we still have a struct resource that is unique to that specific
auxiliary device?

Raag

  parent reply	other threads:[~2025-04-04 11:36 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 [this message]
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

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=Z-_ESekESYYvMHeR@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=ira.weiny@intel.com \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.