All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] docs: sound: kernel-api: writing-an-alsa-driver.rst: polishing
Date: Thu, 06 Apr 2023 11:04:05 +0200	[thread overview]
Message-ID: <878rf5v0u2.wl-tiwai@suse.de> (raw)
In-Reply-To: <ZC5/OHCWkJImeQ2a@ugly>

On Thu, 06 Apr 2023 10:13:44 +0200,
Oswald Buddenhagen wrote:
> 
> On Thu, Apr 06, 2023 at 09:56:06AM +0200, Takashi Iwai wrote:
> > No, the point is that, if an irq handler misses the multiple period
> > updates, it has to handle the situation in a single shot, and the
> > offset gets corrected to the value within the period size;
> > 
> i know. my point is that if that happens, something must have gone
> more or less terribly wrong already, and we should be thinking about
> how to prevent that, rather than how to "reliably" paper over the
> problem. but i suppose we can give the hardware some slack ... if more
> than two periods are configured.

You can't prevent it perfectly.  The execution of an irq handler may
be delayed by various reasons, and whether it happens or not can't be
deterministic.  The same driver code and the configuration might not
work on a slower machine, too.  So you'll still need to handle such
errors in a proper manner.


thanks,

Takashi

  reply	other threads:[~2023-04-06  9:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-05 20:12 [PATCH] docs: sound: kernel-api: writing-an-alsa-driver.rst: polishing Oswald Buddenhagen
2023-04-06  6:55 ` Takashi Iwai
2023-04-06  7:33   ` Oswald Buddenhagen
2023-04-06  7:56     ` Takashi Iwai
2023-04-06  8:13       ` Oswald Buddenhagen
2023-04-06  9:04         ` Takashi Iwai [this message]
2023-04-06 14:14 ` kernel test robot

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=878rf5v0u2.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=oswald.buddenhagen@gmx.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.