From: Vinod Koul <vinod.koul@intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, patches.audio@intel.com,
liam.r.girdwood@linux.intel.com, Mark Brown <broonie@kernel.org>,
Jeeja KP <jeeja.kp@intel.com>,
"Subhransu S. Prusty" <subhransu.s.prusty@intel.com>
Subject: Re: [PATCH v5 2/4] ASoC: Intel - add Skylake HDA audio driver
Date: Tue, 16 Jun 2015 20:55:27 +0530 [thread overview]
Message-ID: <20150616152527.GY28601@localhost> (raw)
In-Reply-To: <s5hk2v4gbrq.wl-tiwai@suse.de>
On Mon, Jun 15, 2015 at 06:46:33PM +0200, Takashi Iwai wrote:
> At Mon, 15 Jun 2015 17:42:02 +0100,
> Mark Brown wrote:
> >
> > On Mon, Jun 15, 2015 at 06:35:16PM +0200, Takashi Iwai wrote:
> > > Mark Brown wrote:
> > > > On Thu, Jun 11, 2015 at 10:03:56PM +0530, Vinod Koul wrote:
> >
> > > > > + for (i = 0; i < num_stream; i++) {
> > > > > + struct hdac_ext_stream *stream =
> > > > > + kzalloc(sizeof(*stream), GFP_KERNEL);
> >
> > > > Still not sure why these are Sky Lake specific?
> >
> > > Currently the allocation and the free of each HDA(-ext) stream are
> > > left to each controller driver. (See the stream object is embedded.)
> >
> > It looks awfully like it's dynamically allocated here...
> >
> > > And, yes, the allocation (especially the assignment of the stream tag)
> > > *is* SKL specific. SKL has some twists in the interpretation of
> > > HD-audio spec.
> >
> > I can see the thing calling these functions being driver specific but as
> > far as I can see all these are doing is allocating structs, initialising
> > them with passed in parameters, putting them on a list and calling a
> > core function on them. It's not the bit taking the decisions, it's just
> > doing mechanical things.
>
> Actually, this can be done a bit more cleanly -- if there will be no
> more additions to the stream object. It wasn't clear, so the
> allocation and free are left to the driver, so far.
Stream object shouldnt be modfied, so in that case should I move this to
core and ext/ ?
--
~Vinod
next prev parent reply other threads:[~2015-06-16 15:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 16:33 [PATCH v5 0/4] ASoC: intel - add skylake PCM driver Vinod Koul
2015-06-11 16:33 ` [PATCH v5 1/4] ASoC: Intel: add Skylake HDA platform driver Vinod Koul
2015-06-11 16:33 ` [PATCH v5 2/4] ASoC: Intel - add Skylake HDA audio driver Vinod Koul
2015-06-15 15:56 ` Mark Brown
2015-06-15 16:35 ` Takashi Iwai
2015-06-15 16:42 ` Mark Brown
2015-06-15 16:46 ` Takashi Iwai
2015-06-16 15:25 ` Vinod Koul [this message]
2015-06-16 15:27 ` Takashi Iwai
2015-06-16 3:52 ` Vinod Koul
2015-06-16 10:28 ` Mark Brown
2015-06-16 15:24 ` Vinod Koul
2015-06-16 15:28 ` Takashi Iwai
2015-06-11 16:33 ` [PATCH v5 3/4] ASoC: Intel - add makefile support for SKL driver Vinod Koul
2015-06-15 15:57 ` Mark Brown
2015-06-15 16:42 ` Takashi Iwai
2015-06-15 18:54 ` Mark Brown
2015-06-16 4:44 ` Vinod Koul
2015-06-16 10:43 ` Mark Brown
2015-06-16 15:22 ` Vinod Koul
2015-06-16 5:01 ` Takashi Iwai
2015-06-16 10:52 ` Mark Brown
2015-06-11 16:33 ` [PATCH v5 4/4] ASoC: intel - adds support for decoupled mode in skl driver 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=20150616152527.GY28601@localhost \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=jeeja.kp@intel.com \
--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