linux-kernel - Re: Use of drivers/platform and matching include?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAOesGMjxwmr0Vo0Puc-nZntgXLy6D1PTohz=C+fFukP_Eu1iQg@mail.gmail.com>
Date:	Fri, 4 Oct 2013 09:48:41 -0700
From:	Olof Johansson <olof@...om.net>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:	Russell King - ARM Linux <linux@....linux.org.uk>,
	Kumar Gala <galak@...eaurora.org>,
	Linux Kernel list <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	linux-arm-msm@...r.kernel.org
Subject: Re: Use of drivers/platform and matching include?

On Fri, Oct 4, 2013 at 6:22 AM, Greg Kroah-Hartman
<gregkh@...uxfoundation.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/