From: Mark Brown <broonie@sirena.org.uk>
To: Dmitry Baryshkov <dbaryshkov@gmail.com>
Cc: Russ Dill <russ.dill@gmail.com>, alsa-devel@alsa-project.org
Subject: Re: [PATCH 4/5] pxa2xx-lib: support building for several pxa's
Date: Mon, 8 Sep 2008 11:17:24 +0100 [thread overview]
Message-ID: <20080908101723.GD790@sirena.org.uk> (raw)
In-Reply-To: <1220864773-31745-4-git-send-email-dbaryshkov@gmail.com>
On Mon, Sep 08, 2008 at 01:06:12PM +0400, Dmitry Baryshkov wrote:
> Here's a version of the third patch in the series without all the
> cpu_is_pxa3xx())'s around the pxa_gpio_mode's? Also, there was a build
> error when just building the sound/arm pxa2xx-ac97.
If there's a build error introduced by the earlier patch it ought to be
fixed there rather than in a subsequent patch?
> -#ifdef CONFIG_PXA3xx
> -#define GCR_CLKBPB (1 << 31) /* Internal clock enable */
> -#endif
> +#define GCR_CLKBPB (1 << 31) /* Internal clock enable, PXA3XX only */
At least this hunk needs to at least get acked by rmk, and would
probably need to go via the ARM tree.
> + if (!cpu_is_pxa3xx()) {
> + pxa_gpio_mode(GPIO31_SYNC_AC97_MD);
> + pxa_gpio_mode(GPIO30_SDATA_OUT_AC97_MD);
> + pxa_gpio_mode(GPIO28_BITCLK_AC97_MD);
> + pxa_gpio_mode(GPIO29_SDATA_IN_AC97_MD);
> + }
I'd rather do this by explicitly identifying the PXA2xx CPUs (on the
basis that Marvell are producing new PXA variants but the set of PXA2xx
CPUs should be fixed now).
> --- a/sound/soc/pxa/pxa2xx-i2s.c
> +++ b/sound/soc/pxa/pxa2xx-i2s.c
This should be split into a separate patch - it's not directly related
to the other changes except in terms of the overall goal and covers a
different driver. It's also not mentioned in the patch description.
next prev parent reply other threads:[~2008-09-08 10:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-08 8:53 [GIT PULL] unify two pxa sound drivers Dmitry Baryshkov
2008-09-08 9:05 ` Liam Girdwood
2008-09-08 9:06 ` [PATCH 1/5] Permit simultaneous compilation of both PXA AC97 drivers Dmitry Baryshkov
2008-09-08 9:06 ` [PATCH 2/5] Separate common pxa2xx-ac97 code Dmitry Baryshkov
2008-09-08 9:06 ` [PATCH 3/5] Make pxa-ac97-lib separate module Dmitry Baryshkov
2008-09-08 9:06 ` [PATCH 4/5] pxa2xx-lib: support building for several pxa's Dmitry Baryshkov
2008-09-08 9:06 ` [PATCH 5/5] Separate common pxa2xx-pcm code Dmitry Baryshkov
2008-09-08 10:07 ` Eric Miao
2008-09-08 10:13 ` Dmitry
2008-09-08 10:33 ` Mark Brown
2008-09-08 10:17 ` Mark Brown [this message]
2008-09-08 9:33 ` [PATCH 2/5] Separate common pxa2xx-ac97 code Liam Girdwood
2008-09-08 9:42 ` Dmitry Baryshkov
2008-09-08 9:51 ` Liam Girdwood
2008-09-08 9:30 ` [PATCH 1/5] Permit simultaneous compilation of both PXA AC97 drivers Mark Brown
2008-09-08 10:19 ` Dmitry Baryshkov
2008-09-08 10:35 ` 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=20080908101723.GD790@sirena.org.uk \
--to=broonie@sirena.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=dbaryshkov@gmail.com \
--cc=russ.dill@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 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.