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

[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]

On Mon, Aug 05, 2013 at 09:21:37PM +0530, Ashish Chavan wrote:
> On Mon, 2013-08-05 at 15:42 +0100, Mark Brown wrote:

> > No, I'm talking about the same thing I was talking about originally.

> Thanks for confirming it. From our view point, we still feel that it's
> not a good design which requires an additional MFD component even to
> support a stand alone CODEC chip. The way we look at it is, there are so

What makes you say that a MFD is required for a standalone CODEC?

> many stand alone CODEC drivers in kernel and most of them are fine
> without the MFD stub. We wish that our DA9055 CODEC driver should also
> be treated in the same way. Just placing it in a different hardware
> package (together with PMIC, in this case) shouldn't necessitate any
> changes in software. e.g. whether any chip is produced as a BGA
> component or through hole component, has no effect on it's software.

You only need to write the glue once, it'd probably take you less time
than writing these e-mails...  Once you've handed the regmap to the ASoC
core the code is identical.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-08-05 16:23 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
2013-08-05 14:42                         ` [alsa-devel] " Mark Brown
2013-08-05 14:42                           ` Mark Brown
2013-08-05 15:51                           ` Ashish Chavan
2013-08-05 16:23                             ` Mark Brown [this message]
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=20130805162342.GS9858@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=ashish.chavan@kpitcummins.com \
    --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.