From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Takashi Iwai <tiwai@suse.de>, Bard Liao <bardliao@realtek.com>,
alsa-devel@alsa-project.org
Subject: Re: [PATCH 6/6] ASoC: Intel: Add Haswell Machine support
Date: Mon, 24 Feb 2014 19:55:15 +0000 [thread overview]
Message-ID: <1393271715.2323.64.camel@loki> (raw)
In-Reply-To: <20140221052247.GF25940@sirena.org.uk>
On Fri, 2014-02-21 at 14:22 +0900, Mark Brown wrote:
> On Thu, Feb 20, 2014 at 09:48:47PM +0000, Liam Girdwood wrote:
> > Add support for Haswell based machines with SST DSP audio.
>
> Applied, thanks.
>
> > +config SND_SOC_INTEL_HASWELL_MACH
> > + tristate "ASoC Audio DSP support for Intel Haswell Lynxpoint"
> > + depends on SND_SOC_INTEL_SST && X86_INTEL_LPSS
> > + select SND_SOC_INTEL_HASWELL
> > + select SND_SOC_RT5640
> > + help
> > + This adds support for the Lynxpoint Audio DSP on Intel(R) Haswell
> > + Ultrabook platforms.
> > + Say Y if you have such a device
> > + If unsure select "N".
>
> Looks like there's formatting issues here again - tab/space probably.
>
> > +static const struct snd_soc_dapm_route haswell_rt5640_map[] = {
> > +
> > + {"Headphones", NULL, "HPOR"},
> > + {"Headphones", NULL, "HPOL"},
> > + {"IN2P", NULL, "Mic"},
> > +
> > + /* CODEC BE connections */
> > + {"SSP0 CODEC IN", NULL, "AIF1 Capture"},
> > + {"AIF1 Playback", NULL, "SSP0 CODEC OUT"},
> > +};
>
> A DPCM system in mainline! Yay!
>
> > +static int haswell_rt5640_hw_params(struct snd_pcm_substream *substream,
> > + struct snd_pcm_hw_params *params)
> > +{
> > + struct snd_soc_pcm_runtime *rtd = substream->private_data;
> > + struct snd_soc_dai *codec_dai = rtd->codec_dai;
> > + int ret;
> > +
> > + /* Set codec DAI configuration */
> > + ret = snd_soc_dai_set_fmt(codec_dai, SND_SOC_DAIFMT_I2S |
> > + SND_SOC_DAIFMT_NB_NF | SND_SOC_DAIFMT_CBS_CFS);
> > + if (ret < 0) {
> > + dev_err(rtd->dev, "can't set codec DAI configuration\n");
> > + return ret;
> > + }
>
> Set .dai_fmt in the dai_link?
Will update, I think we left that so we could read the DAI fmt from ACPI
in the near future. However, I do intend to read the DAI link from ACPI
in the near future too, so we should construct the DAI link with DAI
format from ACPI at the same time.
>
> > + /* set correct codec filter for DAI format and clock config */
> > + snd_soc_update_bits(rtd->codec, 0x83, 0xffff, 0x8000);
>
> The CODEC driver ought to be figuring out the magic numbers for itself
> really.
I was thinking of a codec public API call for the last one here. I'll
chat with Bard after BYT upstreaming and see what we can come up with.
Liam
next prev parent reply other threads:[~2014-02-24 19:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 21:48 [PATCH 1/6] ASoC: Intel: Add support for Haswell/Broadwell DSP Liam Girdwood
2014-02-20 21:48 ` [PATCH 2/6] ASoC: Intel: Add Haswell/Broadwell IPC Liam Girdwood
2014-02-21 5:03 ` Mark Brown
2014-02-20 21:48 ` [PATCH 3/6] ASoC: Intel: Add Haswell and Broadwell PCM platform driver Liam Girdwood
2014-02-21 5:16 ` Mark Brown
2014-02-21 7:11 ` Takashi Iwai
2014-02-23 3:19 ` Mark Brown
2014-02-24 20:00 ` Liam Girdwood
2014-02-21 7:28 ` Takashi Iwai
2014-02-24 20:07 ` Liam Girdwood
2014-02-20 21:48 ` [PATCH 4/6] ASoC: Intel: Add trace support for Haswell/Broadwell SST IPC messages Liam Girdwood
2014-02-21 5:19 ` Mark Brown
2014-02-24 19:50 ` Liam Girdwood
2014-02-20 21:48 ` [PATCH 5/6] ASoC: Intel: Add build support for Haswell ADSP Liam Girdwood
2014-02-21 5:19 ` Mark Brown
2014-02-20 21:48 ` [PATCH 6/6] ASoC: Intel: Add Haswell Machine support Liam Girdwood
2014-02-21 5:22 ` Mark Brown
2014-02-24 19:55 ` Liam Girdwood [this message]
2014-02-21 5:01 ` [PATCH 1/6] ASoC: Intel: Add support for Haswell/Broadwell DSP Mark Brown
2014-02-21 13:05 ` Jarkko Nikula
2014-02-24 20:09 ` Liam Girdwood
2014-02-24 19:47 ` Liam Girdwood
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=1393271715.2323.64.camel@loki \
--to=liam.r.girdwood@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=bardliao@realtek.com \
--cc=broonie@kernel.org \
--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