All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ashish Chavan <ashish.chavan@kpitcummins.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	alsa-devel <alsa-devel@alsa-project.org>,
	"kiran.padwal" <kiran.padwal@kpitcummins.com>, lrg <lrg@ti.com>,
	David Dajun Chen <david.chen@diasemi.com>
Subject: Re: [PATCH] ASoC: codecs: da9055: Update driver name to fix breakage due to pmic driver with same name
Date: Mon, 5 Aug 2013 13:25:31 +0530	[thread overview]
Message-ID: <1375689331.28910.5.camel@matrix> (raw)
In-Reply-To: <20130729160157.GZ9858@sirena.org.uk>

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.

  reply	other threads:[~2013-08-05  7:19 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-05 11:47 [PATCH] ASoC: codecs: da9055: Update driver name to fix breakage due to pmic driver with same name Ashish Chavan
2013-07-05 11:44 ` [alsa-devel] " Mark Brown
2013-07-05 11:44   ` Mark Brown
2013-07-05 13:35   ` Ashish Chavan
2013-07-05 13:37     ` [alsa-devel] " Mark Brown
2013-07-05 13:37       ` Mark Brown
2013-07-08  7:54       ` Ashish Chavan
2013-07-08 11:26         ` [alsa-devel] " Mark Brown
2013-07-08 11:26           ` Mark Brown
2013-07-11 11:36           ` Ashish Chavan
2013-07-17 10:36             ` [alsa-devel] " Mark Brown
2013-07-17 10:36               ` Mark Brown
2013-07-22  8:43               ` Ashish Chavan
2013-07-22 10:02                 ` [alsa-devel] " Mark Brown
2013-07-22 10:02                   ` Mark Brown
2013-07-29 15:06                   ` Ashish Chavan
2013-07-29 16:01                     ` [alsa-devel] " Mark Brown
2013-08-05  7:55                       ` Ashish Chavan [this message]
2013-08-05 14:42                         ` Mark Brown
2013-08-05 14:42                           ` Mark Brown
2013-08-05 15:51                           ` Ashish Chavan
2013-08-05 16:23                             ` [alsa-devel] " Mark Brown
2013-08-29 12:08                               ` Ashish Chavan
2013-09-02  9:49                                 ` Opensource [Adam Thomson]
2013-09-02 10:38                                   ` [alsa-devel] " Mark Brown
2013-09-02 15:38                                     ` Opensource [Adam Thomson]
2013-09-02 17:41                                       ` [alsa-devel] " Mark Brown
2013-09-02 17:41                                         ` Mark Brown
2013-09-04 16:13                                         ` Opensource [Adam Thomson]
2013-09-04 18:34                                           ` [alsa-devel] " Mark Brown
2013-09-04 18:34                                             ` Mark Brown
2013-09-06 14:17                                             ` Opensource [Adam Thomson]
2013-09-09 11:26                                               ` [alsa-devel] " Mark Brown
2013-09-09 11:26                                                 ` Mark Brown
2013-09-10 13:05                                                 ` Opensource [Adam Thomson]
2013-09-10 17:07                                                   ` [alsa-devel] " Mark Brown
2013-09-10 17:07                                                     ` Mark Brown
2013-09-12 17:11                                                     ` Opensource [Adam Thomson]
2013-09-12 21:58                                                       ` [alsa-devel] " Mark Brown
2013-09-13 15:05                                                         ` Opensource [Adam Thomson]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1375689331.28910.5.camel@matrix \
    --to=ashish.chavan@kpitcummins.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=david.chen@diasemi.com \
    --cc=kiran.padwal@kpitcummins.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.