From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30551 invoked by alias); 21 Oct 2010 08:57:59 -0000 Received: (qmail 30517 invoked by uid 22791); 21 Oct 2010 08:57:57 -0000 X-SWARE-Spam-Status: No, hits=1.3 required=5.0 tests=AWL,BAYES_00,BOTNET,RDNS_NONE X-Spam-Check-By: sourceware.org Received: from Unknown (HELO mail.ecoscentric.com) (212.13.207.201) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 21 Oct 2010 08:57:53 +0000 Received: from localhost (hagrid.ecoscentric.com [127.0.0.1]) by mail.ecoscentric.com (Postfix) with ESMTP id 5ABCF2F7800D for ; Thu, 21 Oct 2010 09:57:50 +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 kT0nJjFejd3K; Thu, 21 Oct 2010 09:57:46 +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: john@dallaway.org.uk 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 08:57:00 -0000 Message-Id: <20101021085745.F24062F78008@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/msg00026.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 #30 from John Dallaway 2010-10-21 09:57:39 BST --- (In reply to comment #29) > (In reply to comment #28) > > > I'm concerned that usbs_serial_start() will now block until a connection has > > been established and endpoints have been configured. How will this affect > > the > > implementation multiple function devices over a single USB port where > > multiple > > usbs_*_start() functions may need to be called? I'm thinking that it should > > be > > possible to present both a mass storage device and a serial device (for > > example) over a single physical interface. > > I don't think this scenario is supported by the USB spec - a single end device > can only ever implement a single class driver, as identified by the device > descriptor. To get multiple class drivers running behind a single USB > connector, you would need to emulate a USB hub and hang the class drivers off > the back of that - one per virtual USB slave device. > > While such a feature would be nice to have, it would need quite a bit of extra > work and may require additional features which are not present on the currently > supported hardware. Chris, thanks for your reply. I had assumed that this is how (eg) USB docking stations work. Perhaps they use a vendor-specific class. 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? Will the driver re-use the same endpoint structures if the cable is disconnected and then reconnected? I'm just wanting to check we have all bases covered here. -- 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.