From: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
To: linux-clk-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: mturquette-rdvid1DuHRBWk0Htik3J/w@public.gmane.org,
sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org,
linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
mark.rutland-5wv7dgnIgG8@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
yang.zheng-TNX95d0MmH7DzftRWevZcw@public.gmane.org,
zhangqing-TNX95d0MmH7DzftRWevZcw@public.gmane.org,
Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
Subject: [PATCH 0/7] clk: rockchip: rk3328 fixes in preparation of graphics support
Date: Mon, 22 Jan 2018 15:15:23 +0100 [thread overview]
Message-ID: <20180122141530.12398-1-heiko@sntech.de> (raw)
Fix some clock issues on rk3328 to make way for the upcoming graphics
support on rk3328.
Heiko Stuebner (6):
clk: rockchip: fix hclk_vio_niu on rk3328
clk: rockchip: remove HCLK_VIO from rk3328 dt header
clk: rockchip: export sclk_hdmi_sfc on rk3328
clk: rockchip: protect all remaining rk3328 interconnect clocks
clk: rockchip: remove ignore_unused flag from rk3328 vio_h2p clocks
clk: rockchip: document hdmi_phy external input for rk3328
Zheng Yang (1):
clk: rockchip: add flags for rk3328 dclk_lcdc
.../bindings/clock/rockchip,rk3328-cru.txt | 1 +
drivers/clk/rockchip/clk-rk3328.c | 67 ++++++++++++++--------
include/dt-bindings/clock/rk3328-cru.h | 1 -
3 files changed, 44 insertions(+), 25 deletions(-)
--
2.14.2
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2018-01-22 14:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 14:15 Heiko Stuebner [this message]
2018-01-22 14:15 ` [PATCH 1/7] clk: rockchip: fix hclk_vio_niu on rk3328 Heiko Stuebner
2018-01-22 14:15 ` [PATCH 4/7] clk: rockchip: protect all remaining rk3328 interconnect clocks Heiko Stuebner
[not found] ` <20180122141530.12398-1-heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
2018-01-22 14:15 ` [PATCH 2/7] clk: rockchip: remove HCLK_VIO from rk3328 dt header Heiko Stuebner
2018-01-22 14:15 ` [PATCH 3/7] clk: rockchip: export sclk_hdmi_sfc on rk3328 Heiko Stuebner
2018-01-22 14:15 ` [PATCH 5/7] clk: rockchip: remove ignore_unused flag from rk3328 vio_h2p clocks Heiko Stuebner
2018-01-22 14:15 ` [PATCH 7/7] clk: rockchip: document hdmi_phy external input for rk3328 Heiko Stuebner
[not found] ` <20180122141530.12398-8-heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
2018-01-29 23:12 ` Rob Herring
2018-02-12 14:02 ` [PATCH 0/7] clk: rockchip: rk3328 fixes in preparation of graphics support Heiko Stuebner
2018-01-22 14:15 ` [PATCH 6/7] clk: rockchip: add flags for rk3328 dclk_lcdc Heiko Stuebner
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=20180122141530.12398-1-heiko@sntech.de \
--to=heiko-4mtyjxux2i+zqb+pc5nmwq@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-clk-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=mturquette-rdvid1DuHRBWk0Htik3J/w@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=yang.zheng-TNX95d0MmH7DzftRWevZcw@public.gmane.org \
--cc=zhangqing-TNX95d0MmH7DzftRWevZcw@public.gmane.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).