From: Eddie James <eajames@linux.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: linux-aspeed@lists.ozlabs.org, devicetree@vger.kernel.org,
linux-media@vger.kernel.org, andrew@aj.id.au, joel@jms.id.au,
robh+dt@kernel.org, mark.rutland@arm.com, mchehab@kernel.org,
hverkuil@xs4all.nl, Eddie James <eajames@linux.ibm.com>
Subject: [PATCH v2 0/4] Aspeed: Enable video engine
Date: Wed, 24 Apr 2019 10:16:56 -0500 [thread overview]
Message-ID: <1556119020-7609-1-git-send-email-eajames@linux.ibm.com> (raw)
This series enables the video engine on Aspeed BMC platforms. The use of the
video engine reset line, originally planned to be made externally available in
the clock driver, is removed from the video engine driver. A node for the video
engine is added to the AST2500 devicetree.
The series also includes a missing property for reserved memory in the
devicetree documentation, and a small change to make the video engine driver
start without reserved memory.
Changes since v1:
- Drop clock patch since it's been applied
- Add a missing semi-colon in the devicetree doc
Eddie James (4):
media: platform: Aspeed: Remove use of reset line
media: platform: Aspeed: Make reserved memory optional
media: dt-bindings: aspeed-video: Add missing memory-region property
ARM: dts: aspeed-g5: Add video engine
.../devicetree/bindings/media/aspeed-video.txt | 6 ++++
arch/arm/boot/dts/aspeed-g5.dtsi | 10 +++++++
drivers/media/platform/aspeed-video.c | 33 ++++------------------
3 files changed, 22 insertions(+), 27 deletions(-)
--
1.8.3.1
next reply other threads:[~2019-04-24 15:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 15:16 Eddie James [this message]
2019-04-24 15:16 ` [PATCH v2 1/4] media: platform: Aspeed: Remove use of reset line Eddie James
2019-04-24 15:16 ` [PATCH v2 2/4] media: platform: Aspeed: Make reserved memory optional Eddie James
2019-04-24 15:16 ` [PATCH v2 3/4] media: dt-bindings: aspeed-video: Add missing memory-region property Eddie James
2019-04-24 21:17 ` Rob Herring
2019-04-25 7:19 ` Hans Verkuil
2019-04-26 14:11 ` Eddie James
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=1556119020-7609-1-git-send-email-eajames@linux.ibm.com \
--to=eajames@linux.ibm.com \
--cc=andrew@aj.id.au \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil@xs4all.nl \
--cc=joel@jms.id.au \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@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).