Hi Wolfram, On 2017-01-09 10:34:20 +0100, Niklas Söderlund wrote: > On 2017-01-04 11:25:50 +0100, Wolfram Sang wrote: > > Bump... > > > > > Yes, this is a bug in the rcar-vin driver which is addressed in the Gen3 > > > patches. However I'm not sure those patches will make it to v4.10, not > > > much review from the V4L2 side yet (Geert and Sergei have had a few > > > comments so there will at lest be one more iteration). > > > > Seems your predictions were correct. I still get: > > > > * OOPS with renesas/dt-for-v4.11 and these patches on top > > * no OOPS with renesas-drivers/master and these patches on top > > > > So, it seems to me that we still should wait with the HDMI related > > patches of this series until the rcar-vin-gen3 branch is in -next. > > D'accord everyone? > > I'm fine with waiting. But as I hinted in my previous email the review > on the rcar-vin-gen3 branch is slow, that is nothing have happened in > that thread since last we spoke of this... > > If this is blocking or other create other issue for you please let me > know and I will do my best to extract the fix and post it separately > from Gen3 enablement. I have now posted a broken out series for rcar-vin which solves this issue. Let's hope we can resolve this blocker with that series. -- Regards, Niklas Söderlund -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
