linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Justin Swartz <justin.swartz@risingedge.co.za>
To: Heiko Stuebner <heiko@sntech.de>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>
Cc: linux-rockchip@lists.infradead.org,
	Justin Swartz <justin.swartz@risingedge.co.za>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: [PATCH v5 0/1] Add rga to rk322x device tree
Date: Sun, 19 Apr 2020 12:51:32 +0000	[thread overview]
Message-ID: <20200419125134.29923-1-justin.swartz@risingedge.co.za> (raw)
In-Reply-To: <558b35c3-7f75-8d0d-048b-c55c06fa8a53@gmail.com>

This patchset aims to enable use of Rockchip's RGA, a 2D raster
graphic acceleration unit, on rk322x based devices.

Changes in v5:
  - Remove the patch to rockchip-rga device tree binding documentation
    as Johan Jonker has already included mention of "rockchip,rk3228-rga"
    since the conversion to YAML.

  - Remove the assignment of "disabled" to the rga "status" attribute
    in rk322x.dtsi, as Heiko Stuebner has said:
      "no status for soc internal components without any board-specifics"

  - Remove the now unnecessary patch to enable rga for the rk3229-xms6
    board.

Changes in v4:
  - Add a compatible value entry for the rk3228 to the rockchip-rga
    device tree binding documentation.

Changes in v3:
  - Relocate rga node to the correct position in rk322x.dtsi, as
    indicated by Johan Jonker.

Changes in v2:
  - Remove unnecessary "rockchip,rk3228-rga" device tree compatibility
    string patch, as advised by Ezequiel Garcia.

  - Use both "rockchip,rk3228-rga" and "rockchip,rk3288-rga" in the
    rga node's compatibility property, as suggested by Heiko Stuebner.

Justin Swartz (1):
  ARM: dts: rockchip: add rga node for rk322x

 arch/arm/boot/dts/rk322x.dtsi | 10 ++++++++++
 1 file changed, 10 insertions(+)

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

  reply	other threads:[~2020-04-19 12:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-03 22:30 [PATCH v4 0/3] Add rga to rk322x device tree Justin Swartz
2020-02-03 22:40 ` [PATCH v4 1/3] [media] dt-bindings: Add binding for rk3228 rga Justin Swartz
2020-02-06 19:06   ` Rob Herring
2020-03-01  0:29   ` Heiko Stuebner
2020-02-03 22:40 ` [PATCH v4 2/3] ARM: dts: rockchip: add rga node for rk322x Justin Swartz
2020-04-18  9:15   ` Johan Jonker
2020-04-18  9:49     ` Heiko Stuebner
2020-04-18  9:56       ` Justin Swartz
2020-04-18 10:53         ` Heiko Stuebner
2020-04-18 12:14           ` Johan Jonker
2020-04-19 12:51             ` Justin Swartz [this message]
2020-05-18 22:52               ` [PATCH v5 0/1] Add rga to rk322x device tree Heiko Stuebner
2020-04-19 12:51             ` [PATCH v5 1/1] ARM: dts: rockchip: add rga node for rk322x Justin Swartz
2020-02-03 22:40 ` [PATCH v4 3/3] ARM: dts: rockchip: enable rga for rk3229-xms6 Justin Swartz

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=20200419125134.29923-1-justin.swartz@risingedge.co.za \
    --to=justin.swartz@risingedge.co.za \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).