On Mon, 2013-07-29 at 17:01 +0100, Mark Brown wrote:
On Mon, Jul 29, 2013 at 08:36:26PM +0530, Ashish Chavan wrote:
produced as a standalone codec device soon, and we hope the driver can be re-used directly without changes. Is this the reason why we see only a handful examples of suggested implementation in kernel?
Well, it's a very unusual hardware design choice to have multiple I2C endpoints in a single physical chip.
I hope to see more of such devices in near future.
With regmap it should be very straightforward to reuse the same driver for both standalone and non-standalone versions, just a small amount of glue code in the CODEC driver I'd expect. Usually the bus level code is tiny.
The glue code that you are talking about is for the same virtual MFD component that you proposed initially, right? I mean the glue code in CODEC will help it to get attached to the MFD. In this case, in addition to the glue code inside CODEC we will also need additional MFD component. Or I am completely misinterpreting you here?
This message contains information that may be privileged or confidential and is the property of the KPIT Cummins Infosystems Ltd. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. KPIT Cummins Infosystems Ltd. does not accept any liability for virus infected mails.