Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Pavel Hofman <pavel.hofman@insite.cz>
Cc: ALSA development <alsa-devel@alsa-project.org>
Subject: Re: PATCH - ESI Juli driver - works OK
Date: Thu, 20 Mar 2008 12:37:16 +0100	[thread overview]
Message-ID: <s5hwsnxtymr.wl%tiwai@suse.de> (raw)
In-Reply-To: <47E016F8.6030504@insite.cz>

At Tue, 18 Mar 2008 20:24:40 +0100,
Pavel Hofman wrote:
> 
> Takashi Iwai wrote:
> > At Tue, 18 Mar 2008 07:56:11 +0100,
> > Pavel Hofman wrote:
> >> Takashi Iwai wrote:
> >>> At Mon, 17 Mar 2008 16:50:39 +0100,
> >>> Pavel Hofman wrote:
> >>>
> >>> Well, then we'll need to find some point to compromise.  Could you
> >>> repost the patch after reducing the callbacks again?
> >>>
> >>> I'll have also no time from the next week at all -- will be on
> >>> vacation for three weeks.  So, let's kick it out soonish :)
> >>>
> >> Hi,
> >>
> >> I am sorry, the previous patch had some debugs enabled. Here is a fixed 
> >> patch.
> >>
> >> Thanks a lot.
> >>
> >> Pavel.
> >>
> >>
> >> Signed-off-by: Pavel Hofman <dustin at seznam.cz>
> >>
> >> * moving most of clock-specific code to card-specific routines
> >> * support for ESI Juli
> >> * to-be-researched - monitoring of analog/digital inputs
> > 
> > Thanks.  Now I checked the patch and found it much better now.
> > However, I still think the get_rate_index can be omitted by checking
> > the index from the rate list dynamically.  This looks inefficent but
> > improves the readability and reduces the code size better.  Moreover,
> > the snd_pcm_hw's aren't needed to be prepared for each type.
> > 
> > Below is my revised patch.  With this patch, ice->hw_rates must be
> > non-NULL and this is referred in many places.  It cleans up
> > *_internal_clock*() nicely.
> > 
> 
> Well Takashi, you are the real master here, your patch tells. I 
> especially like the smart way you replaced the ugly switch/case 
> structures in juli.c
> 
> The patch works fine, both standard clock as well as Juli.

Thanks for confirming.  I applied the patch to HG tree now.


Takashi

      reply	other threads:[~2008-03-20 11:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-16 12:57 PATCH - ESI Juli driver Pavel Hofman
2008-03-17  7:59 ` Takashi Iwai
2008-03-17  8:57   ` Pavel Hofman
2008-03-17  9:24     ` Takashi Iwai
2008-03-17  9:37       ` Pavel Hofman
2008-03-17 13:04         ` Takashi Iwai
2008-03-17 14:08           ` Pavel Hofman
2008-03-17 15:17             ` Takashi Iwai
2008-03-17 15:50               ` Pavel Hofman
2008-03-17 15:59                 ` Takashi Iwai
2008-03-17 16:39                   ` Pavel Hofman
2008-03-17 23:28                   ` Pavel Hofman
2008-03-18  6:56                   ` PATCH - ESI Juli driver - removed debugs Pavel Hofman
2008-03-18 14:59                     ` Takashi Iwai
2008-03-18 15:59                       ` Pavel Hofman
2008-03-20 14:20                         ` Pavel Hofman
2008-03-20 21:49                           ` PATCH - ESI Juli driver - OK Pavel Hofman
2008-03-18 19:24                       ` PATCH - ESI Juli driver - works OK Pavel Hofman
2008-03-20 11:37                         ` Takashi Iwai [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=s5hwsnxtymr.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=pavel.hofman@insite.cz \
    /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