On 8/18/2016 12:04 PM, Stefan Wahren wrote: > Hi John, > >> John Youn <John.Youn@xxxxxxxxxxxx> hat am 18. August 2016 um 20:03 >> geschrieben: >> >> >> On 8/17/2016 3:17 PM, Stefan Wahren wrote: >>> Hi John, >>> >>>> John Youn <John.Youn@xxxxxxxxxxxx> hat am 17. August 2016 um 23:21 >>>> geschrieben: >>>> >>>> >>>> ... >>>> Ok, yeah, that seems better. >>>> >>>> Can you check if applying just patch 2 and 3 solves the issue? If so I >>>> think we can send those upstream. >>> >>> unfortunately not: >> >> Ok. I'll see if I can come up with a more conservative version of >> patch 4 until I can look at it properly. I'll try to get to this >> sometime next week but I may not be able to get to it until later. > > Great > >> >> In the meantime, specifying the fifo sizes as you've done can serve as >> a workaround. > > Beside of this workaround, do you see any benefit of patch 2/6 from my series? > > I don't want to introduce DT properties which are only useful for workarounds? Does everything work fine if you don't set any parameters, and use my patches from before? If so, and if you're willing to wait for the fix to those patches then I don't see a need for it. They would be useful beyond a workaround, if only for our internal test platform, but we don't need it right away. Regards, John -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
