All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>,
	shiiba <naoya.shiiba.nx@renesas.com>,
	Takashi Iwai <tiwai@suse.de>, Liam Girdwood <lgirdwood@gmail.com>,
	komatsu <toshiaki.komatsu.ud@renesas.com>,
	Mark Brown <broonie@kernel.org>,
	Hiroyuki Yokoyama <hiroyuki.yokoyama.vx@renesas.com>
Subject: Re: Question about device recovery when under/over run error case
Date: Tue, 19 Jan 2016 21:33:41 +0900	[thread overview]
Message-ID: <569E2D25.4070205@sakamocchi.jp> (raw)
In-Reply-To: <87powy4207.wl%kuninori.morimoto.gx@renesas.com>

On Jan 19 2016 13:42, Kuninori Morimoto wrote:
> I believe snd-soc-rcar is OK at this point,

Could I request you to explain about usage of this lock primitive in SoC
with a few cores (i.e. 2) when dts allows the driver to handle several
PCM substreams and userspace applications try to use the PCM substreams
almost the same time?
http://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/tree/sound/soc/sh/rcar/core.c#n501

It's my concern since I did read your codes.


Regards

Takashi Sakamoto

  reply	other threads:[~2016-01-19 12:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-18  4:45 Question about device recovery when under/over run error case Kuninori Morimoto
2016-01-18  5:03 ` Takashi Sakamoto
2016-01-18  6:04   ` Kuninori Morimoto
2016-01-18  8:29     ` Takashi Iwai
2016-01-19  0:04       ` Kuninori Morimoto
2016-01-19  1:15         ` Takashi Sakamoto
2016-01-19  3:08           ` Kuninori Morimoto
2016-01-19  3:21             ` Takashi Sakamoto
2016-01-19  4:42               ` Kuninori Morimoto
2016-01-19 12:33                 ` Takashi Sakamoto [this message]
2016-01-20  1:17                   ` Kuninori Morimoto
2016-01-20  3:19                     ` Takashi Sakamoto

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=569E2D25.4070205@sakamocchi.jp \
    --to=o-takashi@sakamocchi.jp \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=hiroyuki.yokoyama.vx@renesas.com \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=lgirdwood@gmail.com \
    --cc=naoya.shiiba.nx@renesas.com \
    --cc=tiwai@suse.de \
    --cc=toshiaki.komatsu.ud@renesas.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.