public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "Evan Green" <evgreen@chromium.org>
Cc: <alsa-devel@alsa-project.org>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Amadeusz S*awi*ski" <amadeuszx.slawinski@linux.intel.com>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Jaroslav Kysela" <perex@perex.cz>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ALSA: hda: Use correct start/count for sysfs init
Date: Wed, 26 Jun 2019 10:27:11 +0200	[thread overview]
Message-ID: <s5himsssqe8.wl-tiwai@suse.de> (raw)
In-Reply-To: <20190625215418.17548-1-evgreen@chromium.org>

On Tue, 25 Jun 2019 23:54:18 +0200,
Evan Green wrote:
> 
> The normal flow through the widget sysfs codepath is that
> snd_hdac_refresh_widgets() is called once without the sysfs bool set
> to set up codec->num_nodes and friends, then another time with the
> bool set to actually allocate all the sysfs widgets. However, during
> the first time allocation, hda_widget_sysfs_reinit() ignores the new
> num_nodes passed in via parameter and just calls hda_widget_sysfs_init(),
> using whatever was in codec->num_nodes before the update. This is not
> correct in cases where num_nodes changes. Here's an example:
> 
> Sometime earlier:
> snd_hdac_refresh_widgets(hdac, false)
>   sets codec->num_nodes to 2, widgets is still not allocated
> 
> Now:
> snd_hdac_refresh_widgets(hdac, true)
>   hda_widget_sysfs_reinit(num_nodes=7)
>     hda_widget_sysfs_init()
>       widget_tree_create()
>         alloc(codec->num_nodes) // this is still 2
>   codec->num_nodes = 7
> 
> Pass num_nodes and start_nid down into widget_tree_create() so that
> the right number of nodes are allocated in all cases.
> 
> Signed-off-by: Evan Green <evgreen@chromium.org>

Thanks for the patch.  That's indeed a problem, but I guess a simpler
approach is just to return if sysfs didn't exist.  If the sysfs
entries aren't present at the second call with sysfs=true, it implies
that the codec object will be exposed anyway later, and the sysfs will
be created there.  So, something like below would work instead?


thanks,

Takashi

--- a/sound/hda/hdac_sysfs.c
+++ b/sound/hda/hdac_sysfs.c
@@ -428,7 +428,7 @@ int hda_widget_sysfs_reinit(struct hdac_device *codec,
 	int i;
 
 	if (!codec->widgets)
-		return hda_widget_sysfs_init(codec);
+		return 0;
 
 	tree = kmemdup(codec->widgets, sizeof(*tree), GFP_KERNEL);
 	if (!tree)

  reply	other threads:[~2019-06-26  8:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-25 21:54 [PATCH] ALSA: hda: Use correct start/count for sysfs init Evan Green
2019-06-26  8:27 ` Takashi Iwai [this message]
2019-06-26 20:34   ` Evan Green
2019-06-26 21:16     ` Takashi Iwai
2019-06-26 21:59       ` Evan Green
2019-06-27  5:26         ` Takashi Iwai
2019-06-27 17:39           ` Evan Green

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=s5himsssqe8.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=amadeuszx.slawinski@linux.intel.com \
    --cc=evgreen@chromium.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=tglx@linutronix.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