On Thu, Apr 20, 2017 at 10:53:54AM +0200, Daniel Vetter wrote:

> Related to this is that there's no single stop-shop for driver
> submissions for the arm platform stuff, but it's all split up. Fairly
> often that means at least one of the maintainers doesn't like your
> face, is on vacation or leave, burried for other reasons, or at least
> has slightly different ideas about what color the bikeshed needs to
> be. That makes contributions for people who just want to get their
> driver for a given platform in a pain.

> For non-arm-soc ecosystem drivers things seem a lot more relaxed and
> efficient and sensible.

I really think this is more of a cross subsystem issue than an ARM issue
- I'm seeing it come up just as much with x86 stuff these days as ARM
(more so at the minute, though I think that's just a bit of learning
that's going on).  x86 has historically been simpler hardware with less
interaction between blocks that triggers cross subsystem issues but
that's becoming less and less the case for the laptops.

Most of what I'm seeing these days goes pretty smoothly, and we're
reasonably well decoupled for the common cases so things can make
progress even if one bit does end up getting stuck.  AFAICT the main
issues are the normal maintainer scaling problems.