All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ughreja, Rakesh A" <rakesh.a.ughreja@intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"Koul, Vinod" <vinod.koul@intel.com>,
	"pierre-louis.bossart@linux.intel.com"
	<pierre-louis.bossart@linux.intel.com>,
	"liam.r.girdwood@linux.intel.com"
	<liam.r.girdwood@linux.intel.com>,
	Patches Audio <patches.audio@intel.com>,
	"broonie@kernel.org" <broonie@kernel.org>
Subject: Re: [RFC v2 00/11] Enable HDA Codec support on Intel Platforms (Series2)
Date: Mon, 11 Dec 2017 15:10:32 +0000	[thread overview]
Message-ID: <85DFEED57DC57344B2483EF7BF8CB60579AD2978@BGSMSX104.gar.corp.intel.com> (raw)
In-Reply-To: <s5hbmj5mrts.wl-tiwai@suse.de>



>-----Original Message-----
>From: Takashi Iwai [mailto:tiwai@suse.de]
>Sent: Monday, December 11, 2017 4:53 PM
>To: Ughreja, Rakesh A <rakesh.a.ughreja@intel.com>
>Cc: alsa-devel@alsa-project.org; broonie@kernel.org;
>liam.r.girdwood@linux.intel.com; pierre-louis.bossart@linux.intel.com; Koul, Vinod
><vinod.koul@intel.com>; Patches Audio <patches.audio@intel.com>
>Subject: Re: [RFC v2 00/11] Enable HDA Codec support on Intel Platforms
>(Series2)
>
>On Mon, 11 Dec 2017 11:52:52 +0100,
>Rakesh Ughreja wrote:
>>
>> Many Intel platforms (SKL, KBL) etc. in the market supports enhanced
>> audio capabilities which also includes DSP processing. This patch carry
>> forwards the works that is done in the previous series to enable HD Audio
>> codecs on such platforms.
>>
>> This patch series adds ASoC HDA codec driver for Intel platforms. It is
>> written by reusing the legacy HDA ALSA codec driver. Intention is to
>> maximize the reuse and minimize the changes in the legacy HDA codec driver.
>>
>> I would like to receive feedback before proceeding further on this
>> direction.
>>
>> INFO:
>> - This series is tested on KBL based product (Dell XPS 13).
>> - Basic playback is working with headset and speakers.
>> - HDMI playback is working.
>> - Capture operation is not tested.
>> - More platforms and use cases coverage can be added once we have basic
>>   agreement in terms of the overall approach.
>>
>> Changes in v2:
>> - Using Topology framework to create DAIs and DAI Links
>> - Moved most commonly used functions into a separate file for machine driver
>> - Implemented separate Realtek ASoC HDA Driver driver for Realtek HDA
>codecs.
>>   It is just a driver registration wrapper which reuses the legacy HDA codec
>>   driver. This allows the removes the limitation that was present in v1.
>> - Implemented the review feedback.
>
>Looking through the patchset quickly, I have a mixed feeling with it.
>I see you're trying to get it working with minimal changes, which is

Thanks once again for the quick feedback.

>good in one side.  OTOH, it is unacceptably messy, in special, because
>the device creation and registration phases are mixed up.

I am not sure if I understand this fully. "Device creation and registration
phases are mixed up". If you can explain bit more, I can try to improve
it.

>
>And exporting each codec table doesn't look nice.  We need to find a
>better way...

Do you think accessing the codec table via some EXPORT function
is a better way ?

>
>
>thanks,
>
>Takashi

  reply	other threads:[~2017-12-11 15:10 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-11 10:52 [RFC v2 00/11] Enable HDA Codec support on Intel Platforms (Series2) Rakesh Ughreja
2017-12-11 10:52 ` [RFC v2 01/11] ASoC: Intel: Boards: Machine driver for Intel platforms Rakesh Ughreja
2017-12-11 10:52 ` [RFC v2 02/11] ASoC: Intel: Skylake: Add entry in sst_acpi_mach for HDA codecs Rakesh Ughreja
2017-12-11 10:52 ` [RFC v2 03/11] ASoC: Intel: Skylake: add HDA BE DAIs Rakesh Ughreja
2017-12-11 10:52 ` [RFC v2 04/11] ASoC: Intel: Skylake: use hda_bus instead of hdac_bus Rakesh Ughreja
2017-12-11 10:52 ` [RFC v2 05/11] ALSA: hda - make some of the functions externally visible Rakesh Ughreja
2017-12-11 10:52 ` [RFC v2 06/11] ASoC: hdac_hda: add ASoC based HDA codec driver Rakesh Ughreja
2017-12-11 10:52 ` [RFC v2 07/11] ALSA: hda: add new API snd_hda_asoc_codec_new for ASoC codec drivers Rakesh Ughreja
2017-12-11 10:53 ` [RFC v2 08/11] ASoC: hdac_hda: add DAI, widgets and related ops Rakesh Ughreja
2017-12-11 10:53 ` [RFC v2 09/11] ASoC: hdac_hda: add runtime PM support Rakesh Ughreja
2017-12-11 10:53 ` [RFC v2 10/11] ASoC: patch_realtek: add ASoC based Realtek HDA codec driver patch Rakesh Ughreja
2017-12-11 10:53 ` [RFC v2 11/11] ASoC: Intel: Boards: add support for HDA codecs Rakesh Ughreja
2017-12-11 11:23 ` [RFC v2 00/11] Enable HDA Codec support on Intel Platforms (Series2) Takashi Iwai
2017-12-11 15:10   ` Ughreja, Rakesh A [this message]
2017-12-11 15:21     ` Takashi Iwai
2017-12-11 18:20       ` Ughreja, Rakesh A
2017-12-11 18:49         ` Takashi Iwai
2017-12-12 16:37           ` Ughreja, Rakesh A
2017-12-12 16:50             ` Takashi Iwai
2017-12-12 18:25               ` Ughreja, Rakesh A
2017-12-12 18:21             ` Joël Krähemann
2017-12-12 18:40               ` Ughreja, Rakesh A
2017-12-12 18:51                 ` Joël Krähemann
2017-12-13  5:22                   ` Ughreja, Rakesh A

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=85DFEED57DC57344B2483EF7BF8CB60579AD2978@BGSMSX104.gar.corp.intel.com \
    --to=rakesh.a.ughreja@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=patches.audio@intel.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=tiwai@suse.de \
    --cc=vinod.koul@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.