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
| ||
|
Date: Wed, 1 Jul 2020 20:32:50 -0300 From: Jason Gunthorpe <jgg@...pe.ca> To: Mark Brown <broonie@...nel.org> Cc: Ranjani Sridharan <ranjani.sridharan@...ux.intel.com>, Greg KH <gregkh@...uxfoundation.org>, Takashi Iwai <tiwai@...e.de>, Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>, Jeff Kirsher <jeffrey.t.kirsher@...el.com>, davem@...emloft.net, netdev@...r.kernel.org, linux-rdma@...r.kernel.org, nhorman@...hat.com, sassmann@...hat.com, Fred Oh <fred.oh@...ux.intel.com>, lee.jones@...aro.org Subject: Re: [net-next v4 10/12] ASoC: SOF: Introduce descriptors for SOF client On Wed, Jul 01, 2020 at 10:50:49AM +0100, Mark Brown wrote: > On Tue, Jun 30, 2020 at 02:27:10PM -0300, Jason Gunthorpe wrote: > > > I wonder if SW_MFD might me more apt though? Based on Mark's remarks > > current MFD is 'hw' MFD where the created platform_devices expect a > > MMIO pass through, while this is a MFD a device-specific SW > > interfacing layer. > > Another part of this is that there's not a clean cut over between MMIO > and not using any hardware resources at all - for example a device might > be connected over I2C but use resources to distribute interrupts to > subdevices. How does the subdevice do anything if it only received an interrupt? That sounds rather more like virtual bus's use case.. Jason
Powered by blists - more mailing lists