Hi, > Field Rsvd0 is reserved field, so patch should not have impact for > other xHCI controllers. Wait, is this a case of Linux failing to zero-initialize something that should be zero initialized before use (why not explain it as such?), or are you suggesting monkeying with internal xHC data at run time, in area which is known to actually be used by at least one implementation? There is no mention of Rsvd0 in the xHCI spec, did you mean RsvdO? Reserved and Opaque, For exclusive use by the xHC. Software shall *not* write this, unless allowed by the vendor. Cadence isn't the only xHC vendor... (There is no mention of "Stream Endpoint Context" either, so maybe you meant "Stream Context" or "Endpoint Context"...) Regards, Michal