Re: [PATCH] ASoC: codecs: da9055: Update driver name to fix breakage due to pmic driver with same name

[Ashish Chavan <ashish.chavan@kpitcummins.com>]

On Mon, 2013-07-22 at 11:02 +0100, Mark Brown wrote:
> On Mon, Jul 22, 2013 at 02:13:14PM +0530, Ashish Chavan wrote:
>
> > working on it and hope to submit updated drivers in next 5-6 weeks. In
> > the meanwhile you may apply quick fix (one which I already posted), if
> > you find it worth.
>
> You would need to resend, as I indicated orginally I discarded it.

We had started working on restructuring of both PMIC and CODEC drivers.
But soon after starting, we realized that the kind of abstraction that
we were heading towards will not be logically correct and good from
maintainability point of view. Basically tying up two COMPLETELY
INDEPENDENT (they really don't share anything other than the name!)
drivers via a virtual MFD entity will not make much sense in our
opinion. Also as mentioned earlier, the codec design(chip) will be
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?


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.