From: "H. Nikolaus Schaller" <hns@goldelico.com> To: Tony Lindgren <tony@atomide.com>, Paul Cercueil <paul@crapouillou.net> Cc: "David Airlie" <airlied@linux.ie>, "Daniel Vetter" <daniel@ffwll.ch>, "Rob Herring" <robh+dt@kernel.org>, "Mark Rutland" <mark.rutland@arm.com>, "Benoît Cousson" <bcousson@baylibre.com>, "Ralf Baechle" <ralf@linux-mips.org>, "Paul Burton" <paulburton@kernel.org>, "James Hogan" <jhogan@kernel.org>, dri-devel <dri-devel@lists.freedesktop.org>, devicetree <devicetree@vger.kernel.org>, "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>, Linux-OMAP <linux-omap@vger.kernel.org>, "OpenPVRSGX Linux Driver Group" <openpvrsgx-devgroup@letux.org>, "Discussions about the Letux Kernel" <letux-kernel@openphoenux.org>, kernel@pyra-handheld.com, linux-mips@vger.kernel.org, "Paul Boddie" <paul@boddie.org.uk> Subject: Re: [PATCH v3 8/8] MIPS: DTS: jz4780: add sgx gpu node Date: Sun, 24 Nov 2019 18:59:07 +0100 [thread overview] Message-ID: <FA810F13-BF2A-4849-9BAA-01FA2F768976@goldelico.com> (raw) In-Reply-To: <20191124174837.GX35479@atomide.com> Hi Paul, Tony, > Am 24.11.2019 um 18:48 schrieb Tony Lindgren <tony@atomide.com>: > > * Paul Cercueil <paul@crapouillou.net> [191124 12:58]: >> Le dim., nov. 24, 2019 at 12:40, H. Nikolaus Schaller <hns@goldelico.com> a >> écrit : >>> and add interrupt and clocks. > ... >>> --- a/arch/mips/boot/dts/ingenic/jz4780.dtsi >>> +++ b/arch/mips/boot/dts/ingenic/jz4780.dtsi >>> @@ -46,6 +46,17 @@ >>> #clock-cells = <1>; >>> }; >>> >>> + gpu: gpu@13040000 { >> >> We try to keep the nodes ordered by address, could you move this node where >> it belongs? > ... Yes, I have noted. > >>> + compatible = "ingenic,jz4780-sgx540-120", "img,sgx540-120", >>> "img,sgx540", "img,sgx5"; >>> + reg = <0x13040000 0x4000>; >>> + >>> + clocks = <&cgu JZ4780_CLK_GPU>; >>> + clock-names = "gpu"; > > Just checking.. Is there something else to configure here > potentially in addition to the clocks? It doesn't look so. Unfortuantely there isn't much information except a v3.18 kernel supported by the vendor and that one also just has a gpu node with clock control. > That is, do we need to do some interconnect specific > configuration etc in addition to the clocks to have > runtime PM work for enabling and disabling sgx on > jz4780? I think we have to leave that open for further study. BR, Nikolaus
WARNING: multiple messages have this Message-ID (diff)
From: "H. Nikolaus Schaller" <hns@goldelico.com> To: Tony Lindgren <tony@atomide.com>, Paul Cercueil <paul@crapouillou.net> Cc: "Mark Rutland" <mark.rutland@arm.com>, devicetree <devicetree@vger.kernel.org>, "Discussions about the Letux Kernel" <letux-kernel@openphoenux.org>, "Paul Burton" <paulburton@kernel.org>, "David Airlie" <airlied@linux.ie>, "James Hogan" <jhogan@kernel.org>, "OpenPVRSGX Linux Driver Group" <openpvrsgx-devgroup@letux.org>, "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>, "Ralf Baechle" <ralf@linux-mips.org>, linux-mips@vger.kernel.org, "Paul Boddie" <paul@boddie.org.uk>, "Rob Herring" <robh+dt@kernel.org>, dri-devel <dri-devel@lists.freedesktop.org>, "Benoît Cousson" <bcousson@baylibre.com>, kernel@pyra-handheld.com, Linux-OMAP <linux-omap@vger.kernel.org> Subject: Re: [PATCH v3 8/8] MIPS: DTS: jz4780: add sgx gpu node Date: Sun, 24 Nov 2019 18:59:07 +0100 [thread overview] Message-ID: <FA810F13-BF2A-4849-9BAA-01FA2F768976@goldelico.com> (raw) Message-ID: <20191124175907.l4RBQJ_IGofnqRKGsoomjeAIkymh98EbuKHrPBiAh3s@z> (raw) In-Reply-To: <20191124174837.GX35479@atomide.com> Hi Paul, Tony, > Am 24.11.2019 um 18:48 schrieb Tony Lindgren <tony@atomide.com>: > > * Paul Cercueil <paul@crapouillou.net> [191124 12:58]: >> Le dim., nov. 24, 2019 at 12:40, H. Nikolaus Schaller <hns@goldelico.com> a >> écrit : >>> and add interrupt and clocks. > ... >>> --- a/arch/mips/boot/dts/ingenic/jz4780.dtsi >>> +++ b/arch/mips/boot/dts/ingenic/jz4780.dtsi >>> @@ -46,6 +46,17 @@ >>> #clock-cells = <1>; >>> }; >>> >>> + gpu: gpu@13040000 { >> >> We try to keep the nodes ordered by address, could you move this node where >> it belongs? > ... Yes, I have noted. > >>> + compatible = "ingenic,jz4780-sgx540-120", "img,sgx540-120", >>> "img,sgx540", "img,sgx5"; >>> + reg = <0x13040000 0x4000>; >>> + >>> + clocks = <&cgu JZ4780_CLK_GPU>; >>> + clock-names = "gpu"; > > Just checking.. Is there something else to configure here > potentially in addition to the clocks? It doesn't look so. Unfortuantely there isn't much information except a v3.18 kernel supported by the vendor and that one also just has a gpu node with clock control. > That is, do we need to do some interconnect specific > configuration etc in addition to the clocks to have > runtime PM work for enabling and disabling sgx on > jz4780? I think we have to leave that open for further study. BR, Nikolaus _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-11-24 17:59 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-11-24 11:40 [PATCH v3 0/8] ARM/MIPS: DTS: add child nodes describing the PVRSGX GPU present in some OMAP SoC and JZ4780 (and many more) H. Nikolaus Schaller 2019-11-24 11:40 ` H. Nikolaus Schaller 2019-11-24 11:40 ` [PATCH v3 1/8] dt-bindings: add img,pvrsgx.yaml for Imagination GPUs H. Nikolaus Schaller 2019-11-24 11:40 ` H. Nikolaus Schaller 2019-12-05 17:01 ` Rob Herring 2019-12-05 17:01 ` Rob Herring 2019-12-17 18:01 ` H. Nikolaus Schaller 2019-12-17 18:01 ` [PATCH v3 1/8] dt-bindings: add img, pvrsgx.yaml " H. Nikolaus Schaller 2019-11-24 11:40 ` [PATCH v3 2/8] ARM: DTS: am33xx: add sgx gpu child node H. Nikolaus Schaller 2019-11-24 11:40 ` H. Nikolaus Schaller 2019-11-24 11:40 ` [PATCH v3 3/8] ARM: DTS: am3517: " H. Nikolaus Schaller 2019-11-24 11:40 ` H. Nikolaus Schaller 2019-11-24 11:40 ` [PATCH v3 4/8] ARM: DTS: omap3: " H. Nikolaus Schaller 2019-11-24 11:40 ` H. Nikolaus Schaller 2019-11-24 11:40 ` [PATCH v3 5/8] ARM: DTS: omap36xx: " H. Nikolaus Schaller 2019-11-24 11:40 ` H. Nikolaus Schaller 2019-11-24 11:40 ` [PATCH v3 6/8] ARM: DTS: omap4: " H. Nikolaus Schaller 2019-11-24 11:40 ` H. Nikolaus Schaller 2019-11-24 11:40 ` [PATCH v3 7/8] ARM: DTS: omap5: " H. Nikolaus Schaller 2019-11-24 11:40 ` H. Nikolaus Schaller 2019-11-24 11:40 ` [PATCH v3 8/8] MIPS: DTS: jz4780: add sgx gpu node H. Nikolaus Schaller 2019-11-24 11:40 ` H. Nikolaus Schaller 2019-11-24 12:57 ` Paul Cercueil 2019-11-24 12:57 ` Paul Cercueil 2019-11-24 17:48 ` Tony Lindgren 2019-11-24 17:48 ` Tony Lindgren 2019-11-24 17:59 ` H. Nikolaus Schaller [this message] 2019-11-24 17:59 ` H. Nikolaus Schaller 2019-11-25 15:46 ` Tony Lindgren 2019-11-25 15:46 ` Tony Lindgren
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=FA810F13-BF2A-4849-9BAA-01FA2F768976@goldelico.com \ --to=hns@goldelico.com \ --cc=airlied@linux.ie \ --cc=bcousson@baylibre.com \ --cc=daniel@ffwll.ch \ --cc=devicetree@vger.kernel.org \ --cc=dri-devel@lists.freedesktop.org \ --cc=jhogan@kernel.org \ --cc=kernel@pyra-handheld.com \ --cc=letux-kernel@openphoenux.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mips@vger.kernel.org \ --cc=linux-omap@vger.kernel.org \ --cc=mark.rutland@arm.com \ --cc=openpvrsgx-devgroup@letux.org \ --cc=paul@boddie.org.uk \ --cc=paul@crapouillou.net \ --cc=paulburton@kernel.org \ --cc=ralf@linux-mips.org \ --cc=robh+dt@kernel.org \ --cc=tony@atomide.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.