From: Eddie James <eajames@linux.ibm.com>
To: linux-media@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-aspeed@lists.ozlabs.org,
joel@jms.id.au, linux-clk@vger.kernel.org, sboyd@kernel.org,
mturquette@baylibre.com, devicetree@vger.kernel.org,
mark.rutland@arm.com, robh+dt@kernel.org
Subject: [PATCH 0/5] Aspeed: Enable video engine
Date: Tue, 2 Apr 2019 18:24:33 +0000 [thread overview]
Message-ID: <1554229478-5621-1-git-send-email-eajames@linux.ibm.com> (raw)
This series enables the video engine on Aspeed BMC platforms. The video engine
clocking is added to the Aspeed clock driver. 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. Finally 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.
Eddie James (5):
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
clk: Aspeed: Setup video engine clocking
ARM: dts: aspeed-g5: Add video engine
.../devicetree/bindings/media/aspeed-video.txt | 6 ++++
arch/arm/boot/dts/aspeed-g5.dtsi | 10 ++++++
drivers/clk/clk-aspeed.c | 42 ++++++++++++++++++++--
drivers/media/platform/aspeed-video.c | 33 ++++-------------
4 files changed, 61 insertions(+), 30 deletions(-)
--
1.8.3.1
next reply other threads:[~2019-04-02 18:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 18:24 Eddie James [this message]
2019-04-02 18:24 ` [PATCH 1/5] media: platform: Aspeed: Remove use of reset line Eddie James
2019-04-11 2:48 ` Joel Stanley
2019-04-02 18:24 ` [PATCH 2/5] media: platform: Aspeed: Make reserved memory optional Eddie James
2019-04-02 18:24 [PATCH 0/5] Aspeed: Enable video engine Eddie James
2019-04-24 10:50 ` Hans Verkuil
2019-04-24 15:00 ` 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=1554229478-5621-1-git-send-email-eajames@linux.ibm.com \
--to=eajames@linux.ibm.com \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@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 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.