On Fri, Dec 18, 2020 at 06:03:10PM +0000, Mark Brown wrote: > On Fri, Dec 18, 2020 at 12:28:17PM -0400, Jason Gunthorpe wrote: > > On Fri, Dec 18, 2020 at 03:52:04PM +0000, Mark Brown wrote: > > > On Fri, Dec 18, 2020 at 10:08:54AM -0400, Jason Gunthorpe wrote: > > > > > I thought the recent LWN article summed it up nicely, auxillary bus is > > > > for gluing to subsystems together using a driver specific software API > > > > to connect to the HW, MFD is for splitting a physical HW into disjoint > > > > regions of HW. > > > > This conflicts with the statements from Greg about not using the > > > platform bus for things that aren't memory mapped or "direct firmware", > > > a large proportion of MFD subfunctions are neither at least in so far as > > > I can understand what direct firmware means. > > > I assume MFD will keep existing and it will somehow stop using > > platform device for the children it builds. > > If it's not supposed to use platform devices so I'm assuming that the > intention is that it should use aux devices, otherwise presumably it'd > be making some new clone of the platform bus but I've not seen anyone > suggesting this. I wouldn't assume that, I certainly don't want to see all the HW related items in platform_device cloned roughly into aux device. I've understood the bus type should be basically related to the thing that is creating the device. In a clean view platform code creates platform devices. DT should create DT devices, ACPI creates ACPI devices, PNP does pnp devices, etc So, I strongly suspect, MFD should create mfd devices on a MFD bus type. Alexandre's point is completely valid, and I think is the main challenge here, somehow avoiding duplication. If we were to look at it with some OOP viewpoint I'd say the generic HW resource related parts should be some shared superclass between 'struct device' and 'struct platform/pnp/pci/acpi/mfd/etc_device'. > > > To be honest I don't find the LWN article clarifies things particularly > > > here, the rationale appears to involve some misconceptions about what > > > MFDs look like. It looks like it assumes that MFD functions have > > > physically separate register sets for example which is not a reliable > > > feature of MFDs, nor is the assumption that there's no shared > > > functionality which appears to be there. It also appears to assume that > > > I think the MFD cell model is probably the deciding feature. If that > > cell description scheme suites the device, and it is very HW focused, > > then MFD is probably the answer. > > > The places I see aux device being used are a terrible fit for the cell > > idea. If there are MFD drivers that are awkardly crammed into that > > cell description then maybe they should be aux devices? > > When you say the MFD cell model it's not clear what you mean - I *think* > you're referring to the idea of the subdevices getting all the I mean using static "struct mfd_cell" arrays to describe things. > Look at something like wm8994 for example - the subdevices just know > which addresses in the device I2C/SPI regmap to work with but some of > them have interrupts passed through to them (and could potentially also > have separate subdevices for clocks and pinctrl). These subdevices are > not memory mapped, not enumerated by firmware and the hardware has > indistinct separation of functions in the register map compared to how > Linux models the chips. wm8994 seems to fit in the mfd_cell static arrays pretty well.. Jason
