Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp1256imm; Thu, 30 Aug 2018 07:01:00 -0700 (PDT) X-Google-Smtp-Source: ANB0VdZZjbRzwD//2QL+RoOOoRzR7OlYKZedknb8iKgcv9o/d67+awAvlYtfoh2nGGdZYngR8gKE X-Received: by 2002:a62:8913:: with SMTP id v19-v6mr10690252pfd.127.1535637660488; Thu, 30 Aug 2018 07:01:00 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1535637660; cv=none; d=google.com; s=arc-20160816; b=kczQGeGWouPFzdlBp+gwjmtdv+Nyyu7FO2JGjJd98qRQW5SUIMfaq4pyThD78Z0v2H FNuhvdcZ0KB/juqNJMSHC2msh2q7z7a2jCeXloAIm9pmkY9sw3Nl/EvmaPKB0hfVxs04 Q1mt4csAD0c7KnMZ6N8PzW5KS7wBG0NZ/VWauqctV2JvRGvM62IQx0IWxDracWksoouP XxPA8mzafFrCEJFX7FoKF+aHF6ptlY4NYMuSYovP+4PnCZaZ+mehYjNAKIjePZwbMdnQ O2ujEWK6lUwV6N2imPv75AAORV3AA823VcKbKzxlmTusbAODJT2bk+DU8YdnQIT4WesA dlnQ== 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 :arc-authentication-results; bh=yjtGhboblhrWCJqYL3hnOWUUQqvvvSL0+k/HfA0mEB4=; b=prgefIS4+2xof3/masg4ENvXhHk+6IweDXU5hOUJh485EZon57HHSvuZhjnYXYujE5 YVHpl18H3xrermnl1BA3VMYfSf3ehRO86aMiC6aWQPfnlP7+e901e7D7LYkqR0fs30lj 7QEXF1EyeLQRTOZiLGAdtESvlFl7KCXUdU04QJx6suur4rUkjbGRpSHPsTdwF8Tvda5P 1w6TJJSFmAevtXZqvW4ftoMR/zI4MwUUzIlKknfjOhv28BpfE0A9xOJCvRyCX+0aDwPv 4xZkXzZM0CjLQmlDrEcAQMYh8Oe3EZ0W8+FzO/sTryYTN2VWGqNyR/v81AjtBPSGlhKA hmGg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=X05bmN+3; 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 d4-v6si6597060pla.299.2018.08.30.07.00.43; Thu, 30 Aug 2018 07:01:00 -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=X05bmN+3; 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 S1729089AbeH3SBs (ORCPT + 99 others); Thu, 30 Aug 2018 14:01:48 -0400 Received: from mail.kernel.org ([198.145.29.99]:38578 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728273AbeH3SBs (ORCPT ); Thu, 30 Aug 2018 14:01:48 -0400 Received: from mail-qt0-f178.google.com (mail-qt0-f178.google.com [209.85.216.178]) (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 AA86520837; Thu, 30 Aug 2018 13:59:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1535637571; bh=NwGv5MOMEk/kYncyPUzRRk51uQVcYw9bZA/AB2YpLYI=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=X05bmN+3h6e9UGvMXL+0c5NVbxo3Sej0hUS0QE5cycFopTm28NxVLt6mkoI/w3FpY Q+cqIY+mPQCs/zjqW1bcb3X2HYBoMocN3vsHoocsSx/leK19sNVxC8l2CwvVxusjnP ybvdHKqaNFx7pha+GBmFj/1RFE/pgSBe1vuhRJ2Y= Received: by mail-qt0-f178.google.com with SMTP id n6-v6so9897268qtl.4; Thu, 30 Aug 2018 06:59:31 -0700 (PDT) X-Gm-Message-State: APzg51B//shgz/GTO1InDr8j356TErsjPR5GA/FugvJ5Bf4LcMrpppNn 40tNbk9MgGX0t01m3ZKbTJgpcDBCQ4Ik3yoWuA== X-Received: by 2002:ac8:148b:: with SMTP id l11-v6mr2131416qtj.27.1535637570855; Thu, 30 Aug 2018 06:59:30 -0700 (PDT) MIME-Version: 1.0 References: <1535096165-45827-1-git-send-email-hanjie.lin@amlogic.com> <1535096165-45827-2-git-send-email-hanjie.lin@amlogic.com> <8c48964151d24758298ba935da336c0829e2b287.camel@baylibre.com> <11d7547b-feb4-6ecb-cef3-db46ce8ee2ef@amlogic.com> <20180829004122.GA25928@bogus> <84d5399c-67d4-f8a4-3613-00d91f21292f@amlogic.com> In-Reply-To: <84d5399c-67d4-f8a4-3613-00d91f21292f@amlogic.com> From: Rob Herring Date: Thu, 30 Aug 2018 08:59:19 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v2 1/2] dt-bindings: PCI: meson: add DT bindings for Amlogic Meson PCIe controller To: Hanjie Lin Cc: Jerome Brunet , Bjorn Helgaas , Yue Wang , Kevin Hilman , "linux-kernel@vger.kernel.org" , linux-pci@vger.kernel.org, "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" , linux-amlogic@lists.infradead.org, Yixun Lan , Liang Yang , Jianxin Pan , Qiufang Dai , Jian Hu , devicetree@vger.kernel.org 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, Aug 30, 2018 at 2:37 AM Hanjie Lin wrote: > > > > On 2018/8/29 8:41, Rob Herring wrote: > > On Mon, Aug 27, 2018 at 04:55:20PM +0800, Hanjie Lin wrote: > >> > >> > >> On 2018/8/24 16:22, Jerome Brunet wrote: > >>> On Fri, 2018-08-24 at 15:36 +0800, Hanjie Lin wrote: > >>>> From: Yue Wang > >>>> > >>>> The Amlogic Meson PCIe host controller is based on the Synopsys DesignWare > >>>> PCI core. This patch adds documentation for the DT bindings in Meson PCIe > >>>> controller. > >>>> > >>>> Signed-off-by: Yue Wang > >>>> Signed-off-by: Hanjie Lin > >>>> --- > >>>> .../devicetree/bindings/pci/amlogic,meson-pcie.txt | 63 ++++++++++++++++++++++ > >>>> 1 file changed, 63 insertions(+) > >>>> create mode 100644 Documentation/devicetree/bindings/pci/amlogic,meson-pcie.txt > >>>> > >>>> diff --git a/Documentation/devicetree/bindings/pci/amlogic,meson-pcie.txt b/Documentation/devicetree/bindings/pci/amlogic,meson-pcie.txt > >>>> new file mode 100644 > >>>> index 0000000..8a831d1 > >>>> --- /dev/null > >>>> +++ b/Documentation/devicetree/bindings/pci/amlogic,meson-pcie.txt > >>>> @@ -0,0 +1,63 @@ > >>>> +Amlogic Meson AXG DWC PCIE SoC controller > >>>> + > >>>> +Amlogic Meson PCIe host controller is based on the Synopsys DesignWare PCI core. > >>>> +It shares common functions with the PCIe DesignWare core driver and > >>>> +inherits common properties defined in > >>>> +Documentation/devicetree/bindings/pci/designware-pci.txt. > >>>> + > >>>> +Additional properties are described here: > >>>> + > >>>> +Required properties: > >>>> +- compatible: > >>>> + should contain "amlogic,axg-pcie" to identify the core. > >>>> +- reg: > >>>> + Should contain the configuration address space. > >>>> +- reg-names: Must be > >>>> + - "elbi" External local bus interface registers > >>>> + - "cfg" Meson specific registers > >>>> + - "config" PCIe configuration space > >>>> +- reset-gpios: The GPIO to generate PCIe PERST# assert and deassert signal. > >>>> +- clocks: Must contain an entry for each entry in clock-names. > >>>> +- clock-names: Must include the following entries: > >>>> + - "pclk" PCIe GEN 100M PLL clock > >>>> + - "port" PCIe_x(A or B) RC clock gate > >>>> + - "general" PCIe Phy clock > >>>> + - "mipi" PCIe_x(A or B) 100M ref clock gate > >>>> +- resets: phandle to the reset lines. > >>>> +- reset-names: must contain "phy" and "peripheral" > >>>> + - "port" Port A or B reset > >>>> + - "apb" APB reset > >>> > >>> The above description is not coherent (phy <=> port) > >>> > >> > >> Yes, this should be port and apb here. > >> We'll integrate phy driver into ctrl driver, and move phy reset to here also. > > > > Why? That's the wrong thing to do if they are separate h/w blocks. You > > can do whatever you like in the drivers, but the DT should reflect the > > h/w. > > > > Rob > > > > . > > > > We have the dedicated phy driver which only process reset job, > and we consider that it's too overkill to do just these things . > So we will integrate phy reset job into the controller driver int the next version. What's in the separate register space you had for the phy? Rob