Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Rakesh Ughreja <rakesh.a.ughreja@intel.com>
Cc: alsa-devel@alsa-project.org, vinod.koul@intel.com,
	pierre-louis.bossart@linux.intel.com,
	liam.r.girdwood@linux.intel.com, patches.audio@intel.com,
	broonie@kernel.org
Subject: Re: [RFC v4 0/3] Enable HDA Codec support on Intel Platforms (Series1)
Date: Wed, 27 Dec 2017 10:40:01 +0100	[thread overview]
Message-ID: <s5hlghotspa.wl-tiwai@suse.de> (raw)
In-Reply-To: <1513947132-28089-1-git-send-email-rakesh.a.ughreja@intel.com>

On Fri, 22 Dec 2017 13:52:09 +0100,
Rakesh Ughreja wrote:
> 
> Enhanced HD Audio capabilities introduced in HD Audio controllers are
> added in backward compatible way i.e. it does not change the behavior
> of the controller with respect to HDA Bus and HDA devices.
> 
> Since there is no change in the hardware with respect to the HDA bus and
> HDA device it is more appropriate to represent the same in software as
> well.
> 
> In order to align software representation with hardware it makes more
> sense to have common data structures across device, bus and driver for both
> enhanced HDA controllers and legacy HDA controllers.
> 
> This patch series removes the hdac_ext_device structure, hdac_ext_bus and
> hdac_ext_driver data structures so that legacy and enhanced HDaudio
> capabilities can be handled in a backwards-compatible way without
> separate definitions.
> 
> Once this clean-up is complete, additional patches will allow for
> HDaudio codec support in an ASoC framework without the need to develop
> new codec drivers, thereby enabling the use of the Intel DSP on more
> platforms (currently limited to hdmi).
> 
> Changes in v4:
> - No changes in this series except rebase as there were no comments.
> 
> Changes in v3:
> - No changes in this series except rebase as there were no comments.
> 
> Changes in v2:
> - First three patches from v1 are merged so not included in this series.
> - No changes in this series except rebase as there were no comments.
> 
> Rakesh Ughreja (3):
>   ALSA: hdac: Remove usage of struct hdac_ext_device and use hdac_device
>     instead
>   ALSA: hdac: Remove usage of struct hdac_ext_bus and use hdac_bus
>     instead
>   ALSA: hdac: Remove usage of struct hdac_ext_driver, use hdac_driver
>     instead

These don't seem cleanly applicable to either Mark nor my tree.

Could you rebase so that the recent component cleanups can be
included?


thanks,

Takashi

  parent reply	other threads:[~2017-12-27  9:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-22 12:52 [RFC v4 0/3] Enable HDA Codec support on Intel Platforms (Series1) Rakesh Ughreja
2017-12-22 12:52 ` [RFC v4 1/3] ALSA: hdac: Remove usage of struct hdac_ext_device and use hdac_device instead Rakesh Ughreja
2017-12-22 12:52 ` [RFC v4 2/3] ALSA: hdac: Remove usage of struct hdac_ext_bus and use hdac_bus instead Rakesh Ughreja
2017-12-22 12:52 ` [RFC v4 3/3] ALSA: hdac: Remove usage of struct hdac_ext_driver, use hdac_driver instead Rakesh Ughreja
2017-12-27  9:40 ` Takashi Iwai [this message]
2018-01-02  3:58   ` [RFC v4 0/3] Enable HDA Codec support on Intel Platforms (Series1) 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=s5hlghotspa.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --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=rakesh.a.ughreja@intel.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox