All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, clemens@ladisch.de,
	ffado-devel@lists.sf.net
Subject: Re: [PATCH 0/2 v2] ALSA: oxfw: implement retries for scs1x at transaction failure
Date: Thu, 25 Feb 2016 11:00:59 +0900	[thread overview]
Message-ID: <56CE605B.2000706@sakamocchi.jp> (raw)
In-Reply-To: <s5hbn76dsxi.wl-tiwai@suse.de>

On Feb 25 2016 00:33, Takashi Iwai wrote:
> On Wed, 24 Feb 2016 01:26:31 +0100,
> Takashi Sakamoto wrote:
>>
>> Hi,
>>
>> This patchset updates my former post below. Changes are just adding my sign
>> (I forgot it...) and improvements of commit messages.
>>
>> [alsa-devel] [PATCH 0/2] ALSA: oxfw: implement retries for scs1x at transaction failure
>> http://mailman.alsa-project.org/pipermail/alsa-devel/2016-February/104579.html
>>
>> In thread of the post, I got some comments about work to extend ALSA
>> rawmidi core. I've investigated it in a few days ago and realized that it
>> may not so light work, mainly because of a lack of unified state
>> management[0].
>>
>> In this development cycle, I'd like to give it up and use my time for the
>> other work within my plan for the cycle. Please just apply these two patches.
>>
>> [0] In short, the state management is understandable for developers who
>> can understand it, and I'm not.
>>
>> Regards
>>
>> Takashi Sakamoto (2):
>>    ALSA: oxfw: retry MIDI transferring for scs1x at transaction failure
>>    ALSA: oxfw: discontinue MIDI substream for scs1x at transaction
>>      failure
>
> Applied both now.  Thanks.

Thanks.

ALSA rawmidi core handles substreams for both directions, therefore 
state management may not so simple as we expected (at least, for driver 
based on packet streaming such as IEC 61883-1/6, there're more items to 
be considered. So as USB MIDI Device class, too, I think). I'd like to 
schedule the work to next developing cycle for Linux 4.7 or later.


Regards

Takashi Sakamoto

      reply	other threads:[~2016-02-25  2:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-24  0:26 [PATCH 0/2 v2] ALSA: oxfw: implement retries for scs1x at transaction failure Takashi Sakamoto
2016-02-24  0:26 ` [PATCH 1/2] ALSA: oxfw: retry MIDI transferring " Takashi Sakamoto
2016-02-24  0:26 ` [PATCH 2/2] ALSA: oxfw: discontinue MIDI substream " Takashi Sakamoto
2016-02-24 15:33 ` [PATCH 0/2 v2] ALSA: oxfw: implement retries " Takashi Iwai
2016-02-25  2:00   ` Takashi Sakamoto [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=56CE605B.2000706@sakamocchi.jp \
    --to=o-takashi@sakamocchi.jp \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    --cc=ffado-devel@lists.sf.net \
    --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.