From: Heiko Stuebner <heiko@sntech.de>
To: linux-clk@vger.kernel.org
Cc: mturquette@baylibre.com, sboyd@codeaurora.org,
linux-rockchip@lists.infradead.org, robh+dt@kernel.org,
mark.rutland@arm.com, devicetree@vger.kernel.org,
yang.zheng@rock-chips.com, zhangqing@rock-chips.com
Subject: Re: [PATCH 0/7] clk: rockchip: rk3328 fixes in preparation of graphics support
Date: Mon, 12 Feb 2018 15:02:29 +0100 [thread overview]
Message-ID: <4164196.RnrTvLKjBY@phil> (raw)
In-Reply-To: <20180122141530.12398-1-heiko@sntech.de>
Am Montag, 22. Januar 2018, 15:15:23 CET schrieb Heiko Stuebner:
> 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
applied for 4.17
prev parent reply other threads:[~2018-02-12 14:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 14:15 [PATCH 0/7] clk: rockchip: rk3328 fixes in preparation of graphics support Heiko Stuebner
2018-01-22 14:15 ` [PATCH 1/7] clk: rockchip: fix hclk_vio_niu on rk3328 Heiko Stuebner
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 4/7] clk: rockchip: protect all remaining rk3328 interconnect clocks 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 6/7] clk: rockchip: add flags for rk3328 dclk_lcdc Heiko Stuebner
2018-01-22 14:15 ` [PATCH 7/7] clk: rockchip: document hdmi_phy external input for rk3328 Heiko Stuebner
2018-01-29 23:12 ` Rob Herring
2018-02-12 14:02 ` Heiko Stuebner [this message]
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=4164196.RnrTvLKjBY@phil \
--to=heiko@sntech.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=yang.zheng@rock-chips.com \
--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