alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>
Subject: Re: [alsa-devel] some lock needed for flush_delayed_work ?
Date: 04 Sep 2019 10:13:36 +0900	[thread overview]
Message-ID: <87pnkgoocf.wl-kuninori.morimoto.gx@renesas.com> (raw)
In-Reply-To: <s5hv9u9vfl6.wl-tiwai@suse.de>


Hi Takashi

Thank you for your feedback

> > I got below error when I unbind/bind CPU DAI.
> > It seems we need to have some kind of lock ?
> 
> No, this kind of error usually is due to the missing initialization of
> the lock object.  In this case, the work hasn't been initialized
> before calling the flush_delayed_work().
> 
> I suppose it's an error path at snd_soc_bind_card(), and the patch
> like below might fix the issue.

I double checked this issue.
It seems below 2 things happend in the same time.
Thank you. Your feedback/hint helped it.
Good things is that there is no issue at upstream code.

	1) latest ASoC branch had delayed_work update
	2) my local patch didn't care about it

Thank you for your help !!
Best regards
---
Kuninori Morimoto
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

      reply	other threads:[~2019-09-04  1:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-03  8:00 [alsa-devel] some lock needed for flush_delayed_work ? Kuninori Morimoto
2019-09-03 10:28 ` Takashi Iwai
2019-09-04  1:13   ` Kuninori Morimoto [this message]

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=87pnkgoocf.wl-kuninori.morimoto.gx@renesas.com \
    --to=kuninori.morimoto.gx@renesas.com \
    --cc=alsa-devel@alsa-project.org \
    --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;
as well as URLs for NNTP newsgroup(s).