On Thu, Jun 1, 2017 at 9:38 AM, Stephen Boyd <sboyd@xxxxxxxxxxxxxx> wrote: > On 05/24, Linus Walleij wrote: >> I am sorry if you guys are swamped, I just don't know what to do, >> clock drivers are starting to become the bottleneck for everything >> I do. I bet the ARM SoC maintainers must be noticing it too. (...) > Meh. Life happens and msm8660 is about a decade old now and not > something that I can easily review without digging through old > websites to find documentation on the code I worked on 7 years > ago. So sorry, but these sorts of patches are basically > approaching priority none for me and I have to steal time to > review them. Sorry the reference above was mainly to the Gemini SoC clock driver which was blocking ARM consolidation, the fact that this MSM8660 thing was stalled too just got me to think it was related. I understand the MSM8660 is low prio, but the first DragonBoard was pushed to developers en masse in 2012 (yours truly included), which was just half a decade ago, and started the community boards effort from Qualcomm, and yeah, community moves slower than markets usually, the board is still supported by the BSquare company that managed the board release for Qualcomm, I can still login and check schematics and support forums, cool isn't it :D Yours, Linus Walleij -- 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
