From owner-freebsd-usb@FreeBSD.ORG Thu Oct 10 07:32:57 2013 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id ACA80429 for ; Thu, 10 Oct 2013 07:32:57 +0000 (UTC) (envelope-from aseem.jolly@gmail.com) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8E193263B for ; Thu, 10 Oct 2013 07:32:57 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1VUAjw-0002vg-Ch for freebsd-usb@freebsd.org; Thu, 10 Oct 2013 00:32:56 -0700 Date: Thu, 10 Oct 2013 00:32:56 -0700 (PDT) From: "aseem.jolly" To: freebsd-usb@freebsd.org Message-ID: <1381390376377-5850751.post@n5.nabble.com> In-Reply-To: <525649BB.2060906@bitfrost.no> References: <1381274499940-5850403.post@n5.nabble.com> <5254FD72.2050507@bitfrost.no> <1381342263797-5850596.post@n5.nabble.com> <525649BB.2060906@bitfrost.no> Subject: Re: USB device configuration MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 07:32:57 -0000 >It is allowed to set the configuration multiple times. Refer to USB >2.0 specification. In what possible scenario would we want to set the configuration again? I know USB 2.0 specification allows it. I have also tried to modify the code and have sent SET_CONFIGURATION request to the device multiple times, and device didn't report any error. Or do you mean different configurations of a device, if a device supports more that one configuration? >Is this making a difference for you? I have scene a case in which we were unable to attach the umass driver to the device but since USB_DEBUG was not enabled at that time so I was not able to get more information out of it and being extremely intermittent in nature, I am not able to reproduce it again. I am trying to figure out the possible scenarios in which we might end up not attaching the driver to the device. I believe if we are not able to select a configuration then we don't attach the driver to the device. In usb_unconfigure func: udev->curr_config_no = USB_UNCONFIG_NO; udev->curr_config_index = USB_UNCONFIG_INDEX In usb_probe_and_attach func: if (udev->curr_config_index == USB_UNCONFIG_INDEX) { /* do nothing - no configuration has been set */ goto done; } >From the console logs, it is clear that SET_ADDRESS went successfully, have noticed that we have assigned a ugen name to the device and also request to get the String descriptors(Product, Manufacturer etc) went successfully so that make me believe that there might be an error in performing SET_CONFIGURATION request. Do you have any other suggestions? -- View this message in context: http://freebsd.1045724.n5.nabble.com/USB-device-configuration-tp5850403p5850751.html Sent from the freebsd-usb mailing list archive at Nabble.com.