From: Takashi Iwai <tiwai@suse.de>
To: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
Cc: alsa-devel@alsa-project.org, Jaroslav Kysela <perex@perex.cz>
Subject: Re: [PATCH v2] ALSA: emu10k1: track loss of external clock on E-MU cards
Date: Mon, 17 Jul 2023 09:31:59 +0200 [thread overview]
Message-ID: <87sf9nj8nk.wl-tiwai@suse.de> (raw)
In-Reply-To: <20230715160738.326832-1-oswald.buddenhagen@gmx.de>
On Sat, 15 Jul 2023 18:07:38 +0200,
Oswald Buddenhagen wrote:
>
> This uses IRQs to track spontaneous changes to the word clock source
> register.
>
> FWIW, that this can happen in the first place is the reason why it is
> futile to lock the clock source mixer setting while the device is open -
> we can't consistently control the rate anyway. Though arguably, we
> should reset any open streams when that happens, as they become
> corrupted anyway.
>
> Signed-off-by: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
>
> ---
> v2:
> - use driver-local lock instead of core's control_rwsem
>
> ---
> FIXME? while i'm not sure, i think this won't notice seamless switches
> between 44.1 and 48 kHz. assuming that's the case, this seems like a
> minor issue: firstly, just about nothing actually produces such a
> seamless switch - my only device that can even do that is the e-mu card
> itself, but the driver disrupts that by temporarily muting the output.
> secondly, the user is unlikely to select an external source before
> setting it up properly. and the easy workaround is actually never doing
> that.
> regardless, to actually test that i'd need a second e-mu card.
The code change itself looks sane, so I took the patch as is now.
thanks,
Takashi
prev parent reply other threads:[~2023-07-17 7:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-15 16:07 [PATCH v2] ALSA: emu10k1: track loss of external clock on E-MU cards Oswald Buddenhagen
2023-07-17 7:31 ` 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=87sf9nj8nk.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=oswald.buddenhagen@gmx.de \
--cc=perex@perex.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