From: Nicolin Chen <nicoleotsuka@gmail.com>
To: "Lothar Waßmann" <LW@KARO-electronics.de>,
"Mark Brown" <broonie@kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
Fabio Estevam <fabio.estevam@freescale.com>,
Jaroslav Kysela <perex@perex.cz>,
Liam Girdwood <lgirdwood@gmail.com>,
Takashi Iwai <tiwai@suse.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: fsl: select SND_SOC_FSL_SAI or SND_SOC_FSL_SSI depending on SoC type
Date: Thu, 28 Jan 2016 15:08:47 -0800 [thread overview]
Message-ID: <20160128230846.GA32388@Asurada-Nvidia> (raw)
In-Reply-To: <20160128223352.GB4130@sirena.org.uk>
On Thu, Jan 28, 2016 at 11:33:52PM +0100, Mark Brown wrote:
> On Wed, Jan 20, 2016 at 01:30:38PM +0100, Lothar Waßmann wrote:
>
> > - select SND_SOC_FSL_SSI
> > + select SND_SOC_FSL_SAI if SOC_IMX6UL
> > + select SND_SOC_FSL_SSI if SOC_IMX6Q || SOC_IMX6SL || SOC_IMX6SX
>
> Does this card not work for older i.MXs (which had the same SSI/AUDMUX
> combination as the majority of the i.MX6 family) as well?
It's widely used in older i.MXs according to their DTS files. So
it should be safer to just leave SSI over here.
And I actually doubt the feasibility of running this driver with
i.MX6UL as there might not be an AUDMUX on i.MX6UL since it does
not have SSI any more while the driver always touches the address
space of AUDMUX which may not exist on i.MX6UL.
next prev parent reply other threads:[~2016-01-28 23:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 12:30 [PATCH] ASoC: fsl: select SND_SOC_FSL_SAI or SND_SOC_FSL_SSI depending on SoC type Lothar Waßmann
2016-01-28 22:33 ` Mark Brown
2016-01-28 23:08 ` Nicolin Chen [this message]
2016-01-29 5:51 ` Lothar Waßmann
2016-01-29 6:25 ` Nicolin Chen
2016-01-29 11:33 ` Lothar Waßmann
2016-01-29 5:59 ` Lothar Waßmann
2016-01-29 6:30 ` Nicolin Chen
2016-01-29 9:43 ` Lothar Waßmann
2016-01-29 11:16 ` 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=20160128230846.GA32388@Asurada-Nvidia \
--to=nicoleotsuka@gmail.com \
--cc=LW@KARO-electronics.de \
--cc=alsa-devel@alsa-project.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=fabio.estevam@freescale.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.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