Use of drivers/platform and matching include?

[Olof Johansson]

On Fri, Oct 4, 2013 at 6:22 AM, Greg Kroah-Hartman
<gregkh at linuxfoundation.org> wrote:
> On Fri, Oct 04, 2013 at 12:41:28PM +0100, Russell King - ARM Linux wrote:
>>
>> So, no, there will be no new drivers under arch/arm.  They must be in the
>> drivers subtree somewhere.
>
> I have no objection with this, and encourage it.

Ok, so these are some of the requirements as far as I see it:

* No per-vendor driver dumping ground under drivers/* (i.e. no
drivers/platform/<soc vendor>/)
* No weirdly constructed single-driver directories directly under
drivers/* (we already have a few and should look at moving those)
because nothing else fits
* We need some sort of convention on dependencies. Several of these
are more libraries than drivers, i.e. we'll have cross-calls for
things like queue management, resource allocation, etc. So having a
single location to hold most of these makes sense instead of
everything cross-depending on everything else.

Based on the above, how about we create something like
drivers/resourcemgr to hold these?   I think at least parts of the
mvebu-mbus driver that ended up under drivers/bus might be a fit to
move there. The APM queue allocator would likely be a fit, and maybe
some of the qualcomm stuff. Kumar, what are your thoughts on that?
Greg?


-Olof