Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp1169864ybl; Thu, 22 Aug 2019 10:19:07 -0700 (PDT) X-Google-Smtp-Source: APXvYqwh9fScpAU0GwxUFRZujhgbVyjHNtvpVOvKYGrSjPTN2u2fY9syMGkDdHbYog9vjQgBnCQA X-Received: by 2002:aa7:9a52:: with SMTP id x18mr319903pfj.8.1566494347839; Thu, 22 Aug 2019 10:19:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566494347; cv=none; d=google.com; s=arc-20160816; b=pYLmpR4jhXD0UArB4d260SUrThyph/gqJyS+in6t77YQZvDDnv3nMm91MYqNtyCEBq i42LDAoZi+1lgzdN0vuNPajaHHa3JWH4Dbq2iSgMngN2tQHaKWiLDxoneunUYuej1Vv4 uXVlx6hbJ6J8iYmpE1A9X8TmqC2cjjWK2PDqei1IAu8TqF0gw4lglgFc8bOh+KiQ9Khv Oi3rkcxyjy4RAiRjA+sj4y5ZGkXGxs6QuPo6hHWkV1pjAR0DzAfd+hvWNKnQoYGFDyYF s4xGDkDyZJcxHEGQA/J0pDfxoWZKaDGsyGVkG9AaGIrrm+hTyFH6ooNxEb3fwoZQxsrd 7Jwg== 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=5oaBjsKQBY8ZvTwaj9Z5Ucb6qfbweeKK4LoU7bVUOPE=; b=d5uI2+Zg/PUnKREcS0Pixf1DVw3jYchTn7XtdQXZCjJ6gNah+sbt7gzn9lK4/8oMmD wBC0d7Z6RMIRHAc9hT+tvnfeTrZeC1RitaqICYL2gjnRAahAvcmy767JQn6rOFUeqaSm Tnp5mbyZn/tRUiaWhdq4qAyS12AMTe2hnPH5D5WkFO1MAd6TAxazN9P4MORxWDQqoCB5 mj67jTzlRso+2eW3Vv269TD9F0H2CS1bMnYxD4Psl1C18JLwSg7LLbUAyiuhPHUp2LHJ fLtFFt5HtpFw4x7WN2GKYbXQsUzvlLqQqK0cXyeVQTk8ne3ErbFqemT6iqjlVUBfIu/X OCsg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=BesAFVzs; 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 c25si164781pfi.256.2019.08.22.10.18.52; Thu, 22 Aug 2019 10:19:07 -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=BesAFVzs; 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 S2389753AbfHVQHy (ORCPT + 99 others); Thu, 22 Aug 2019 12:07:54 -0400 Received: from mail.kernel.org ([198.145.29.99]:37282 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1732004AbfHVQHy (ORCPT ); Thu, 22 Aug 2019 12:07:54 -0400 Received: from mail-qt1-f180.google.com (mail-qt1-f180.google.com [209.85.160.180]) (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 CDA6423401; Thu, 22 Aug 2019 16:07:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1566490073; bh=+vvqhUd+pkM/dp0wpCvzhG8McGJK25Nvoqw+tfejM2Y=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=BesAFVzsDotV2IgMK8BrzUQ6H08d8AhjQZad8fkGpQAuLyaczM4gn9965kE5D/EIL Z3ix5KFGpfNqdbELyObfDVup9RQvgevYv9BkzNTdP7BJ/a3gMQLisQjTAiYtvPxv5D 8OXLZNNts4YEbHYVSSaxqs+9aaAmipwa8ppION2s= Received: by mail-qt1-f180.google.com with SMTP id i4so8300782qtj.8; Thu, 22 Aug 2019 09:07:52 -0700 (PDT) X-Gm-Message-State: APjAAAXTOYKQc0w3CuLl+u5GeJUngl2RaoNATfu11SnzKxhTongP9wYo nD41torosYeY9K3nMNrKs9ComcYNWPx2chpUYw== X-Received: by 2002:a0c:eb92:: with SMTP id x18mr96839qvo.39.1566490071850; Thu, 22 Aug 2019 09:07:51 -0700 (PDT) MIME-Version: 1.0 References: <20190822143703.13030-1-masneyb@onstation.org> <20190822143703.13030-3-masneyb@onstation.org> In-Reply-To: <20190822143703.13030-3-masneyb@onstation.org> From: Rob Herring Date: Thu, 22 Aug 2019 11:07:39 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v6 2/7] dt-bindings: display: msm: gmu: add optional ocmem property To: Brian Masney Cc: Andy Gross , Rob Clark , Sean Paul , Bjorn Andersson , David Airlie , Daniel Vetter , Mark Rutland , Jonathan Marek , linux-arm-msm , "linux-kernel@vger.kernel.org" , dri-devel , freedreno , devicetree@vger.kernel.org, Jordan Crouse 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 22, 2019 at 9:37 AM Brian Masney wrote: > > Some A3xx and A4xx Adreno GPUs do not have GMEM inside the GPU core and > must use the On Chip MEMory (OCMEM) in order to be functional. Add the > optional ocmem property to the Adreno Graphics Management Unit bindings. > > Signed-off-by: Brian Masney > --- > Changes since v5: > - rename ocmem property to sram to match what TI currently has. > > Changes since v4: > - None > > Changes since v3: > - correct link to qcom,ocmem.yaml > > Changes since v2: > - Add a3xx example with OCMEM > > Changes since v1: > - None > > .../devicetree/bindings/display/msm/gmu.txt | 50 +++++++++++++++++++ > 1 file changed, 50 insertions(+) > > diff --git a/Documentation/devicetree/bindings/display/msm/gmu.txt b/Documentation/devicetree/bindings/display/msm/gmu.txt > index 90af5b0a56a9..2305a2aede5a 100644 > --- a/Documentation/devicetree/bindings/display/msm/gmu.txt > +++ b/Documentation/devicetree/bindings/display/msm/gmu.txt > @@ -31,6 +31,10 @@ Required properties: > - iommus: phandle to the adreno iommu > - operating-points-v2: phandle to the OPP operating points > > +Optional properties: > +- sram: phandle to the On Chip Memory (OCMEM) that's present on some Snapdragon > + SoCs. See Documentation/devicetree/bindings/sram/qcom,ocmem.yaml. > + > Example: > > / { > @@ -63,3 +67,49 @@ Example: > operating-points-v2 = <&gmu_opp_table>; > }; > }; > + > +a3xx example with OCMEM support: > + > +/ { > + ... > + > + gpu: adreno@fdb00000 { > + compatible = "qcom,adreno-330.2", > + "qcom,adreno"; > + reg = <0xfdb00000 0x10000>; > + reg-names = "kgsl_3d0_reg_memory"; > + interrupts = ; > + interrupt-names = "kgsl_3d0_irq"; > + clock-names = "core", > + "iface", > + "mem_iface"; > + clocks = <&mmcc OXILI_GFX3D_CLK>, > + <&mmcc OXILICX_AHB_CLK>, > + <&mmcc OXILICX_AXI_CLK>; > + sram = <&ocmem>; Shouldn't this point to gmu-sram@0? You can always get the parent from the child which is a bit easier than the other way around. > + power-domains = <&mmcc OXILICX_GDSC>; > + operating-points-v2 = <&gpu_opp_table>; > + iommus = <&gpu_iommu 0>; > + }; > + > + ocmem: ocmem@fdd00000 { > + compatible = "qcom,msm8974-ocmem"; > + > + reg = <0xfdd00000 0x2000>, > + <0xfec00000 0x180000>; > + reg-names = "ctrl", > + "mem"; > + > + clocks = <&rpmcc RPM_SMD_OCMEMGX_CLK>, > + <&mmcc OCMEMCX_OCMEMNOC_CLK>; > + clock-names = "core", > + "iface"; > + > + #address-cells = <1>; > + #size-cells = <1>; > + > + gmu-sram@0 { > + reg = <0x0 0x100000>; > + }; > + }; > +}; > -- > 2.21.0 >