On Wed, Jan 25, 2017 at 06:29:55PM +0000, Mark Brown wrote: > On Wed, Jan 25, 2017 at 06:23:20PM +0000, Mark Rutland wrote: > > On Wed, Jan 25, 2017 at 08:56:42AM -0800, Furquan Shaikh wrote: > > > > That is the reason why the recent change to add ACPI support to fixed > > > regulators was done > > > (https://github.com/torvalds/linux/blob/master/drivers/regulator/fixed.c#L100). > > > To be honest, I'm surprised this got merged. > > My understanding was that it was instantiated from another device as an > implementation detail of that device, letting it say "this GPIO should > be handled as a regulator". > > > Mark, this was added in this cycle; can we please rip that out for now? > > If it's instantiated directly we probably should. I think that given the larger problem that needs to be addressed here, and how the us of DSD properties muddies the water, it would be preferable to remove it until we have some consensus. > > We can certainly come up with something that allows drivers to support > > both, but trying to do this without updating drivers opens a huge set of > > problems. > > I think there's a reasonable chance that any ACPI specs could be written > in such a way as to allow transparent support in Linux, the main thing > I'd worry about is naming issues. I think it's certainly possible to handle this so that drivers don't largely have to care. I also think there is some massaging the needs to be done (e.g. tables of names or some indirection for ACPI/DT differences), and a unified API that tries to completely hide that is not truly possible. Thanks, Mark. -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
