From: Hans Verkuil <hverkuil@xs4all.nl>
To: Eddie James <eajames@linux.ibm.com>, linux-media@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-aspeed@lists.ozlabs.org,
joel@jms.id.au, andrew@aj.id.au, mchehab@kernel.org,
linux-clk@vger.kernel.org, sboyd@kernel.org,
mturquette@baylibre.com, devicetree@vger.kernel.org,
mark.rutland@arm.com, robh+dt@kernel.org
Subject: Re: [PATCH 0/5] Aspeed: Enable video engine
Date: Wed, 24 Apr 2019 12:50:06 +0200 [thread overview]
Message-ID: <b524e352-2e9d-6360-5517-18eee2e02c2c@xs4all.nl> (raw)
In-Reply-To: <1554229504-5661-1-git-send-email-eajames@linux.ibm.com>
Hi Eddie,
On 4/2/19 8:24 PM, Eddie James wrote:
> 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.
I assume you'll post a v3 since there were some comments?
If you want to get it in for 5.2, then be aware that you should post it tomorrow
at the latest.
Regards,
Hans
>
> 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(-)
>
next prev parent reply other threads:[~2019-04-24 10:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 18:24 [PATCH 0/5] Aspeed: Enable video engine Eddie James
2019-04-02 18:25 ` [PATCH 1/5] media: platform: Aspeed: Remove use of reset line Eddie James
2019-04-11 2:49 ` Joel Stanley
2019-04-02 18:25 ` [PATCH 2/5] media: platform: Aspeed: Make reserved memory optional Eddie James
2019-04-03 6:01 ` Andrew Jeffery
2019-04-03 14:35 ` Eddie James
2019-04-04 2:16 ` Andrew Jeffery
2019-04-02 18:25 ` [PATCH 3/5] media: dt-bindings: aspeed-video: Add missing memory-region property Eddie James
2019-04-02 21:05 ` Jae Hyun Yoo
2019-04-06 6:06 ` Rob Herring
2019-04-02 18:25 ` [PATCH 4/5] clk: Aspeed: Setup video engine clocking Eddie James
2019-04-11 2:50 ` Joel Stanley
2019-04-18 21:56 ` Stephen Boyd
2019-04-02 18:25 ` [PATCH 5/5] ARM: dts: aspeed-g5: Add video engine Eddie James
2019-04-24 10:50 ` Hans Verkuil [this message]
2019-04-24 15:00 ` [PATCH 0/5] Aspeed: Enable " Eddie James
-- strict thread matches above, loose matches on Subject: below --
2019-04-02 18:24 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=b524e352-2e9d-6360-5517-18eee2e02c2c@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=andrew@aj.id.au \
--cc=devicetree@vger.kernel.org \
--cc=eajames@linux.ibm.com \
--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=mchehab@kernel.org \
--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 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).