From owner-freebsd-arm@FreeBSD.ORG  Mon May  5 15:28:21 2014
Return-Path: <owner-freebsd-arm@FreeBSD.ORG>
Delivered-To: freebsd-arm@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id A9F752EF;
 Mon,  5 May 2014 15:28:21 +0000 (UTC)
Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 789BA1991;
 Mon,  5 May 2014 15:28:21 +0000 (UTC)
Received: from c-24-8-230-52.hsd1.co.comcast.net ([24.8.230.52]
 helo=damnhippie.dyndns.org)
 by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256)
 (Exim 4.72) (envelope-from <ian@FreeBSD.org>)
 id 1WhKoV-000LqS-RD; Mon, 05 May 2014 15:28:19 +0000
Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240])
 by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id s45FSFaD023763;
 Mon, 5 May 2014 09:28:15 -0600 (MDT) (envelope-from ian@FreeBSD.org)
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Originating-IP: 24.8.230.52
X-Report-Abuse-To: abuse@dyndns.com (see
 http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse
 reporting information)
X-MHO-User: U2FsdGVkX190HgEdne3tHiCramDckn7o
Subject: Re: USB isochronous traffic with Rasberry Pi [WAS: Re: USB audio
 device on Raspberry Pi]
From: Ian Lepore <ian@FreeBSD.org>
To: Adrian Chadd <adrian@FreeBSD.org>
In-Reply-To: <CAJ-Vmo=XmH-RX6_i13NuAXhq-jTC+WedGiyOMJaPO4r014DSgw@mail.gmail.com>
References: <20140425154430.GA76168@utility-01.thismonkey.com>
 <535A8AEA.1000100@selasky.org> <20140425204134.GA458@cicely7.cicely.de>
 <20140430091411.GA45015@utility-01.thismonkey.com>
 <5360C0A7.9010407@selasky.org>
 <1398867266.22079.51.camel@revolution.hippie.lan>
 <CAGW5k5bZ_bTQUXuzNm=tbwx3npz1_HoOR3vM8TBRVFs8zWCq-w@mail.gmail.com>
 <5362638B.1080104@selasky.org> <5363C133.2000304@selasky.org>
 <53677CB8.5000800@selasky.org>
 <CAJ-Vmo=XmH-RX6_i13NuAXhq-jTC+WedGiyOMJaPO4r014DSgw@mail.gmail.com>
Content-Type: text/plain; charset="us-ascii"
Date: Mon, 05 May 2014 09:28:15 -0600
Message-ID: <1399303695.22079.239.camel@revolution.hippie.lan>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port 
Content-Transfer-Encoding: 7bit
Cc: "freebsd-arm@freebsd.org" <freebsd-arm@FreeBSD.org>
X-BeenThere: freebsd-arm@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: "Porting FreeBSD to ARM processors." <freebsd-arm.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arm/>
List-Post: <mailto:freebsd-arm@freebsd.org>
List-Help: <mailto:freebsd-arm-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 05 May 2014 15:28:21 -0000

On Mon, 2014-05-05 at 08:18 -0700, Adrian Chadd wrote:
> evil idea:
> 
> #define DELAY(ms) _DELAY(ms, __FILE__, __LINE__)
> 
> .. then modify the relevant arm delay function to take FILE/LINE and
> KTR log it. :-)
> 
> 
> -a

Except some uart console output routines are structured like

    while (!readreg(STATUS) & TXRDY)
        DELAY(n);

I don't know why people think that calling delay in busy loops like that
has any value, considering that DELAY is almost always implemented as
some form of

    while (readreg(COUNTER) < target_count)
        ;

I guess maybe it has value only in that it helps you find busy-loops.
I'd rather that we had a function just for that purpose, like

    while (readreg(COUNTER) < target_count)
        cpu_busy_loop();

(We have something like that that's x86-specific, iirc).

-- Ian