From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Curtis Malainey <cujomalainey@chromium.org>, alsa-devel@alsa-project.org
Cc: Cezary Rojewski <cezary.rojewski@intel.com>,
Kai Vehmanen <kai.vehmanen@linux.intel.com>,
Jie Yang <yang.jie@linux.intel.com>,
Takashi Iwai <tiwai@suse.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Ben Zhang <benzh@chromium.org>, Mac Chiang <mac.chiang@intel.com>,
Mark Brown <broonie@kernel.org>,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
Bard Liao <bardliao@realtek.com>,
Sathya Prakash M R <sathya.prakash.m.r@intel.com>,
Naveen Manohar <naveen.m@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Jon Flatley <jflat@chromium.org>,
Bard liao <yung-chuan.liao@linux.intel.com>,
Allison Randal <allison@lohutok.net>
Subject: Re: [alsa-devel] [PATCH v4] ASoC: intel: Add Broadwell rt5650 machine driver
Date: Wed, 18 Dec 2019 11:57:55 -0600 [thread overview]
Message-ID: <295df05e-e3c6-fed8-50fa-4b2ad87b3057@linux.intel.com> (raw)
In-Reply-To: <20191218143937.122665-1-cujomalainey@chromium.org>
On 12/18/19 8:39 AM, Curtis Malainey wrote:
> From: Ben Zhang <benzh@chromium.org>
>
> Add machine driver for Broadwell + rt5650.
>
> Signed-off-by: Bard Liao <bardliao@realtek.com>
> Signed-off-by: Ben Zhang <benzh@chromium.org>
> Signed-off-by: Mac Chiang <mac.chiang@intel.com>
> Signed-off-by: Jon Flatley <jflat@chromium.org>
> Signed-off-by: Curtis Malainey <cujomalainey@chromium.org>
Acked-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Note that SOF support will require a fix for the back-end definition
below but that should be done on all Broadwell drivers when the on-going
GitHub thread [1] reaches a conclusion
[1] https://github.com/thesofproject/linux/pull/1484
> + /* Back End DAI links */
> + {
> + /* SSP0 - Codec */
> + .name = "Codec",
> + .id = 0,
> + .no_pcm = 1,
> + .dai_fmt = SND_SOC_DAIFMT_DSP_B | SND_SOC_DAIFMT_NB_NF |
> + SND_SOC_DAIFMT_CBS_CFS,
> + .ignore_suspend = 1,
> + .ignore_pmdown_time = 1,
> + .be_hw_params_fixup = broadwell_ssp0_fixup,
> + .ops = &bdw_rt5650_ops,
> + .dpcm_playback = 1,
> + .dpcm_capture = 1,
> + .init = bdw_rt5650_init,
> + SND_SOC_DAILINK_REG(dummy, be, dummy),
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2019-12-18 18:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 14:39 [alsa-devel] [PATCH v4] ASoC: intel: Add Broadwell rt5650 machine driver Curtis Malainey
2019-12-18 17:57 ` Pierre-Louis Bossart [this message]
2019-12-18 20:05 ` [alsa-devel] Applied "ASoC: intel: Add Broadwell rt5650 machine driver" to the asoc tree 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=295df05e-e3c6-fed8-50fa-4b2ad87b3057@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=allison@lohutok.net \
--cc=alsa-devel@alsa-project.org \
--cc=bardliao@realtek.com \
--cc=benzh@chromium.org \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=cujomalainey@chromium.org \
--cc=jflat@chromium.org \
--cc=kai.vehmanen@linux.intel.com \
--cc=krzk@kernel.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=mac.chiang@intel.com \
--cc=naveen.m@intel.com \
--cc=sathya.prakash.m.r@intel.com \
--cc=tglx@linutronix.de \
--cc=tiwai@suse.com \
--cc=yang.jie@linux.intel.com \
--cc=yung-chuan.liao@linux.intel.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