From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1751420AbdBBKQS (ORCPT <rfc822;w@1wt.eu>);
        Thu, 2 Feb 2017 05:16:18 -0500
Received: from gw.crowfest.net ([52.42.241.221]:43504 "EHLO gw.crowfest.net"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1751014AbdBBKQP (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 2 Feb 2017 05:16:15 -0500
Message-ID: <1486030569.18291.1.camel@crowfest.net>
Subject: Re: [RESENT PATCH] ARM: bcm2835: Add devicetree for the Raspberry
 Pi 3, for arm (32)
From: Michael Zoran <mzoran@crowfest.net>
To: Stefan Wahren <stefan.wahren@i2se.com>,
        Gerd Hoffmann <kraxel@redhat.com>, Eric Anholt <eric@anholt.net>
Cc: Mark Rutland <mark.rutland@arm.com>,
        "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
        <devicetree@vger.kernel.org>,
        Russell King <linux@armlinux.org.uk>,
        open list <linux-kernel@vger.kernel.org>,
        Rob Herring <robh+dt@kernel.org>, linux-rpi-kernel@lists.infradead.org,
        "moderated list:ARM PORT" <linux-arm-kernel@lists.infradead.org>
Date: Thu, 02 Feb 2017 02:16:09 -0800
In-Reply-To: <3b3ffeb9-6e92-114c-8fdc-9586bdc68373@i2se.com>
References: <1484845444-4617-1-git-send-email-kraxel@redhat.com>
         <87fukcgsqp.fsf@eliezer.anholt.net> <878tpqki0k.fsf@eliezer.anholt.net>
         <1485944672.1076.50.camel@redhat.com> <1485951653.1076.54.camel@redhat.com>
         <1486024672.11636.1.camel@crowfest.net>
         <3b3ffeb9-6e92-114c-8fdc-9586bdc68373@i2se.com>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.22.4-1 
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Thu, 2017-02-02 at 10:50 +0100, Stefan Wahren wrote:
> Am 02.02.2017 um 09:37 schrieb Michael Zoran:
> > This is actually a problem I had to deal with way in the begging of
> > ARM64.  What was done in the github tree was to have the one of the
> > DTS
> >    files(in this case 64) #include the 32 bit dts.  That way it's
> > not
> > needed to have the symbolic link and install should work.
> > 
> > I know it's ulgy, but it works...
> > 
> > Take a look at:
> > https://github.com/raspberrypi/linux/blob/rpi-4.10.y/arch/arm64/boo
> > t/dt
> > s/broadcom/bcm2710-rpi-3-b.dts
> > 
> > Here is what the file contains:
> > #define RPI364
> > 
> > #include "../../../../arm/boot/dts/bcm2710-rpi-3-b.dts"
> > 
> > 
> > 
> 
> This do not work in the context of the split device-tree repository
> [0] 
> (where the directory structure differs).
> 
> [0] 
> https://git.kernel.org/cgit/linux/kernel/git/devicetree/devicetree-re
> basing.git/

Well, two other options would be to simply duplicate the device tree
files. I know that's a pain...

The other option is choose one or the other(arm64 vs. arm32), I would
guess pick arm32.  It works...  And at this time, arm64 doesn't have a
whole bunch of benefit on the RPI 3.  Perhaps maybe a RPI 4 will come
out someday and we will see more of a gain.