All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kai Vehmanen <kai.vehmanen@linux.intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	Kai Vehmanen <kai.vehmanen@linux.intel.com>,
	Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
Subject: Re: [alsa-devel] [PATCH] ASoC: SOF: intel: Fix probe error without i915 graphics
Date: Mon, 17 Feb 2020 16:21:37 +0200 (EET)	[thread overview]
Message-ID: <alpine.DEB.2.21.2002171612320.2957@eliteleevi.tm.intel.com> (raw)
In-Reply-To: <s5hk14lgvy6.wl-tiwai@suse.de>

Hey,

On Mon, 17 Feb 2020, Takashi Iwai wrote:

> On Mon, 17 Feb 2020 14:17:54 +0100, Kai Vehmanen wrote:
> >  snd_hdac_i915_exit() calls
> >    -> snd_hdac_acomp_exit(), which again calls
> >    -> component.c:component_master_del(dev, &hdac_component_master_ops);
> >    -> component.c:take_down_master()
> >    -> devres.c:devres_release_group(master->dev, NULL);
> > 
> > ...  now that is somewhat suprising. Basicly that goes on to release all 
> > devres resources for the hdac_bus device (not just those related to 
> > acomp!).
> 
> Does it really?  I thought it applies only to the group, and id=NULL
> indicating that it's a local group that was created with id=NULL (by
> address match).

at least in my tests, acomp_exit() ended up releasing a bunch of devres 
allocations made with devm_kzalloc() that had no relation to acomp. I 
noted that in devres.c:find_group(), docs say:

/* Find devres group with ID @id.  If @id is NULL, look for the latest. */
static struct devres_group * find_group(struct device *dev, void *id)

... I don't see how it would be limiting a local group.

Br, Kai
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2020-02-17 14:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-16 20:35 [alsa-devel] [PATCH] ASoC: SOF: intel: Fix probe error without i915 graphics Takashi Iwai
2020-02-17  9:11 ` Kai Vehmanen
2020-02-17  9:17   ` Takashi Iwai
2020-02-17  9:45     ` Kai Vehmanen
2020-02-17 13:17 ` Kai Vehmanen
2020-02-17 13:55   ` Takashi Iwai
2020-02-17 14:21     ` Kai Vehmanen [this message]
2020-02-17 14:25       ` Takashi Iwai
2020-02-18 11:12         ` Kai Vehmanen

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=alpine.DEB.2.21.2002171612320.2957@eliteleevi.tm.intel.com \
    --to=kai.vehmanen@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=ranjani.sridharan@linux.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 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.