All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: soc@kernel.org
Cc: arm@kernel.org, linux-omap@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	"Tony Lindgren" <tony@atomide.com>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
	"Rob Herring" <robh@kernel.org>, "Nishanth Menon" <nm@ti.com>,
	"Vignesh Raghavendra" <vigneshr@ti.com>,
	"Andrew Davis" <afd@ti.com>
Subject: [GIT PULL] Add PowerVR Series5 SGX GPUs for the TI SoCs
Date: Mon, 26 Feb 2024 12:36:12 +0200	[thread overview]
Message-ID: <pull-1708943489-872615@atomide.com> (raw)

From: "Tony Lindgren" <tony@atomide.com>

The following changes since commit 6613476e225e090cc9aad49be7fa504e290dd33d:

  Linux 6.8-rc1 (2024-01-21 14:11:32 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/sgx-for-v6.9-signed

for you to fetch changes up to 21cfb2ba471bde8fefc327f4c8e2af9499f5173d:

  arm64: dts: ti: k3-am654-main: Add device tree entry for SGX GPU (2024-01-26 09:43:23 +0200)

----------------------------------------------------------------
Add PowerVR Series5 SGX GPUs for the TI SoCs

With the Imagination Rogue GPU binding added, let's also add the devicetree
binding for earlier SGX GPUs. Let's also patch the TI SoCs for the related
SGX GPU nodes.

Based on the mailing list discussions, the conclusion was that we need two
separate device tree bindings, one for Rogue and upcoming GPUS, and one for
the older SGX GPUs.

For merging the changes, I applied the binding changes together with the
TI SoC related changes into a branch leaving out the sun6i and mips changes
as suggested by Rob.

These changes are mostly 32-bit SoCs, but also contains one arm64 change.
It does not cause any merge conflicts.

----------------------------------------------------------------
Andrew Davis (9):
      dt-bindings: gpu: Rename img,powervr to img,powervr-rogue
      dt-bindings: gpu: Add PowerVR Series5 SGX GPUs
      ARM: dts: omap3: Add device tree entry for SGX GPU
      ARM: dts: omap4: Add device tree entry for SGX GPU
      ARM: dts: omap5: Add device tree entry for SGX GPU
      ARM: dts: AM33xx: Add device tree entry for SGX GPU
      ARM: dts: AM437x: Add device tree entry for SGX GPU
      ARM: dts: DRA7xx: Add device tree entry for SGX GPU
      arm64: dts: ti: k3-am654-main: Add device tree entry for SGX GPU

 .../{img,powervr.yaml => img,powervr-rogue.yaml}   |   4 +-
 .../devicetree/bindings/gpu/img,powervr-sgx.yaml   | 138 +++++++++++++++++++++
 MAINTAINERS                                        |   3 +-
 arch/arm/boot/dts/ti/omap/am33xx.dtsi              |   9 +-
 arch/arm/boot/dts/ti/omap/am3517.dtsi              |  11 +-
 arch/arm/boot/dts/ti/omap/am4372.dtsi              |   6 +
 arch/arm/boot/dts/ti/omap/dra7.dtsi                |   9 +-
 arch/arm/boot/dts/ti/omap/omap34xx.dtsi            |  11 +-
 arch/arm/boot/dts/ti/omap/omap36xx.dtsi            |   9 +-
 arch/arm/boot/dts/ti/omap/omap4.dtsi               |   9 +-
 arch/arm/boot/dts/ti/omap/omap5.dtsi               |   9 +-
 arch/arm64/boot/dts/ti/k3-am65-main.dtsi           |   7 ++
 12 files changed, 195 insertions(+), 30 deletions(-)
 rename Documentation/devicetree/bindings/gpu/{img,powervr.yaml => img,powervr-rogue.yaml} (91%)
 create mode 100644 Documentation/devicetree/bindings/gpu/img,powervr-sgx.yaml

WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: soc@kernel.org
Cc: arm@kernel.org, linux-omap@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	"Tony Lindgren" <tony@atomide.com>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
	"Rob Herring" <robh@kernel.org>, "Nishanth Menon" <nm@ti.com>,
	"Vignesh Raghavendra" <vigneshr@ti.com>,
	"Andrew Davis" <afd@ti.com>
Subject: [GIT PULL] Add PowerVR Series5 SGX GPUs for the TI SoCs
Date: Mon, 26 Feb 2024 12:36:12 +0200	[thread overview]
Message-ID: <pull-1708943489-872615@atomide.com> (raw)

From: "Tony Lindgren" <tony@atomide.com>

The following changes since commit 6613476e225e090cc9aad49be7fa504e290dd33d:

  Linux 6.8-rc1 (2024-01-21 14:11:32 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/sgx-for-v6.9-signed

for you to fetch changes up to 21cfb2ba471bde8fefc327f4c8e2af9499f5173d:

  arm64: dts: ti: k3-am654-main: Add device tree entry for SGX GPU (2024-01-26 09:43:23 +0200)

----------------------------------------------------------------
Add PowerVR Series5 SGX GPUs for the TI SoCs

With the Imagination Rogue GPU binding added, let's also add the devicetree
binding for earlier SGX GPUs. Let's also patch the TI SoCs for the related
SGX GPU nodes.

Based on the mailing list discussions, the conclusion was that we need two
separate device tree bindings, one for Rogue and upcoming GPUS, and one for
the older SGX GPUs.

For merging the changes, I applied the binding changes together with the
TI SoC related changes into a branch leaving out the sun6i and mips changes
as suggested by Rob.

These changes are mostly 32-bit SoCs, but also contains one arm64 change.
It does not cause any merge conflicts.

----------------------------------------------------------------
Andrew Davis (9):
      dt-bindings: gpu: Rename img,powervr to img,powervr-rogue
      dt-bindings: gpu: Add PowerVR Series5 SGX GPUs
      ARM: dts: omap3: Add device tree entry for SGX GPU
      ARM: dts: omap4: Add device tree entry for SGX GPU
      ARM: dts: omap5: Add device tree entry for SGX GPU
      ARM: dts: AM33xx: Add device tree entry for SGX GPU
      ARM: dts: AM437x: Add device tree entry for SGX GPU
      ARM: dts: DRA7xx: Add device tree entry for SGX GPU
      arm64: dts: ti: k3-am654-main: Add device tree entry for SGX GPU

 .../{img,powervr.yaml => img,powervr-rogue.yaml}   |   4 +-
 .../devicetree/bindings/gpu/img,powervr-sgx.yaml   | 138 +++++++++++++++++++++
 MAINTAINERS                                        |   3 +-
 arch/arm/boot/dts/ti/omap/am33xx.dtsi              |   9 +-
 arch/arm/boot/dts/ti/omap/am3517.dtsi              |  11 +-
 arch/arm/boot/dts/ti/omap/am4372.dtsi              |   6 +
 arch/arm/boot/dts/ti/omap/dra7.dtsi                |   9 +-
 arch/arm/boot/dts/ti/omap/omap34xx.dtsi            |  11 +-
 arch/arm/boot/dts/ti/omap/omap36xx.dtsi            |   9 +-
 arch/arm/boot/dts/ti/omap/omap4.dtsi               |   9 +-
 arch/arm/boot/dts/ti/omap/omap5.dtsi               |   9 +-
 arch/arm64/boot/dts/ti/k3-am65-main.dtsi           |   7 ++
 12 files changed, 195 insertions(+), 30 deletions(-)
 rename Documentation/devicetree/bindings/gpu/{img,powervr.yaml => img,powervr-rogue.yaml} (91%)
 create mode 100644 Documentation/devicetree/bindings/gpu/img,powervr-sgx.yaml

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2024-02-26 10:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-26 10:36 Tony Lindgren [this message]
2024-02-26 10:36 ` [GIT PULL] Add PowerVR Series5 SGX GPUs for the TI SoCs Tony Lindgren
2024-03-04  8:01 ` patchwork-bot+linux-soc

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=pull-1708943489-872615@atomide.com \
    --to=tony@atomide.com \
    --cc=afd@ti.com \
    --cc=arm@kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=robh@kernel.org \
    --cc=soc@kernel.org \
    --cc=vigneshr@ti.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: link
Be 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.