On Wed, Jun 3, 2015 at 5:29 AM, Olli Salonen <olli.salonen@xxxxxx> wrote: > I'm seeing the same issue as well. I thought that maybe some recent > Si2168 changes did impact this, but it does not seem to be the case. We've had a couple of people raise this so its highly likely we have an issue. I had some patches to the 2168 driver to add support for a new firmware revision. The last time I tested the HVR2205 I convinced myself those were not required, thus I discarded those and re-tested. Probably a warm boot. If the GPIOs aren't truly resetting the SI2168 and thus a warm boot didn't flush the firmware, I suspect dropping the patches would have no immediate effect until a full power-down took place. I'm wondering whether the testing was invalid and indeed we have a problem in the field, as well as a GPIO issue. Two potential issues. I'll schedule sometime later this week to fire up my HVR22xx dev platform and re-validate the 2205. Thanks for raising this. -- Steven Toth - Kernel Labs http://www.kernellabs.com -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
