From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 22994C433EF for ; Mon, 24 Jan 2022 20:08:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:Message-ID: Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:References: List-Owner; bh=c7mUoPUZZQlGq4AsZ4t9YWKAOQi8tHz6k/C5R+lRgh8=; b=H+Fj9Liei/A/sB 6FcnC1+KJP8j7sg6gKizdOm9z/vxbqE6SCQ8Qsoqh+NjkQQpLzBIrpi/leBO4Q8nftrNYTLHVWt5z zat9PkcxKGCUBj3A9bgfla+N9HDuEss48M2S+l0d8MtQqCLzKdcvbjP3vhZKWXOlQSnwkEZk9/ACH K85xOvuMmktHJP6Y9oIpQLQ+4mLanQrT/0ZqSZQsjFXYGaSwpSHkShLt6GNlf1XunKFhnaSjU85FZ 0iucRLC44hAcxhMVSqgcyQrLPTzRVRteUAW70Ekkl7TIsi8z8NeOTssylA8mgGguyfIkUioUr1Dhz bmjU1RdQcdOe1KnJBDyQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1nC5c0-005254-QX; Mon, 24 Jan 2022 20:06:48 +0000 Received: from dfw.source.kernel.org ([139.178.84.217]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1nC5bx-00524O-8R for linux-arm-kernel@lists.infradead.org; Mon, 24 Jan 2022 20:06:46 +0000 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 261BE6131E; Mon, 24 Jan 2022 20:06:44 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 47DB4C340E5; Mon, 24 Jan 2022 20:06:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1643054803; bh=tAxMFrZB97HTTzVWzaI/qrmHKlzIq2ip8Mfv5JarAmU=; h=Date:From:To:Cc:Subject:In-Reply-To:From; b=W71W7OVtlJXUuzDFOk4JNI3jFFGpgJEWDwmQccXN2Sp6MvKfTszyA9pNH+/chP+7S AnJDhIObpRrxXfudSNj6cqZXbINuLF5Y7pGb7zr2DC+bd/YXrAaNUNIMeTEWf4yDYE Miir9XGkeks2RYTOw/CQna7HPJn1PIsmfZcYSvuRrXqCzImlUIu32veQcMlzrTXc7b m7EPBYtGKfrGoipdu9cncLKmh6zxvFVDBzcH9cb3sMC/z5AdUZv23XEgSpxWYZbPku o5vOCZTHDMCFCCZolSlNkiDjckOwhjzH/J3uL0nTHS3bntFwFV9inMlyvZL/+MDHHs TjxxMgsR4d90g== Date: Mon, 24 Jan 2022 14:06:41 -0600 From: Bjorn Helgaas To: Alain Volmat Cc: Rob Herring , linux-pci@vger.kernel.org, Patrice Chotard , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Fabrice Gasnier Subject: Re: [PATCH RESEND v2 1/5] dt-bindings: pci: st-pcie: PCIe controller found on STi platforms Message-ID: <20220124200641.GA1546900@bhelgaas> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20220103074731.3651-2-avolmat@me.com> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220124_120645_421347_A0FE678E X-CRM114-Status: GOOD ( 20.54 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Mon, Jan 03, 2022 at 08:47:27AM +0100, Alain Volmat wrote: > Addition of the bindings for the Designware based PCIe controller > that can be found on STi platforms such as STiH407, STiH410 or STiH418. > > Signed-off-by: Alain Volmat > --- > .../devicetree/bindings/pci/snps,dw-pcie.yaml | 2 +- > .../devicetree/bindings/pci/st,st-pcie.yaml | 112 ++++++++++++++++++ > 2 files changed, 113 insertions(+), 1 deletion(-) > create mode 100644 Documentation/devicetree/bindings/pci/st,st-pcie.yaml > > diff --git a/Documentation/devicetree/bindings/pci/snps,dw-pcie.yaml b/Documentation/devicetree/bindings/pci/snps,dw-pcie.yaml > index 9ed0dfba7f89..3a92078128f7 100644 > --- a/Documentation/devicetree/bindings/pci/snps,dw-pcie.yaml > +++ b/Documentation/devicetree/bindings/pci/snps,dw-pcie.yaml > @@ -35,7 +35,7 @@ properties: > maxItems: 5 > items: > enum: [ dbi, dbi2, config, atu, app, elbi, mgmt, ctrl, parf, cfg, link, > - ulreg, smu, mpu, apb, phy ] > + ulreg, smu, mpu, apb, phy, mem-window ] > > num-lanes: > description: | > diff --git a/Documentation/devicetree/bindings/pci/st,st-pcie.yaml b/Documentation/devicetree/bindings/pci/st,st-pcie.yaml > new file mode 100644 > index 000000000000..2fa686d573c3 > --- /dev/null > +++ b/Documentation/devicetree/bindings/pci/st,st-pcie.yaml > @@ -0,0 +1,112 @@ > +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/pci/st,st-pcie.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: PCIe RC controller on ST STi platform > + > +maintainers: > + - Alain Volmat > + > +allOf: > + - $ref: /schemas/pci/snps,dw-pcie.yaml# > + > +properties: > + compatible: > + const: st,stih407-pcie > + > + reg: > + items: > + - description: Controller control and status registers. > + - description: PCIe configuration registers. > + - description: Memory made available to the controller > + > + reg-names: > + items: > + - const: dbi > + - const: config > + - const: mem-window I guess "mem-window" is the range for inbound DMA? Other controllers should have similar ranges. Can we use the same DT reg names used by other controllers instead of adding something new and STi-specific? > + interrupts: > + maxItems: 1 > + > + resets: > + items: > + - description: Controller reset > + - description: Powerdown reset (optional) > + minItems: 1 > + > + reset-names: > + items: > + - const: softreset > + - const: powerdown "softreset" and "powerdown" appear only in this binding. Are they really unique to STi, or can we use the same names used for other controllers? _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel