From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from alsa0.perex.cz (alsa0.perex.cz [77.48.224.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 7B16AC7618D for ; Thu, 6 Apr 2023 08:15:10 +0000 (UTC) Received: from alsa1.perex.cz (alsa1.perex.cz [207.180.221.201]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by alsa0.perex.cz (Postfix) with ESMTPS id AF7CC83E; Thu, 6 Apr 2023 10:14:17 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz AF7CC83E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1680768907; bh=uHW+9DlLgHWLN3Df13GkaCwp2VGkxTJH0P43U1wb318=; h=Date:From:To:Subject:References:In-Reply-To:List-Id:List-Archive: List-Help:List-Owner:List-Post:List-Subscribe:List-Unsubscribe: From; b=QboIP5xTYRTtbGNfyOcodbStXd4eg59vubhOpw0UUyZ/KZEmpjI/Iqfs46uHIOhfL 6G+giNJONYH5CxZUCo2rU9O3OXsY2EWXBd5lZZ3WkW5qw1CdF85TBywPD4hPnD12sU Wa/JPB/lMMNfq/TL29pZYqhpBIKPyWsr/1psjdxo= Received: from mailman-core.alsa-project.org (mailman-core.alsa-project.org [10.254.200.10]) by alsa1.perex.cz (Postfix) with ESMTP id 49824F80149; Thu, 6 Apr 2023 10:13:55 +0200 (CEST) Received: by alsa1.perex.cz (Postfix, from userid 50401) id 4ADE0F80246; Thu, 6 Apr 2023 10:13:51 +0200 (CEST) Received: from bluemchen.kde.org (bluemchen.kde.org [IPv6:2001:470:142:8::100]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa1.perex.cz (Postfix) with ESMTPS id 57FF4F8015B for ; Thu, 6 Apr 2023 10:13:48 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz 57FF4F8015B Received: from ugly.fritz.box (localhost [127.0.0.1]) by bluemchen.kde.org (Postfix) with ESMTP id 7F0AA2420B for ; Thu, 6 Apr 2023 04:13:44 -0400 (EDT) Received: by ugly.fritz.box (masqmail 0.3.4, from userid 1000) id 1pkKka-KSu-00 for ; Thu, 06 Apr 2023 10:13:44 +0200 Date: Thu, 6 Apr 2023 10:13:44 +0200 From: Oswald Buddenhagen To: alsa-devel@alsa-project.org Subject: Re: [PATCH] docs: sound: kernel-api: writing-an-alsa-driver.rst: polishing Message-ID: Mail-Followup-To: alsa-devel@alsa-project.org References: <20230405201220.2197863-1-oswald.buddenhagen@gmx.de> <87pm8hv6sg.wl-tiwai@suse.de> <87fs9dv3zd.wl-tiwai@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <87fs9dv3zd.wl-tiwai@suse.de> Message-ID-Hash: 2RFQOHL2MSFXDDVMUKSGGV3EDYXE5ONL X-Message-ID-Hash: 2RFQOHL2MSFXDDVMUKSGGV3EDYXE5ONL X-MailFrom: ossi@kde.org X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-alsa-devel.alsa-project.org-0; header-match-alsa-devel.alsa-project.org-1; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.8 Precedence: list List-Id: "Alsa-devel mailing list for ALSA developers - http://www.alsa-project.org" Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: 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.