All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ramesh Babu <ramesh.babu@intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Vinod Koul <vinod.koul@intel.com>,
	tiwai@suse.de, alsa-devel@alsa-project.org, lgirdwood@gmail.com,
	pathes.audio@intel.com
Subject: Re: [alsa-devel] [RFC 3/3] ALSA: hda - add soc hda bus wrapper
Date: Wed, 8 Apr 2015 10:17:20 +0530	[thread overview]
Message-ID: <20150408044714.GA6212@ramesh.babu@intel.com> (raw)
In-Reply-To: <20150406170804.GQ6023@sirena.org.uk>

On Mon, Apr 06, 2015 at 06:08:04PM +0100, Mark Brown wrote:

Hi Takashi, Mark

> On Thu, Apr 02, 2015 at 03:27:31PM +0530, Vinod Koul wrote:
> 
> 
> > +/**
> > + * hda_device_unregister - unregister a hda device
> > + * @pdev: hda device we're unregistering
> > + *
> > + * Unregistration is done in 2 steps. First we release all resources
> > + * and remove it from the subsystem, then we drop reference count by
> > + * calling hda_device_put().
> > + */
> > +void snd_soc_hdac_device_unregister(struct snd_soc_hdac_device *pdev)
> > +{
> > +	snd_hdac_device_exit(&pdev->hdac);
> > +	snd_hdac_device_unregister(&pdev->hdac);
> > +	snd_soc_hdac_device_put(pdev);
> > +}
> > +EXPORT_SYMBOL_GPL(snd_soc_hdac_device_unregister);
> 
> Takashi queried bits of this too...  I have to say I don't entirely
> understand how this device management is supposed to work and the lack
> of any users in the current series isn't giving me anything to refer to
> here, perhaps it's all obvious given them but I don't have them just
> now.  A lot of this looks like it's boilerplate which should be
> duplicating something device modelish and there certainly seem to be
> some things with object lifetimes that need paying attention to.
> 
> All the commit message says is "create asoc wrppers on top of hdac", can
> we have more words please?

Will fix your comments in next version of the RFC patches.
-- 
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2015-04-08  4:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-02  9:57 [RFC 0/3] ALSA: Add soc hda bus support Vinod Koul
2015-04-02  9:57 ` [RFC 1/3] ALSA: hda - remove assigning dev type inside core Vinod Koul
2015-04-04 12:18   ` Takashi Iwai
2015-04-02  9:57 ` [RFC 2/3] ALSA: hda - add ASoC device type for hda core Vinod Koul
2015-04-02  9:57 ` [RFC 3/3] ALSA: hda - add soc hda bus wrapper Vinod Koul
2015-04-04 12:31   ` Takashi Iwai
2015-04-06 17:08   ` Mark Brown
2015-04-08  4:47     ` Ramesh Babu [this message]
2015-04-08  4:47     ` Ramesh Babu
2015-04-08  6:28 ` [RFC 0/3] ALSA: Add soc hda bus support David Henningsson
2015-04-14  4:22   ` 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=20150408044714.GA6212@ramesh.babu@intel.com \
    --to=ramesh.babu@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=pathes.audio@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.