Searched refs:bMaxPower (Results 1 – 13 of 13) sorted by relevance
110 * Reverts the previous API change with regards to bMaxPower.114 guidelines with regards to concurrent use of MaxPower/bMaxPower still apply.118 MaxPower was used instead of bMaxPower, as defined in the specs. If your 232 using the bMaxPower attribute in struct libusb_config_descriptor, the 241 if (dev->config[0].bMaxPower < 250)
180 c->bMaxPower = config->bMaxPower ? : (CONFIG_USB_GADGET_VBUS_DRAW / 2); in config_buf()395 power = c->bMaxPower ? (2 * c->bMaxPower) : CONFIG_USB_GADGET_VBUS_DRAW; in set_config()
375 .bMaxPower = 1,389 .bMaxPower = 1,1093 power = 2 * eth_config.bMaxPower; in eth_set_config()2199 eth_config.bMaxPower = 4; in eth_bind()2202 rndis_config.bMaxPower = 4; in eth_bind()
217 u8 bMaxPower; member
320 __u8 bMaxPower; member
194 config->bMaxPower*2); in usb_display_conf_desc()409 dev->config.desc.bMaxPower * 2);
75 .bMaxPower = 50,
62 .bMaxPower = 50,
125 .bMaxPower = 50,
169 .bMaxPower = USBTTY_MAXPOWER300 .bMaxPower = USBTTY_MAXPOWER
210 u8 bMaxPower; member
188 self.assertEquals(250, descriptor.bMaxPower)
354 __u8 bMaxPower; member