From: Tomoya MORINAGA <tomoya-linux@dsn.lapis-semi.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: perex@perex.cz, linux-kernel@vger.kernel.org, "Wang,
Qi" <qi.wang@intel.com>, "Wang, Yong Y" <yong.y.wang@intel.com>,
"Clark, Joel" <joel.clark@intel.com>,
"Ewe, Kok Howg" <kok.howg.ewe@intel.com>,
Liam Girdwood <lrg@ti.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
alsa-devel@alsa-project.org
Subject: Re: [PATCH] Add SoundCard driver for OKI SEMICONDUCTOR ML7213 IOH
Date: Mon, 24 Oct 2011 21:12:42 +0900 [thread overview]
Message-ID: <4EA5563A.10703@dsn.lapis-semi.com> (raw)
In-Reply-To: <s5h7h3ysa4l.wl%tiwai@suse.de>
Hi Iwai,
(2011/10/21 23:16), Takashi Iwai wrote:
> At Mon, 17 Oct 2011 13:28:39 +0900,
> Tomoya MORINAGA wrote:
>>
>> Hi Iwai,
>>
>> We have just started porting to ASoC structure.
>
> Please add ASoC maintainers to Cc if you have questions about ASoC.
>
>> I have a question.
>>
>> As you reviewed before, currently, our driver consists of 2 parts,
>> Soundcard driver and I2S driver.
>>
>> Soundcard consists of 2 parts
>> - ALSA interface / control part
>> - CODEC control part
>>
>> I2S driver consists of 4 parts
>> - HAL
>> - DMA control / interrupt control
>> - Soundcard interface part
>> - PCI interface function
>>
>> According to "soc" Documentation,
>> We must divide to 3 parts, platform driver, machine driver and codec driver.
>>
>> So, I divided like the following parts.
>>
>> platform driver
>> - ALSA interface / control part
>> - HAL
>> - DMA control / interrupt control
>> - Soundcard interface part
>> - PCI interface function
>>
>> machine driver
>> - (none)
>>
>> codec driver
>> - CODEC control part
>>
>> Is the above dividing true ?
>
> Not really. ASoC is designed to be much more modular. Take a look at
> the codes in sound/soc/*. You'll grasp how the components are split.
> (The documents in Documentation/sound/alsa/soc/ are slightly
> obsoleted...)
Of course, I read Documentation/sound/alsa/soc/ and sound/soc/*.
However, it's not easy for me.
I have just 2 questions.
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.
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.
>
> The conversion of PCM part is usually straightforward, as found in
> *-pcm.c. The DAI setup depends on the hardware implementation.
> That's for machine driver. But it's hard to tell in more details
> until I see the actual code snippet you are working on...
I understand.
I'm going to send our modified driver soon.
Thanks,
--
tomoya
ROHM Co., Ltd.
next prev parent reply other threads:[~2011-10-24 12:12 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 [this message]
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
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=4EA5563A.10703@dsn.lapis-semi.com \
--to=tomoya-linux@dsn.lapis-semi.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=joel.clark@intel.com \
--cc=kok.howg.ewe@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=perex@perex.cz \
--cc=qi.wang@intel.com \
--cc=tiwai@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).