[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1482809386.3862.5.camel@canonical.com>
Date: Tue, 27 Dec 2016 11:29:46 +0800
From: Shrirang Bagul <shrirang.bagul@...onical.com>
To: Mark Brown <broonie@...nel.org>,
Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>
Cc: alsa-devel@...a-project.org,
Jorge Fernandez Monteagudo <jorgefm@...sa.com>,
Arnd Bergmann <arnd@...db.de>,
Liam Girdwood <lgirdwood@...il.com>,
Vinod Koul <vinod.koul@...el.com>,
linux-kernel@...r.kernel.org, Takashi Iwai <tiwai@...e.com>,
Ramesh Babu <ramesh.babu@...el.com>,
Ben Zhang <benzh@...omium.org>,
John Keeping <john@...anate.com>,
Sathyanarayana Nujella <sathyanarayana.nujella@...el.com>,
Colin Ian King <colin.king@...onical.com>,
Jeeja KP <jeeja.kp@...el.com>
Subject: Re: [alsa-devel] [PATCH 2/2] ASoC: Intel: boards: Add Baytrail
RT5660 machine driver
On Mon, 2016-12-19 at 16:44 +0000, Mark Brown wrote:
> On Mon, Dec 19, 2016 at 10:30:09AM -0600, Pierre-Louis Bossart wrote:
>
> > All this code seems to be largely a copy-paste of the bytcr_rt5640 machine
> > driver and the same comments would apply there. This patch did miss the last
>
> Yes, there's a lot of room for cleanups in the existing code too (and of
> course if there's such a large amount of cut'n'paste that implies that
> there should be some code reuse going on).
Thank you for the review and valuable comments. Following the discussion so far,
I feel the proper way would be to adapt bytcr_rt5660 machine driver to manage
RT5660 codec.
>
> > correction merged by Mark to deal with errors "ASoC: Intel: bytcr_rt5640:
> > fallback mechanism if MCLK is not enabled" and the same error handling would
> > be needed.
>
> There was a cut back version of it I thought?
Will try and include the MCLK fallback patch in ver. 2 of the patch.
Download attachment "signature.asc" of type "application/pgp-signature" (842 bytes)
Powered by blists - more mailing lists