Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp5976038ybe; Tue, 10 Sep 2019 11:36:12 -0700 (PDT) X-Google-Smtp-Source: APXvYqzzXAW5wbMTs88IU/I30bym94SC7900n8D5FAb87Ntbg+GACjdJJDWQKndESZFxDnnRwlL5 X-Received: by 2002:aa7:c0da:: with SMTP id j26mr32493014edp.40.1568140572168; Tue, 10 Sep 2019 11:36:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1568140572; cv=none; d=google.com; s=arc-20160816; b=JJ1lB3dnV4GX91i9LGmIAYlb0rWlRzCWfL++UsE5rAXQHMODdJhp5+QTo40XEfsBF1 vo5OzIlCjc9hPOG00MxGQt4I1lE6Iujdembp2jh0zzWJenopAsI3jugfcJBH8Cfc5Koi o0+AvBAuqd/cFJGW0P+LWaaqMv4MrmetLih+Ep6PJMlmw6D/p8VXUpNltv/xuw1OXiBx UgJvtj9zrNnIKbN0gjLEQO1/JJIQdvlNLzHI4JVStIZFApW643BuPGOJJg+LiFcYyzgB 1MPuHmdMipq1d/q9jRixpXXQVmlgjOOVF+FjJRT9f4hETJNRfXRr1LQK+RUZDNEIlgS7 3xqQ== 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=6Wt1hD/MRsQkqqV33+GUQZHencJLKuHpXLwImoJRYqM=; b=Uz65eGJbA+srWgfYrR5iwl+ev6Z7pFXzX65XLZ6bpWNvqS9kLJMLocJpH4o4ptAqX1 rZj/e3g9tj7fFPPU7Gc27RRvdRl5QDZdbeMxPfhudOH/9/RekCMBJfsk2QxSSuiAi1eP 2ZXwwkK46CfuBO5dnSytTR1lcrAmJnPV3jPfqjjAU3u3tpZt/LIie00dt/IVCXGdaKe+ QD+D2GC/xb2eAb5fuk3Ik80aVHoVk2UFI54XPmzNNOyBWHyjF4lScgbmbd0yyxOGjr2j UEZK8VafkMgOV+dSnUNEEG00aPRuMvmAkFxt6XXD06eVR8Pbho0DDZ/FFP5OyobbGGYw XgOg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@googlemail.com header.s=20161025 header.b=YHy1qrMk; 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=QUARANTINE sp=QUARANTINE dis=NONE) header.from=googlemail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x22si10353985edi.382.2019.09.10.11.35.48; Tue, 10 Sep 2019 11:36:12 -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=@googlemail.com header.s=20161025 header.b=YHy1qrMk; 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=QUARANTINE sp=QUARANTINE dis=NONE) header.from=googlemail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728720AbfIIRYd (ORCPT + 99 others); Mon, 9 Sep 2019 13:24:33 -0400 Received: from mail-ot1-f67.google.com ([209.85.210.67]:36455 "EHLO mail-ot1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726864AbfIIRYc (ORCPT ); Mon, 9 Sep 2019 13:24:32 -0400 Received: by mail-ot1-f67.google.com with SMTP id 67so13328917oto.3; Mon, 09 Sep 2019 10:24:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=6Wt1hD/MRsQkqqV33+GUQZHencJLKuHpXLwImoJRYqM=; b=YHy1qrMkczFFQ67ktlriXxOyE29+Bp3XIJ4JoIRyg3btuchKYh3OUMaKdFI2UjMXQD RrRefDltC3kmYcSXFqCYXX8o/i3xwLUGhJKwxrsdjspUD65Ya7wHxSH6XKvx5U4vSRBa R+hO9dTTrFgUaQ+8YXuQHV1dOLkj8osB0WquDFeaCIDRWie5SvRJz1hmUQWSbHQpxDvZ A16PEZ+me5Sa+F/aHm8nFPxB7n76Bj7m6w4LF8oG92BkZSQ/xLXI8oovo5IF8eUcl5z7 3QVyGjBIJpEK3RoUqlvuJqdp4nosMcmKI4FVpRdJSOYNH5QgZSq9OSHNmvPBLS/uFN0G HJaA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=6Wt1hD/MRsQkqqV33+GUQZHencJLKuHpXLwImoJRYqM=; b=MgmG8LdnN4madcniVDKBUxE/QDYCjBXhDB1R4OPhKLr8t8D4VNGBEkGkLzGw32fu0L 9FYrbWhHjUF7YfBKWFXyWRIbHxuV2zSkDcvUC5EArzD2z4K30eED67FZr098BDHUu2Eh dNO6mfl3W1Z6L79g6qjQia3UPf93f10gsq8Xqh0ffaNT8OBcujMKhQirPejxQSbZhgQy vigqaRbBZkKfVAvsHEVnvYA+EoUM+hpx1RnqLIJrBA+SfUC+KxEgiI8F4x3YfD+BWdOg Zd+0/gG1dps1WNFDJY9VrTtXpEUlFgABoB/fOiEuzd5fSoh04Ef/jn6XrKF2rehyMgiL dPeQ== X-Gm-Message-State: APjAAAXWoWxyteql+WHtkFeM4lwaN9Gkbw37xQdtunYsFsK1CGeUFmsG 8rjTkaVZh5rLqofr28uZQXizXwa9JUxAtQUwUqLnpw== X-Received: by 2002:a9d:5c0f:: with SMTP id o15mr21270768otk.81.1568049870233; Mon, 09 Sep 2019 10:24:30 -0700 (PDT) MIME-Version: 1.0 References: <1567667251-33466-1-git-send-email-jianxin.pan@amlogic.com> <1567667251-33466-5-git-send-email-jianxin.pan@amlogic.com> In-Reply-To: From: Martin Blumenstingl Date: Mon, 9 Sep 2019 19:24:19 +0200 Message-ID: Subject: Re: [PATCH v2 4/4] arm64: dts: add support for A1 based Amlogic AD401 To: Jianxin Pan Cc: Kevin Hilman , linux-amlogic@lists.infradead.org, Rob Herring , Carlo Caione , Neil Armstrong , Jerome Brunet , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Jian Hu , Hanjie Lin , Xingyu Chen , Victor Wan , Qiufang Dai , Tao Zeng 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 Hi Jianxin, On Mon, Sep 9, 2019 at 2:03 PM Jianxin Pan wrote: > > Hi Martin, > > On 2019/9/7 23:02, Martin Blumenstingl wrote: > > Hi Jianxin, > > > > On Fri, Sep 6, 2019 at 7:58 AM Jianxin Pan wrote: > > [...] > >>> also I'm a bit surprised to see no busses (like aobus, cbus, periphs, ...) here > >>> aren't there any busses defined in the A1 SoC implementation or are > >>> were you planning to add them later? > >> Unlike previous series,there is no Cortex-M3 AO CPU in A1, and there is no AO/EE power domain. > >> Most of the registers are on the apb_32b bus. aobus, cbus and periphs are not used in A1. > > OK, thank you for the explanation > > since you're going to re-send the patch anyways: can you please > > include the apb_32b bus? > > all other upstream Amlogic .dts are using the bus definitions, so that > > will make A1 consistent with the other SoCs > In A1 (and the later C1), BUS is not mentioned in the memmap and register spec. > Registers are organized and grouped by functions, and we can not find information about buses from the SoC document. do you know why the busses are not part of the documentation? > Maybe it's better to remove bus definitions for these chips. my understanding is that devicetree describes the hardware so if there's a bus in hardware (that we know about) then we should describe it in devicetree personally I think busses also make the .dts easier to read: instead of a huge .dts with all nodes on one level it's split into multiple smaller sub-nodes - thus making it easier to keep track of "where am I in this file". Martin