Question about MFD devices.

[Joachim Holst]

Hi List!

Sorry to bother you with a somewhat stupid newbie question, but I've
already tried this one on the "kernel-newbies" list without a reply :-(

I'm trying to do a simple driver on an embedded (ARM) system that needs to
access some functionality in an MFD device. I've deducted that my driver
needs to be integrated into the MFD device structure, otherwise I won't
really be able to access the required functions.

In the process, I've been trying to figure out when these MFD devices are
supposed to be used, but I don't see the logic behind them as of yet.
Currently it seems to me that "if a chip has more than one function, it's
an MFD" no matter what type of functions the chip supplies.

To me, MFD seems to somewhat duplicate the standard kernel driver
structure, most implementations I've seen make it rather difficult to use
exported interfaces without integrating your driver into the structure.

Personally, I really don't think that a simple driver that toggles a GPIO
X times based on an ADC value should be integrated into an MFD device
structure. A misc device seems a bit more appropriate for this.

I guess that my conclusion are way wrong, so I hope that someone on the
list can enlighten me about this.

BRs,
/Jocke!



-- 
If it can't be fixed with duct-tape, it's definitely borken...

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/