From owner-freebsd-arm@FreeBSD.ORG Sun Apr 7 07:23:56 2013 Return-Path: Delivered-To: arm@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id DB87D53A; Sun, 7 Apr 2013 07:23:56 +0000 (UTC) (envelope-from hps@bitfrost.no) Received: from mta.bitpro.no (mta.bitpro.no [92.42.64.202]) by mx1.freebsd.org (Postfix) with ESMTP id A0AA01BD8; Sun, 7 Apr 2013 07:23:56 +0000 (UTC) Received: from mail.bitfrost.no (mail.bitfrost.no [46.29.221.36]) by mta.bitpro.no (Postfix) with ESMTP id 07C0D7A1CC; Sun, 7 Apr 2013 09:23:56 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at bitfrost.no Received: from laptop015.hselasky.homeunix.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: hanspetter) by mail.bitfrost.no (Postfix) with ESMTPSA id EE36E20A72; Sun, 7 Apr 2013 09:23:49 +0200 (CEST) Message-ID: <51611F61.3040402@bitfrost.no> Date: Sun, 07 Apr 2013 09:25:21 +0200 From: Hans Petter Selasky Organization: Bitfrost A/S MIME-Version: 1.0 To: Oleksandr Tymoshenko Subject: Re: Beaglebone USB driver (Mentor Graphics OTG) References: <51608AA4.2020804@bluezbox.com> <51611A7B.2010105@bitfrost.no> In-Reply-To: <51611A7B.2010105@bitfrost.no> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: arm@freebsd.org, usb@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Apr 2013 07:23:56 -0000 On 04/07/13 09:04, Hans Petter Selasky wrote: > > 3) Make sure that channels are not generating tokens if they are aborted > / cancelled / timedout. This can not be verified using a USB mass > storage device. Verify this by connecting a USB serial adapter. Try to > open/close /dev/cuaU0. Make sure it does not loose any bytes and that > channel cancel does not hang forever. Hi, I recommend that cancel works like this: 1) Set invalid device address, like 127. 2) Use DMA delay feature to make a 4ms wait (see XHCI driver for example). 3) Free host channel (final). --HPS