Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp1983176ybe; Thu, 12 Sep 2019 02:38:29 -0700 (PDT) X-Google-Smtp-Source: APXvYqyhkNyRYGTDAg87DgkgKgnkWFMqnmNsVEhnovBg/NywEQirHwZhPjF3a5gelMHiY/bWQoc+ X-Received: by 2002:a50:852c:: with SMTP id 41mr28839576edr.201.1568281109512; Thu, 12 Sep 2019 02:38:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1568281109; cv=none; d=google.com; s=arc-20160816; b=oA5t6yUoOkpojguK7XVGjcjVHt0vxIuysMOAo7O5pRVmhTZiZOlny6I3v8s25d+hA5 9UXjyQ5a+f3IvPEQdldo4Xa7n6aJdPU5/kG1kK9pA7zyHte/4otIdiB5BuYo1EfRAiM4 SHI0++tUkdZPcycdEMyMqEkCa39XmVh5ks90GfX1Tz3pcXK1xesw8db0CuOG3GySges/ 82P2h409VRWe3pL+ExvtdMG8RacEtpDNdhYwnoMvjQdt79NVE6r7WorS37UxzDumavvD 1a+LmWl4f7XgLwUL6OKqaR2BX+HEKrxktUjAfT0We0N74nt8XVnX9bHOSxr6g6F/w+hh VC8A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=o907g5ReEliliHp1jD4CGBcMPQ67MvCxuOBHbk2SLo8=; b=lLiZalBQYQhKwLxDh525cPQbmJfI2SioAY/1mOL1LRsMAjsCf3Skp0B177BHiWyhDn HtXvfESa+ZxaaN5CZTi3bt71nGVqI8kIy3xtaaSAAza//k2RqeDr6Cz4BRzQNh9Vl20Z S27k1tXFEyvDyF6ITKHKB3TlNPjUQUT94GsyGt3fJe4tJyrMqTzH0O4X1ck6xJ2Rr3yu qhNouruD3keQ8tl+rG39pFyo5ZbOpWoIIqUqZfnpral11omIQZOIx3iYDKNCoOD+m7OK eCTkiCACDcgmxRTE6InpJUg8eDhoPO0o7jQdtz/AYiQmqHQ0/FB826SXP7cO4rbWIkUf tkVA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=o1xGloPC; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id dd11si12466846ejb.206.2019.09.12.02.38.06; Thu, 12 Sep 2019 02:38:29 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=o1xGloPC; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730740AbfILJgH (ORCPT + 99 others); Thu, 12 Sep 2019 05:36:07 -0400 Received: from mail.kernel.org ([198.145.29.99]:54734 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730083AbfILJgG (ORCPT ); Thu, 12 Sep 2019 05:36:06 -0400 Received: from mail-lf1-f49.google.com (mail-lf1-f49.google.com [209.85.167.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 0B74E214AE; Thu, 12 Sep 2019 09:36:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1568280965; bh=o907g5ReEliliHp1jD4CGBcMPQ67MvCxuOBHbk2SLo8=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=o1xGloPCicmW15KwhTZntnYk9UgcnskLW5PH/c/xxbRhKaLacFzc8CvB2J+0DQrRc DmH0vr4s84gZGWW7v/kFNjEwG6hvRU2NYJ+PK/IKjPrj+w8caQZ0FzqV6Y9hU3WSXS YX4shUuhOadTXh3H+dc6BQoY5GIQkNJIEmZn7Wi8= Received: by mail-lf1-f49.google.com with SMTP id u3so3654681lfl.10; Thu, 12 Sep 2019 02:36:04 -0700 (PDT) X-Gm-Message-State: APjAAAV/ySBJw6q+9AoSlv7T/95l/EuCgXsOf075O1RUCTefc8OqRXX+ LdjfnfgQVoAodqRaGT9KAGtPFZsyxd5H1TY5pws= X-Received: by 2002:ac2:43b8:: with SMTP id t24mr8235535lfl.24.1568280963225; Thu, 12 Sep 2019 02:36:03 -0700 (PDT) MIME-Version: 1.0 References: <20190911183632.4317-1-krzk@kernel.org> In-Reply-To: From: Krzysztof Kozlowski Date: Thu, 12 Sep 2019 11:35:52 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [GIT PULL 1/2] arm64: dts: exynos: Pull for v5.4 To: Arnd Bergmann , Marek Szyprowski Cc: Olof Johansson , arm-soc , SoC Team , Kukjin Kim , Linux ARM , "moderated list:ARM/SAMSUNG EXYNOS ARM ARCHITECTURES" , "linux-kernel@vger.kernel.org" , DTML Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 12 Sep 2019 at 08:32, Krzysztof Kozlowski wrote: > > On Wed, 11 Sep 2019 at 23:07, Arnd Bergmann wrote: > > > > On Wed, Sep 11, 2019 at 8:36 PM Krzysztof Kozlowski wrote: > > > > > > Hi, > > > > > > Unfortunately the patches were applied right after closing the linux-next. > > > > Hi Krzysztof, > > > > I took a look at these and am not convinced this is right: > > > > > 1. Fix boot of Exynos7 due to wrong address/size of memory node, > > > > The current state is clearly broken and a fix is needed, but > > I'm not sure this is the right fix. Why do you have 32-bit physical > > addressing on a 64-bit chip? I looked at commit ef72171b3621 > > that introduced it, and it seems it would be better to just > > revert back to 64-bit addresses. > > We discussed with Marek Szyprowski that either we can go back to > 64-bit addressing or stick to 32. There are not known boards with more > than 4 GB of RAM so from this point of view the choice was irrelevant. > At the end of discussion I mentioned to stick with other arm64 boards > (although not all), so revert to have 64 bit address... but Marek > chosen differently. Since you ask, let's go back with revert. > > > > > > 2. Move GPU under /soc node, > > > > No problem > > > > > 3. Minor cleanup of #address-cells. > > > > IIRC, an interrupt-controller is required to have a #address-cells > > property, even if that is normally zero. I don't remember the > > details, but the gic binding lists it as mandatory, and I think > > the PCI interrupt-map relies on it. I would just drop this patch. > > Indeed, binding requires both address and size cells. I'll drop it. Short update: no, address-cells are not required by bindings. They are optional. In case of lack of them, the parent address-cells will be used so effectively this patch was changing it from 0 to 1. Anyway this was not expressed in commit msg so I'll drop it. Best regards, Krzysztof