From: Randy Li <ayaka@soulik.info>
To: linux-rockchip@lists.infradead.org
Cc: Randy Li <ayaka@soulik.info>,
mturquette@baylibre.com, sboyd@kernel.org, heiko@sntech.de,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, ulf.hansson@linaro.org,
zhangqing@rock-chips.com, geert+renesas@glider.be
Subject: [PATCH 0/3] The basic patches for rockchip video codec
Date: Sun, 6 Jan 2019 01:48:34 +0800 [thread overview]
Message-ID: <20190105174837.19378-1-ayaka@soulik.info> (raw)
I will post a driver for video codec using the vendor userspace
interface. It is not used for merging but checking the work status of
the other devices and pre-patches need to be merged.
Without the following modification, video codec can't work properly.
I check the status of the upstream kernel for rockchip, network, eMMC,
USB and VOP work much worse and slow than the vendor kernel. I think the
video codec driver would be a good example to verify the other drivers.
Randy Li (3):
clk: rockchip: add video clk parents for rk3399
arm64: dts: rockchip: add power domain to iommu rk3399
soc: rockchip: power-domain: export idle request
arch/arm64/boot/dts/rockchip/rk3399.dtsi | 2 ++
drivers/clk/rockchip/clk-rk3399.c | 5 +++--
drivers/soc/rockchip/pm_domains.c | 23 +++++++++++++++++++++++
include/dt-bindings/clock/rk3399-cru.h | 2 ++
include/soc/rockchip/pm_domains.h | 18 ++++++++++++++++++
5 files changed, 48 insertions(+), 2 deletions(-)
create mode 100644 include/soc/rockchip/pm_domains.h
--
2.20.1
next reply other threads:[~2019-01-05 17:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-05 17:48 Randy Li [this message]
2019-01-05 17:48 ` [PATCH 1/3] clk: rockchip: add video clk parents for rk3399 Randy Li
2019-01-05 17:48 ` [PATCH 2/3] arm64: dts: rockchip: add power domain to iommu rk3399 Randy Li
2019-01-05 17:48 ` [PATCH 3/3] soc: rockchip: power-domain: export idle request Randy Li
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=20190105174837.19378-1-ayaka@soulik.info \
--to=ayaka@soulik.info \
--cc=geert+renesas@glider.be \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=zhangqing@rock-chips.com \
/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).