Hello, 2014-11-05 23:24 GMT+03:00 Mark Brown <broonie@xxxxxxxxxx>: > On Thu, Nov 06, 2014 at 12:02:49AM +0400, Dmitry Eremin-Solenikov wrote: >> 2014-11-03 16:41 GMT+03:00 Linus Walleij <linus.walleij@xxxxxxxxxx>: > >> > The point is still the same: no unrelated code in drivers/mfd, >> > then either use IIO DAC as a middle layer or sink the DAC handling >> > into respective subdriver, i.e. push it into the backlight or >> > volume directly then. > >> The problem is that the DAC is equally used by backlight and by sound >> device (WIP). >> What about true i2c device driver sitting in drivers/misc and exporting a regmap >> of 2 8-bit registers? > > If it can just export registers that sounds like a MFD. If it needs to > export functionality then like Linus says the IIO subsystem abstracts > DACs. I took a look at IIO subsystem. Thanks for the pointer. Indeed max517 driver can drive m62332 DAC with minimal modifications. However write support of the consumer interface is non-existing yet (which would be required to support DACs in unified manner). I'm actually looking at the regulator interface. Since this DAC serves mostly like a (semi-)constant voltage interface, would it be rather logical to use regulator subsystem to drive it? -- With best wishes Dmitry -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
