linux-kernel - Re: [PATCH v1] mfd: core: Support auxiliary device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Z-6YU24dhxF5PRaw@smile.fi.intel.com>
Date: Thu, 3 Apr 2025 17:16:51 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: Raag Jadav <raag.jadav@...el.com>, david.m.ertman@...el.com,
	ira.weiny@...el.com, lee@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1] mfd: core: Support auxiliary device

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:

...

> > 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.

I think we should simply enforce the requirement that MFD on AUX bus must use
regmap. This will solve the serialisation and common access to the resources.

-- 
With Best Regards,
Andy Shevchenko