From: Takashi Iwai <tiwai@suse.de>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Cc: alsa-devel@alsa-project.org, Vinod Koul <vinod.koul@intel.com>,
clemens@ladisch.de,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
ffado-devel@lists.sf.net,
"Subhransu S . Prusty" <subhransu.s.prusty@intel.com>
Subject: Re: [PATCH 1/2] ALSA: firewire: process packets in 'struct snd_pcm_ops.ack' callback
Date: Fri, 09 Jun 2017 09:05:57 +0200 [thread overview]
Message-ID: <s5hk24l1vze.wl-tiwai@suse.de> (raw)
In-Reply-To: <0daee982-a2b5-08c2-a029-f4b6de8bbf38@sakamocchi.jp>
On Fri, 09 Jun 2017 09:01:56 +0200,
Takashi Sakamoto wrote:
>
> On Jun 9 2017 15:53, Takashi Iwai wrote:
> >>> From: Takashi Iwai <tiwai@suse.de>
> >>> Subject: [PATCH] ALSA: pcm: Suppress status/control mmap when ack ops is
> >>> present
> >>>
> >>> The drivers using PCM ack ops require the notification whenever
> >>> appl_ptr is updated in general. But when the PCM status/control page
> >>> is mmapped, this notification doesn't happen, per design, thus it's
> >>> not guaranteed to receive the fine-grained updates.
> >>>
> >>> For improving the situation, this patch simply suppresses the PCM
> >>> status/control mmap when ack ops is defined. At least, for all
> >>> existing drivers with ack, this should give more benefit.
> >>>
> >>> Once when we really need the full optimization with status/control
> >>> mmap even using ack ops, we may reconsider the check, e.g. introducing
> >>> a new flag. But, so far, this should be good enough.
> >>
> >> Yes this makes sense and we tested it for us, looks good
> >>
> >> Reveiwed-by: Vinod Koul <vinod.koul@intel.com>
> >> Tested-by: Subhransu S. Prusty <subhransu.s.prusty@intel.com>
> >
> > OK, thanks.
> >
> > If Sakamato-san is happy with this change, I'm going to merge it for
> > 4.13.
>
> I'm writing a long long message about my concern for this patch.
Better to shorten, if you want to convince someone :)
> I'm
> happy if you postpone application to your for-next branch, till next
> week.
OK.
Takashi
next prev parent reply other threads:[~2017-06-09 7:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 0:38 [PATCH 0/3] ALSA: firewire: use .ack callback of PCM operation for packet processing Takashi Sakamoto
2017-06-07 0:38 ` [PATCH 1/2] ALSA: firewire: process packets in 'struct snd_pcm_ops.ack' callback Takashi Sakamoto
2017-06-07 5:59 ` Takashi Iwai
2017-06-07 21:20 ` Takashi Iwai
2017-06-09 3:42 ` Vinod Koul
2017-06-09 6:53 ` Takashi Iwai
2017-06-09 7:01 ` Takashi Sakamoto
2017-06-09 7:05 ` Takashi Iwai [this message]
2017-06-12 22:49 ` Takashi Sakamoto
2017-06-13 12:03 ` Takashi Iwai
2017-06-14 14:34 ` Takashi Sakamoto
2017-06-14 14:52 ` Takashi Iwai
2017-06-15 2:32 ` Takashi Sakamoto
2017-06-15 8:48 ` Takashi Iwai
2017-06-15 17:56 ` Takashi Sakamoto
2017-06-15 19:06 ` Takashi Iwai
2017-06-16 15:00 ` Takashi Sakamoto
2017-06-16 15:08 ` Takashi Sakamoto
2017-06-16 15:45 ` Takashi Iwai
2017-06-18 10:13 ` Takashi Sakamoto
2017-06-18 12:29 ` Takashi Iwai
2017-06-07 0:38 ` [PATCH 2/2] ALSA: fireface: constify ALSA specific operations Takashi Sakamoto
2017-06-07 5:59 ` Takashi Iwai
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=s5hk24l1vze.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=ffado-devel@lists.sf.net \
--cc=o-takashi@sakamocchi.jp \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=subhransu.s.prusty@intel.com \
--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 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).