mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "Toshiharu Okada" <toshiharu-linux@dsn.okisemi.com>
Cc: <perex@perex.cz>, <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>, <tomoya-linux@dsn.okisemi.com>
Subject: Re: [PATCH] Add SoundCard driver for OKI SEMICONDUCTOR ML7213 IOH
Date: Thu, 07 Jul 2011 18:38:33 +0200	[thread overview]
Message-ID: <s5h8vsa11x2.wl%tiwai@suse.de> (raw)
In-Reply-To: <A103B14DCBE64935815497A3464F512F@hacdom.okisemi.com>

At Thu, 7 Jul 2011 21:35:17 +0900,
Toshiharu Okada wrote:
> 
> Date: Thu, 07 Jul 2011 11:00:47 +0200
> From: Takashi Iwai <tiwai@suse.de>
> >>
> >> Therefore, I am not considering about ASoC.
> >> Do I need to fit this driver to an ASoC framework for an upstream?
> >
> >Yes, I guess this would be a better choice in your case.
> 
> Thank you for your comment.
> >From now on, We study about ASoC.
> If there are a document, a website, a driver, etc. which are referred, 
> please tell us.

Check Documentation/sound/alsa/soc/* files.

> Why is choosing ASoS better?
> Is it better to correspond to ASoC, when Audio Codec is unfixed?

It's not clear what you mean exactly as "unfixed", but in general, the
decision rather depends on the usage of the device.  If it's designed
for a use as a desktop PC component (such as a PCI card or
onboard-audio on PC), it'd make sense to implement as a stand-alone,
self-contained driver.

OTOH, if it's targeted mainly for embedded area, ASoC is the right
answer.  It's more modularized, and can be more flexibly configured in
the end.


Takashi

  reply	other threads:[~2011-07-07 16:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-06 10:27 Toshiharu Okada
2011-07-06 11:06 ` Takashi Iwai
2011-07-07  7:54   ` Toshiharu Okada
2011-07-07  9:00     ` Takashi Iwai
2011-07-07 12:35       ` Toshiharu Okada
2011-07-07 16:38         ` Takashi Iwai [this message]
2011-07-08 10:52           ` Toshiharu Okada
2011-07-09  1:34           ` Mark Brown
2011-07-09  7:40             ` Takashi Iwai
     [not found] <70D251FDDC55405882A8447CC455D56E@hacdom.okisemi.com>
     [not found] ` <8486F61FC3B94B908BFE654234DD6C97@hacdom.okisemi.com>
2011-10-17  4:28   ` Tomoya MORINAGA
2011-10-21 14:16     ` Takashi Iwai
2011-10-24 12:12       ` Tomoya MORINAGA
2011-10-24 12:20         ` Mark Brown
2011-11-08  9:03           ` Tomoya MORINAGA
2011-11-08 10:39             ` Mark Brown
2011-11-09  2:56               ` Tomoya MORINAGA
2011-11-08 14:38             ` Mark Brown
2011-11-10  5:00               ` Tomoya MORINAGA
2011-11-10 11:22                 ` 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=s5h8vsa11x2.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=joel.clark@intel.com \
    --cc=kok.howg.ewe@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=qi.wang@intel.com \
    --cc=tomoya-linux@dsn.okisemi.com \
    --cc=toshiharu-linux@dsn.okisemi.com \
    --cc=yong.y.wang@intel.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

all inboxes | Powered by JetHome®