Searched refs:bMaxPower (Results 1 – 13 of 13) sorted by relevance
287 assert_eq!(c.bMaxPower, 50); in parse_descriptors_mass_storage()362 assert_eq!(c.bMaxPower, 250); in parse_descriptors_servo()534 assert_eq!(c.bMaxPower, 250); in parse_descriptors_adb()606 assert_eq!(c.bMaxPower, 250); in parse_descriptors_multiple_altsettings()
79 pub bMaxPower: u8, field
200 * Reverts the previous API change with regards to bMaxPower.204 guidelines with regards to concurrent use of MaxPower/bMaxPower still apply.208 MaxPower was used instead of bMaxPower, as defined in the specs. If your 322 using the bMaxPower attribute in struct libusb_config_descriptor, the 331 if (dev->config[0].bMaxPower < 250)
189 self.assertEquals(250, descriptor.bMaxPower)
358 __u8 bMaxPower; member
663 uint8_t bMaxPower; member
77047 __u8 bMaxPower; member
91839 __u8 bMaxPower; member
44846 …<var-decl name="bMaxPower" type-id="8f048e17" visibility="default" filepath="include/uapi/linux/us…66094 …<var-decl name="bMaxPower" type-id="8f048e17" visibility="default" filepath="include/uapi/linux/us…
44817 …<var-decl name="bMaxPower" type-id="8f048e17" visibility="default" filepath="include/uapi/linux/us…66080 …<var-decl name="bMaxPower" type-id="8f048e17" visibility="default" filepath="include/uapi/linux/us…