From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Tomoya MORINAGA <tomoya-linux@dsn.lapis-semi.com>
Cc: alsa-devel@alsa-project.org, "Wang, Qi" <qi.wang@intel.com>,
Takashi Iwai <tiwai@suse.de>,
"Wang, Yong Y" <yong.y.wang@intel.com>,
linux-kernel@vger.kernel.org, "Ewe,
Kok Howg" <kok.howg.ewe@intel.com>, Liam Girdwood <lrg@ti.com>,
"Clark, Joel" <joel.clark@intel.com>
Subject: Re: [PATCH] Add SoundCard driver for OKI SEMICONDUCTOR ML7213 IOH
Date: Mon, 24 Oct 2011 14:20:15 +0200 [thread overview]
Message-ID: <20111024122015.GA26033@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4EA5563A.10703@dsn.lapis-semi.com>
On Mon, Oct 24, 2011 at 09:12:42PM +0900, Tomoya MORINAGA wrote:
> 1. PCI interface function.
> Any current ASoC drivers don't have PCI interface function.
> So I don't know where the function should be in machine driver or
> platform driver.
It depends on what the driver is for. Probably you want a driver which
is some combination of machine driver and the various drivers that are
normally part of the SoC - whatever roles in the system are filled by
this hardware the driver ought to register subsystem drivers for those
roles.
> 2. Register Access
> Can platform driver access register ?
> According to the soc document, platform driver must not access hardware,
> however, some drivers looks accessing their hardware.
What makes you say this? A driver that can't access hardware would be
rather useless...
next prev parent reply other threads:[~2011-10-24 12:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <70D251FDDC55405882A8447CC455D56E@hacdom.okisemi.com>
[not found] ` <8486F61FC3B94B908BFE654234DD6C97@hacdom.okisemi.com>
2011-10-17 4:28 ` [PATCH] Add SoundCard driver for OKI SEMICONDUCTOR ML7213 IOH Tomoya MORINAGA
2011-10-21 14:16 ` Takashi Iwai
2011-10-24 12:12 ` Tomoya MORINAGA
2011-10-24 12:20 ` Mark Brown [this message]
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
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
2011-07-08 10:52 ` Toshiharu Okada
2011-07-09 1:34 ` Mark Brown
2011-07-09 7:40 ` Takashi Iwai
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=20111024122015.GA26033@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=joel.clark@intel.com \
--cc=kok.howg.ewe@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=qi.wang@intel.com \
--cc=tiwai@suse.de \
--cc=tomoya-linux@dsn.lapis-semi.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