From: tommy-huang <tommy_huang@aspeedtech.com>
To: <joel@jms.id.au>, <airlied@linux.ie>, <daniel@ffwll.ch>,
<robh+dt@kernel.org>, <andrew@aj.id.au>,
<linux-aspeed@lists.ozlabs.org>,
<dri-devel@lists.freedesktop.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Cc: <BMC-SW@aspeedtech.com>
Subject: [PATCH 0/4] Add Aspeed AST2600 soc display support
Date: Mon, 1 Nov 2021 19:01:03 +0800 [thread overview]
Message-ID: <20211101110107.29010-1-tommy_huang@aspeedtech.com> (raw)
The Aspeed AST2600 soc diaplay support is added in this patch.
Because some hw designed is changed in this version, add them
in this patch.
v2:
Remove some unnecessary patch.
Refine for reviwer request.
v1:
First add patch.
Joel Stanley (2):
ARM: dts: aspeed: Add GFX node to AST2600
ARM: dts: aspeed: ast2600-evb: Enable GFX device
tommy-huang (2):
drm/aspeed: Update INTR_STS handling
dt-bindings: gpu: Add ASPEED GFX bindings document
.../devicetree/bindings/gpu/aspeed-gfx.txt | 1 +
arch/arm/boot/dts/aspeed-ast2600-evb.dts | 18 +++++++++++++
arch/arm/boot/dts/aspeed-g6.dtsi | 11 ++++++++
drivers/gpu/drm/aspeed/aspeed_gfx.h | 2 ++
drivers/gpu/drm/aspeed/aspeed_gfx_drv.c | 26 ++++++++++++++++---
5 files changed, 55 insertions(+), 3 deletions(-)
--
2.17.1
next reply other threads:[~2021-11-01 11:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 11:01 tommy-huang [this message]
2021-11-01 11:01 ` [PATCH 1/4] ARM: dts: aspeed: Add GFX node to AST2600 tommy-huang
2021-11-01 11:01 ` [PATCH 2/4] ARM: dts: aspeed: ast2600-evb: Enable GFX device tommy-huang
2021-11-01 11:01 ` [PATCH 3/4] drm/aspeed: Update INTR_STS handling tommy-huang
2021-11-16 6:18 ` Joel Stanley
2021-11-16 7:18 ` Tommy Huang
2021-11-01 11:01 ` [PATCH 4/4] dt-bindings: gpu: Add ASPEED GFX bindings document tommy-huang
2021-11-01 20:01 ` Rob Herring
2021-11-02 0:20 ` Tommy Huang
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=20211101110107.29010-1-tommy_huang@aspeedtech.com \
--to=tommy_huang@aspeedtech.com \
--cc=BMC-SW@aspeedtech.com \
--cc=airlied@linux.ie \
--cc=andrew@aj.id.au \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--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).