Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: "Subhransu S. Prusty" <subhransu.s.prusty@intel.com>
Cc: liam.r.girdwood@linux.intel.com, tiwai@suse.de,
	alsa-devel@alsa-project.org, broonie@kernel.org,
	patches.audio@intel.com
Subject: Re: [PATCH v7 0/3] HDA: add extended HDA
Date: Wed, 10 Jun 2015 18:40:41 +0530	[thread overview]
Message-ID: <20150610131041.GU28601@localhost> (raw)
In-Reply-To: <20150610112624.GA4355@vinod.koul@linux.intel.com>

On Wed, Jun 10, 2015 at 04:56:28PM +0530, Subhransu S. Prusty wrote:
> There is an error in this series. Vinod will resend shortly.
> 
Yes some dead code crept in and checkpatch wasnt too happy with few lines,
so I have updated this and resent the fixed series.

Sorry about the noise

-- 
~Vinod
> On Wed, Jun 10, 2015 at 05:03:33PM +0530, Vinod Koul wrote:
> > New HDA controllers from Intel have extended HDA capabilities like multilink,
> > pipe processing, SPIB, GTS etc In order to use them we create an extended
> > HDA bus, controller and stream which uses the extended configuration
> > 
> > Changes in v7:
> > - Feedback from Takashi
> > - removed the macros for register read/writes
> > - add new macros for reg update
> > - fix bus pointer macro
> > - header cleanup on c/h files
> > - new device name ehdaudioiDn
> > - removed flags for ext caps, use pointer only
> > - moved module info to patch 1
> > - sparse check on series
> > - remove codec name in link
> > 
> > Jeeja KP (3):
> >   ALSA: hdac_ext: add extended HDA bus
> >   ALSA: hdac_ext: add hdac extended controller
> >   ALSA: hdac_ext: add extended stream capabilities
> > 
> >  include/sound/hdaudio_ext.h         | 129 ++++++++++++
> >  sound/hda/Kconfig                   |   4 +
> >  sound/hda/Makefile                  |   3 +
> >  sound/hda/ext/Makefile              |   3 +
> >  sound/hda/ext/hdac_ext_bus.c        | 116 +++++++++++
> >  sound/hda/ext/hdac_ext_controller.c | 297 ++++++++++++++++++++++++++
> >  sound/hda/ext/hdac_ext_stream.c     | 402 ++++++++++++++++++++++++++++++++++++
> >  7 files changed, 954 insertions(+)
> >  create mode 100644 include/sound/hdaudio_ext.h
> >  create mode 100644 sound/hda/ext/Makefile
> >  create mode 100644 sound/hda/ext/hdac_ext_bus.c
> >  create mode 100644 sound/hda/ext/hdac_ext_controller.c
> >  create mode 100644 sound/hda/ext/hdac_ext_stream.c
> > 
> > -- 
> > 1.9.1
> > 
> 
> -- 

-- 

  reply	other threads:[~2015-06-10 13:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-10 11:33 [PATCH v7 0/3] HDA: add extended HDA Vinod Koul
2015-06-10 11:26 ` [alsa-devel] " Subhransu S. Prusty
2015-06-10 13:10   ` Vinod Koul [this message]
2015-06-10 11:26 ` Subhransu S. Prusty
2015-06-10 11:33 ` [PATCH v7 1/3] ALSA: hdac_ext: add extended HDA bus Vinod Koul
2015-06-10 11:33 ` [PATCH v7 2/3] ALSA: hdac_ext: add hdac extended controller Vinod Koul
2015-06-10 11:33 ` [PATCH v7 3/3] ALSA: hdac_ext: add extended stream capabilities 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=20150610131041.GU28601@localhost \
    --to=vinod.koul@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=subhransu.s.prusty@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