From: "Lambrecht Jürgen" <J.Lambrecht@TELEVIC.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: "Philippe Rétornaz" <philippe.retornaz@epfl.ch>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Liam Girdwood" <lrg@ti.com>
Subject: Re: [RFC PATCH] ARM ASoC: add sound driver for imx27pdk using mc13783 codec
Date: Mon, 11 Jul 2011 12:30:52 +0200 [thread overview]
Message-ID: <4E1AD0DC.7020201@televic.com> (raw)
In-Reply-To: <20110709022501.GA26900@sirena.org.uk>
On 07/09/2011 04:25 AM, Mark Brown wrote:
>
> On Fri, Jul 08, 2011 at 03:24:51PM +0200, J??rgen Lambrecht wrote:
>
> Please read and try to follow the guidelines in SubmittingPatches:
>
OK, I only had a quick scan through it, ... and instead of complaining
of ./Documentation being always outdated, I better supply a patch for
SubmittingPatches ;-).
>
> - Provide a sensible changelog for your patch
>
i will for the patch indeed
>
> - Send copies to the relevant maintainers
>
Only being an RFC and not a real patch, I didn't do the effort of
checking MAINTAINERS, sorry.
So you and Liam Girdwood for sound/soc
>
> - Word wrap within 80 columns
> - Follow the kernel coding style.
>
Oops, I thought I already sent the patches through ./scripts/checkpatch.pl
(the patches come from another branch in my git on an older version of
the kernel)
(5 errors, shame on me..)
>
>
> >
> > if SND_IMX_SOC
> >
> > -config SND_MXC_SOC_SSI
> > - tristate
> > -
>
> This appeears to be unrelated to adding new machine support and should
> be a separate patch.
>
indeed, is someone else's patch I applied already
(when moving my branch to the latest pengutronix/for-next branch, i
thought that patch would already have been applied - forgot to check)
>
>
> > +config SND_SOC_IMX_MC13783
> > + tristate
> > +
>
> Err... what is this for?
>
Well, normally all drivers here are platform specific, but I saw my
driver for the imx27pdk was the same as the 'Phytec phyCORE (and
phyCARD) boards' one (and now I hear also valid for mx31moboard
platforms). So I decided to copy "phycore-mc13783.c" to "imx-mc13783.c",
and this 'SND_SOC_IMX_MC13783' is to compile in the Makefile.
So I added an extra layer in Kconfig, because my 'SND_SOC_IMX27_MC13783'
selects it, and also the phycore one selects it (but omitted it from my
patch because it is not mine, and only exists in the imx-sound branch of
Sascha).
I think now it is better to remove those 3 lines.
See next paragraph to continue.
>
>
> > config SND_MXC_SOC_WM1133_EV1
> > tristate "Audio on the the i.MX31ADS with WM1133-EV1 fitted"
> > depends on MACH_MX31ADS_WM1133_EV1 && EXPERIMENTAL
> > select SND_SOC_WM8350
> > - select SND_MXC_SOC_SSI
> > select SND_MXC_SOC_FIQ
> > help
>
> Again, this and all the other similar hunks are totally unrelated to
> adding a machine.
>
> > +config SND_SOC_IMX27_MC13783
> > + tristate "SoC Audio support for i.MX27 platforms with a
> MC13783 codec"
> > + depends on MACH_MX27_3DS
>
> The dependency and the text disagree with each other...
>
Indeed. But i did not dare to touch the phycore code (only in imx-sound
branch).. Maybe this is better (removing those 3 lines above):
config SND_SOC_IMX_MC13783
tristate "SoC Audio support for i.MX27 platforms with a MC13783 codec"
depends on MACH_MX27_3DS || MACH_PCM038 || MACH_PCM037 ||
MACH_MX31MOBOARD
select SND_SOC_MC13783
select SND_MXC_SOC_MX2
help
Say Y if you want to add support for SoC audio on i.MX27 platforms
with a MC13783 codec (based on Freescale's imx27pdk kit)
But actually, I have my doubts. Is it possible to reuse such a platform
driver?
I don't know the other platforms, maybe they differ a little bit?
For example our own HW (based on imx27pdk) uses an enable pin (gpio) for
the loudspeaker amplifier. Now I put it on in the machine driver (i mean
the one in ./arch/arm/mach-imx/). But to save power, it could be
interesting to enable the ampli only when needed.
What to do then: copy the complete driver and add an ampli-on/off function?
Thanks for your comments,
Jürgen
[snip: for next mail]
--
Jürgen Lambrecht
R&D Associate
Tel: +32 (0)51 303045 Fax: +32 (0)51 310670
http://www.televic-rail.com
Televic Rail NV - Leo Bekaertlaan 1 - 8870 Izegem - Belgium
Company number 0825.539.581 - RPR Kortrijk
WARNING: multiple messages have this Message-ID (diff)
From: J.Lambrecht@TELEVIC.com (Lambrecht Jürgen)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] ARM ASoC: add sound driver for imx27pdk using mc13783 codec
Date: Mon, 11 Jul 2011 12:30:52 +0200 [thread overview]
Message-ID: <4E1AD0DC.7020201@televic.com> (raw)
In-Reply-To: <20110709022501.GA26900@sirena.org.uk>
On 07/09/2011 04:25 AM, Mark Brown wrote:
>
> On Fri, Jul 08, 2011 at 03:24:51PM +0200, J??rgen Lambrecht wrote:
>
> Please read and try to follow the guidelines in SubmittingPatches:
>
OK, I only had a quick scan through it, ... and instead of complaining
of ./Documentation being always outdated, I better supply a patch for
SubmittingPatches ;-).
>
> - Provide a sensible changelog for your patch
>
i will for the patch indeed
>
> - Send copies to the relevant maintainers
>
Only being an RFC and not a real patch, I didn't do the effort of
checking MAINTAINERS, sorry.
So you and Liam Girdwood for sound/soc
>
> - Word wrap within 80 columns
> - Follow the kernel coding style.
>
Oops, I thought I already sent the patches through ./scripts/checkpatch.pl
(the patches come from another branch in my git on an older version of
the kernel)
(5 errors, shame on me..)
>
>
> >
> > if SND_IMX_SOC
> >
> > -config SND_MXC_SOC_SSI
> > - tristate
> > -
>
> This appeears to be unrelated to adding new machine support and should
> be a separate patch.
>
indeed, is someone else's patch I applied already
(when moving my branch to the latest pengutronix/for-next branch, i
thought that patch would already have been applied - forgot to check)
>
>
> > +config SND_SOC_IMX_MC13783
> > + tristate
> > +
>
> Err... what is this for?
>
Well, normally all drivers here are platform specific, but I saw my
driver for the imx27pdk was the same as the 'Phytec phyCORE (and
phyCARD) boards' one (and now I hear also valid for mx31moboard
platforms). So I decided to copy "phycore-mc13783.c" to "imx-mc13783.c",
and this 'SND_SOC_IMX_MC13783' is to compile in the Makefile.
So I added an extra layer in Kconfig, because my 'SND_SOC_IMX27_MC13783'
selects it, and also the phycore one selects it (but omitted it from my
patch because it is not mine, and only exists in the imx-sound branch of
Sascha).
I think now it is better to remove those 3 lines.
See next paragraph to continue.
>
>
> > config SND_MXC_SOC_WM1133_EV1
> > tristate "Audio on the the i.MX31ADS with WM1133-EV1 fitted"
> > depends on MACH_MX31ADS_WM1133_EV1 && EXPERIMENTAL
> > select SND_SOC_WM8350
> > - select SND_MXC_SOC_SSI
> > select SND_MXC_SOC_FIQ
> > help
>
> Again, this and all the other similar hunks are totally unrelated to
> adding a machine.
>
> > +config SND_SOC_IMX27_MC13783
> > + tristate "SoC Audio support for i.MX27 platforms with a
> MC13783 codec"
> > + depends on MACH_MX27_3DS
>
> The dependency and the text disagree with each other...
>
Indeed. But i did not dare to touch the phycore code (only in imx-sound
branch).. Maybe this is better (removing those 3 lines above):
config SND_SOC_IMX_MC13783
tristate "SoC Audio support for i.MX27 platforms with a MC13783 codec"
depends on MACH_MX27_3DS || MACH_PCM038 || MACH_PCM037 ||
MACH_MX31MOBOARD
select SND_SOC_MC13783
select SND_MXC_SOC_MX2
help
Say Y if you want to add support for SoC audio on i.MX27 platforms
with a MC13783 codec (based on Freescale's imx27pdk kit)
But actually, I have my doubts. Is it possible to reuse such a platform
driver?
I don't know the other platforms, maybe they differ a little bit?
For example our own HW (based on imx27pdk) uses an enable pin (gpio) for
the loudspeaker amplifier. Now I put it on in the machine driver (i mean
the one in ./arch/arm/mach-imx/). But to save power, it could be
interesting to enable the ampli only when needed.
What to do then: copy the complete driver and add an ampli-on/off function?
Thanks for your comments,
J?rgen
[snip: for next mail]
--
J?rgen Lambrecht
R&D Associate
Tel: +32 (0)51 303045 Fax: +32 (0)51 310670
http://www.televic-rail.com
Televic Rail NV - Leo Bekaertlaan 1 - 8870 Izegem - Belgium
Company number 0825.539.581 - RPR Kortrijk
next prev parent reply other threads:[~2011-07-11 10:30 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-08 13:24 [RFC PATCH] ARM ASoC: add sound driver for imx27pdk using mc13783 codec Jürgen Lambrecht
2011-07-08 13:24 ` Jürgen Lambrecht
2011-07-08 14:11 ` Philippe Rétornaz
2011-07-08 14:11 ` Philippe Rétornaz
2011-07-08 14:19 ` Lambrecht Jürgen
2011-07-08 14:19 ` Lambrecht Jürgen
2011-07-27 8:28 ` Philippe Rétornaz
2011-07-27 8:28 ` Philippe Rétornaz
2011-07-29 19:14 ` Jürgen Lambrecht
2011-07-29 19:14 ` Jürgen Lambrecht
2011-09-20 11:39 ` Philippe Rétornaz
2011-09-20 11:39 ` Philippe Rétornaz
2012-01-25 15:45 ` Philippe Rétornaz
2012-01-25 15:45 ` Philippe Rétornaz
2012-01-28 20:57 ` Fabio Estevam
2012-01-28 20:57 ` Fabio Estevam
2012-01-29 19:01 ` Philippe Rétornaz
2012-01-29 19:01 ` Philippe Rétornaz
2012-01-30 15:59 ` Fabio Estevam
2012-01-30 15:59 ` Fabio Estevam
2012-02-02 17:32 ` Mark Brown
2012-02-02 17:32 ` [alsa-devel] " Mark Brown
2012-02-03 7:45 ` Philippe Rétornaz
2012-02-03 7:45 ` [alsa-devel] " Philippe Rétornaz
2012-02-03 11:58 ` Mark Brown
2012-02-03 11:58 ` [alsa-devel] " Mark Brown
2012-02-09 21:24 ` Fabio Estevam
2012-02-09 21:24 ` [alsa-devel] " Fabio Estevam
2011-07-09 2:25 ` Mark Brown
2011-07-09 2:25 ` Mark Brown
2011-07-11 10:30 ` Lambrecht Jürgen [this message]
2011-07-11 10:30 ` Lambrecht Jürgen
2011-07-11 11:44 ` Mark Brown
2011-07-11 11:44 ` 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=4E1AD0DC.7020201@televic.com \
--to=j.lambrecht@televic.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lrg@ti.com \
--cc=philippe.retornaz@epfl.ch \
--cc=s.hauer@pengutronix.de \
/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.