From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16553 invoked by alias); 21 Oct 2010 18:47:59 -0000 Received: (qmail 16540 invoked by uid 22791); 21 Oct 2010 18:47:58 -0000 X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from hagrid.ecoscentric.com (HELO mail.ecoscentric.com) (212.13.207.197) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 21 Oct 2010 18:47:53 +0000 Received: from localhost (hagrid.ecoscentric.com [127.0.0.1]) by mail.ecoscentric.com (Postfix) with ESMTP id 7383F2F78011 for ; Thu, 21 Oct 2010 19:47:51 +0100 (BST) Received: from mail.ecoscentric.com ([127.0.0.1]) by localhost (hagrid.ecoscentric.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ytWxDtj9LBgh; Thu, 21 Oct 2010 19:47:50 +0100 (BST) From: bugzilla-daemon@bugs.ecos.sourceware.org To: ecos-patches@ecos.sourceware.org Subject: [Bug 1001024] STM32 USB driver and proposed USB API change X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: eCos X-Bugzilla-Component: Patches and contributions X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: chris@zynaptic.com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: low X-Bugzilla-Assigned-To: john@dallaway.org.uk X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: In-Reply-To: References: X-Bugzilla-URL: http://bugs.ecos.sourceware.org/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Date: Thu, 21 Oct 2010 18:47:00 -0000 Message-Id: <20101021184750.363B52F78007@mail.ecoscentric.com> Mailing-List: contact ecos-patches-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-patches-owner@ecos.sourceware.org X-SW-Source: 2010-10/txt/msg00029.txt.bz2 Please do not reply to this email. Use the web interface provided at: http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001024 --- Comment #33 from Chris Holgate 2010-10-21 19:47:48 BST --- (In reply to comment #30) > Is there any way to avoid the blocking usbs_*_start() call when using dynamic > endpoint configuration? I was wondering if the endpoint structs should be > retrieved within usbs_*_wait_until_configured(), which is already a blocking > call, rather than within usbs_*_start(). usbs_*_wait_until_configured() would > not be called from usbs_*_start(). This would make a call to > usbs_*_wait_until_configured() essential rather than advisable but would avoid > a hardware-dependent variation in blocking/non-blocking behaviour of > usbs_*_start(). Does this make sense to you? Yes - that is a cleaner way to do it. At the moment USB class driver implementations are a bit ad-hoc and documenting a recommended set of lifecycle management functions as above would help to add some consistency. > Will the driver re-use the same endpoint structures if the cable is > disconnected and then reconnected? Not necessarily - if the descriptors change or the host selects a different configuration, all bets are off. Any endpoint references held by a class driver should be treated as going out of scope when the USB device leaves the 'configured' state. -- Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.