public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Tomoya MORINAGA <tomoya.rohm@gmail.com>
Cc: Liam Girdwood <lrg@ti.com>, Jaroslav Kysela <perex@perex.cz>,
	Takashi Iwai <tiwai@suse.de>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Dimitris Papastamos <dp@opensource.wolfsonmicro.com>,
	Mike Frysinger <vapier@gentoo.org>,
	Daniel Mack <zonque@gmail.com>,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
	qi.wang@intel.com, yong.y.wang@intel.com, joel.clark@intel.com,
	kok.howg.ewe@intel.com
Subject: Re: [PATCH 2/3] sound/soc/lapis: add machine driver
Date: Fri, 2 Dec 2011 11:46:38 +0000	[thread overview]
Message-ID: <20111202114638.GI8245@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CANKRQnjdS1NvcGLa=S1M0D4U_NV3+JR1E4YfAV7Ziq-fE2LQgg@mail.gmail.com>

On Fri, Dec 02, 2011 at 02:33:59PM +0900, Tomoya MORINAGA wrote:
> 2011/11/21 Mark Brown <broonie@opensource.wolfsonmicro.com>:

> > This needs to come after you add the base platform support in the series
> > - clearly this won't work without the CPU side drivers it depends on.

> Most of the chipset drivers for Intel Atom E6xx series have already
> accepted by upstream.
> e.g. i2c-eg20t, pch_dma, pch_uart, spi-topcliff-pch, ml-ioh-gpio, etc...

The CPU side audio drivers are not there - there seemed to be some quite
serious review issues with those.

  parent reply	other threads:[~2011-12-02 11:46 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-21  4:08 [PATCH 1/3] sound/soc/codecs: add LAPIS Semiconductor ML26124 Tomoya MORINAGA
2011-11-21  4:08 ` [PATCH 2/3] sound/soc/lapis: add machine driver Tomoya MORINAGA
2011-11-21 11:34   ` Mark Brown
2011-12-02  5:33     ` Tomoya MORINAGA
2011-12-02  6:14       ` Takashi Iwai
2011-12-02  6:18         ` Tomoya MORINAGA
2011-12-02  6:39           ` Takashi Iwai
2011-12-02  6:52             ` Tomoya MORINAGA
2011-12-02  7:01               ` Takashi Iwai
2011-12-02  7:13                 ` Tomoya MORINAGA
2011-12-02  7:16                   ` Takashi Iwai
2011-12-02 11:46       ` Mark Brown [this message]
2011-12-02 12:09         ` Tomoya MORINAGA
2011-12-02 12:22           ` Mark Brown
2011-12-02 12:35             ` Tomoya MORINAGA
2011-12-02 12:49               ` Mark Brown
2011-11-21  4:08 ` [PATCH 3/3] sound/soc/lapis: add platform driver Tomoya MORINAGA
2011-11-21 11:45   ` Mark Brown
2011-12-12  8:28     ` Tomoya MORINAGA
2011-12-12 10:05       ` [alsa-devel] " Mark Brown
2011-12-13  4:38         ` Tomoya MORINAGA
2011-12-13  4:59           ` Mark Brown
2011-11-21 11:26 ` [PATCH 1/3] sound/soc/codecs: add LAPIS Semiconductor ML26124 Mark Brown
2011-11-22 10:47   ` Tomoya MORINAGA
2011-11-22 11:19     ` Mark Brown
2011-11-25  2:03       ` Tomoya MORINAGA
2011-11-25 11:02         ` Mark Brown

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=20111202114638.GI8245@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=dp@opensource.wolfsonmicro.com \
    --cc=joel.clark@intel.com \
    --cc=kok.howg.ewe@intel.com \
    --cc=lars@metafoo.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@ti.com \
    --cc=perex@perex.cz \
    --cc=qi.wang@intel.com \
    --cc=tiwai@suse.de \
    --cc=tomoya.rohm@gmail.com \
    --cc=vapier@gentoo.org \
    --cc=yong.y.wang@intel.com \
    --cc=zonque@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox