Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S933806Ab3GWSAA (ORCPT <rfc822;w@1wt.eu>);
	Tue, 23 Jul 2013 14:00:00 -0400
Received: from avon.wwwdotorg.org ([70.85.31.133]:46352 "EHLO
	avon.wwwdotorg.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S933598Ab3GWR76 (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Tue, 23 Jul 2013 13:59:58 -0400
Message-ID: <51EEC49A.4080909@wwwdotorg.org>
Date: Tue, 23 Jul 2013 10:59:54 -0700
From: Stephen Warren <swarren@wwwdotorg.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Pawel Moll <pawel.moll@arm.com>
CC: Rob Herring <robherring2@gmail.com>,
        "grant.likely@linaro.org" <grant.likely@linaro.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        Mark Rutland <Mark.Rutland@arm.com>,
        Ian Campbell <ian.campbell@citrix.com>,
        "rob.herring@calxeda.com" <rob.herring@calxeda.com>,
        Olof Johansson <olof@lixom.net>,
        "devicetree-discuss@lists.ozlabs.org" 
	<devicetree-discuss@lists.ozlabs.org>,
        "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH 3/3] MAINTAINERS: Refactor device tree maintainership
References: <1374290388-19308-1-git-send-email-grant.likely@linaro.org>  <1374290388-19308-3-git-send-email-grant.likely@linaro.org>  <1374511851.3609.10.camel@hornet> <51ED9018.1020003@gmail.com> <1374599667.25700.92.camel@hornet>
In-Reply-To: <1374599667.25700.92.camel@hornet>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 2013
Lines: 56

On 07/23/2013 10:14 AM, Pawel Moll wrote:
> On Mon, 2013-07-22 at 21:03 +0100, Rob Herring wrote:
>> On 07/22/2013 11:50 AM, Pawel Moll wrote:
>>> On Sat, 2013-07-20 at 04:19 +0100, Grant Likely wrote:
>>>> +F:	include/dt-bindings
>>>
>>> One thing we didn't finish talking about was the question if this
>>> directory is supposed to contain *.dtsi files as well? The obvious
>>> problem I have is a vexpress motherboard being (well, actually not bein
>>> right now) shared between arch/arm/boot/dts and arch/arm64/boot/dts.
>>
>> Please no. 
> 
> No as in: no don't put *.dtsi files into include/dt-bindings; or: no, do
> not duplicate the motherboard file?

Don't put *.dtsi into include/dt-bindings, I believe.

> It you meant the latter, this is exactly what I wanted to say: I don't
> want to do that, but there's no way of avoiding it right now.

I think the solution is to introduce some new shared/common location for
shared/common *.dtsi files, into the kernel tree, in the interim.

When *.dts move out of the kernel, this common location can simply be
consumed as part of the DT tree re-organization.

Or perhaps, we could move *.dts around in the kernel to match the
proposed DT tree structure before that point in time?

>> we will still need
>> to copy dt-bindings into the kernel. Also, I think we should move all
>> dts files out of arch subdirs and arrange by vendor or soc family. I'm
>> sure there are some cases that structure doesn't fit well, but there is
>> very little in a dts tied to a cpu architecture.
> 
> I couldn't agree more. So:
> 
> <root>/include/dt-bindings/vendor/*?

> <root>/dts/vendor/*?

I would tend to prefer that option, ...

> <root>/of/vendor/*?
> <root>/dt/vendor/*?

or perhaps that one.

> <root>/drivers/of/vendor/*?

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/