From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: Kuninori Morimoto <morimoto.kuninori@renesas.com>,
Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org, lethal@linux-sh.org,
linux-sh@vger.kernel.org
Subject: Re: [PATCH 3/3] Add FSI-AK464x sound support for ms7724se
Date: Wed, 19 Aug 2009 14:45:47 +0000 [thread overview]
Message-ID: <20090819144547.GB3323@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <aec7e5c30908190718j40459a55w614093c6366800db@mail.gmail.com>
On Wed, Aug 19, 2009 at 11:18:13PM +0900, Magnus Damm wrote:
> At this point on SuperH we first select processor and then board(s)
> after that. So the kernel is configured to run on one specific
> processor model. But the FSI block may show up in other processors and
> the pinmux configuration will most likely be different at that point.
> We usually keep the pinmux configuration in the board setup code and
> the let the driver "just work" and never touch any GPIOs unless the
> driver comes with GPIO support.
Hrm, OK. In that case it's a bit of an odd way of doing pinmux
configuration but that's fine.
next prev parent reply other threads:[~2009-08-19 14:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-19 11:25 [PATCH 3/3] Add FSI-AK464x sound support for ms7724se Kuninori Morimoto
2009-08-19 12:00 ` Mark Brown
2009-08-19 13:46 ` Magnus Damm
2009-08-19 14:02 ` Mark Brown
2009-08-19 14:18 ` Magnus Damm
2009-08-19 14:45 ` Mark Brown [this message]
2009-08-20 7:46 ` [alsa-devel] " Kuninori Morimoto
2009-08-20 8:52 ` [alsa-devel] [PATCH 3/3] Add FSI-AK464x sound support for Mark Brown
2009-08-20 11:48 ` [alsa-devel] [PATCH 3/3] Add FSI-AK464x sound support for ms7724se Kuninori Morimoto
2009-08-20 11:55 ` [alsa-devel] [PATCH 3/3] Add FSI-AK464x sound support for 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=20090819144547.GB3323@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lethal@linux-sh.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=morimoto.kuninori@renesas.com \
--cc=tiwai@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox