From: Vinod Koul <vinod.koul@intel.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: ALSA ML <alsa-devel@alsa-project.org>,
Takashi Iwai <tiwai@suse.de>,
Guneshwor Singh <guneshwor.o.singh@intel.com>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Patches Audio <patches.audio@intel.com>,
Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH] ASoC: Intel: Boards: Add CNL RT274 I2S machine driver
Date: Tue, 28 Nov 2017 21:54:15 +0530 [thread overview]
Message-ID: <20171128162415.GV3187@localhost> (raw)
In-Reply-To: <5bdd77e1-fb83-0626-c377-a457294ca38d@linux.intel.com>
On Mon, Nov 27, 2017 at 08:45:16AM -0600, Pierre-Louis Bossart wrote:
> On 11/27/17 6:44 AM, Guneshwor Singh wrote:
> >Add CNL I2S machine driver using Realtek RT274 codec in I2S mode
> >configured to ssp0.
> >
> >Signed-off-by: Guneshwor Singh <guneshwor.o.singh@intel.com>
> >---
> > sound/soc/intel/boards/Kconfig | 13 ++
> > sound/soc/intel/boards/Makefile | 2 +
> > sound/soc/intel/boards/cnl_rt274.c | 250 +++++++++++++++++++++++++++++++++++++
> > 3 files changed, 265 insertions(+)
> > create mode 100644 sound/soc/intel/boards/cnl_rt274.c
> >
> >diff --git a/sound/soc/intel/boards/Kconfig b/sound/soc/intel/boards/Kconfig
> >index 6f754708a48c..29066f0b744f 100644
> >--- a/sound/soc/intel/boards/Kconfig
> >+++ b/sound/soc/intel/boards/Kconfig
> >@@ -262,4 +262,17 @@ config SND_SOC_INTEL_KBL_RT5663_RT5514_MAX98927_MACH
> > Say Y if you have such a device.
> > If unsure select "N".
> >+config SND_SOC_INTEL_CNL_RT274_MACH
> >+ tristate "ASoC Audio driver for Cannonlake with RT274 I2S mode"
> >+ depends on X86 && ACPI && I2C
> >+ select SND_SOC_INTEL_SST
> >+ depends on SND_SOC_INTEL_SKYLAKE
>
> this is going to conflict with the fixes I am working on.
> Vinod, can this wait a bit?
Hey Pierre,
Since you are still working on the fixes, I guess this can sneak in before.
The machine drivers are typically low hanging in terms on complexity so we
can merge this first followed by the rework you are doing. I think that part
will still take a bit to stabilize and cleanup.
--
~Vinod
next prev parent reply other threads:[~2017-11-28 16:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 12:44 [PATCH] ASoC: Intel: Boards: Add CNL RT274 I2S machine driver Guneshwor Singh
2017-11-27 14:45 ` Pierre-Louis Bossart
2017-11-28 16:24 ` Vinod Koul [this message]
2017-11-28 16:44 ` Pierre-Louis Bossart
2018-05-17 6:37 ` Mark Brown
2018-05-17 18:17 ` Pierre-Louis Bossart
2017-11-28 16:25 ` Vinod Koul
-- strict thread matches above, loose matches on Subject: below --
2017-11-09 3:20 Guneshwor Singh
2017-11-15 4:54 ` Vinod Koul
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=20171128162415.GV3187@localhost \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=guneshwor.o.singh@intel.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=patches.audio@intel.com \
--cc=pierre-louis.bossart@linux.intel.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;
as well as URLs for NNTP newsgroup(s).