From: Heiko Stuebner <heiko@sntech.de>
To: Andy Yan <andy.yan@rock-chips.com>
Cc: robh+dt@kernel.org, shawn.lin@rock-chips.com,
zhangqing@rock-chips.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, mturquette@baylibre.com,
sboyd@codeaurora.org, linux-rockchip@lists.infradead.org,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 06/23] clk: rockchip: support more clks for rv1108
Date: Tue, 08 Aug 2017 00:57:45 +0200 [thread overview]
Message-ID: <11738434.oWbxbgkgjP@phil> (raw)
In-Reply-To: <1501662837-12029-1-git-send-email-andy.yan@rock-chips.com>
Hi Andy,
Am Mittwoch, 2. August 2017, 16:33:57 CEST schrieb Andy Yan:
> From: Elaine Zhang <zhangqing@rock-chips.com>
>
> Added the description of the missing clock,
> make the clock tree more complete.
>
> Signed-off-by: Elaine Zhang <zhangqing@rock-chips.com>
> Signed-off-by: Andy Yan <andy.yan@rock-chips.com>
[...]
> FACTOR(0, "xin12m", "xin24m", 0, 1, 2),
>
> - COMPOSITE(0, "i2s0_src", mux_pll_src_2plls_p, 0,
> + /* PD_BUS */
> + GATE(0, "aclk_bus_src_gpll", "gpll", CLK_IGNORE_UNUSED,
> + RV1108_CLKGATE_CON(1), 0, GFLAGS),
> + GATE(0, "aclk_bus_src_apll", "apll", CLK_IGNORE_UNUSED,
> + RV1108_CLKGATE_CON(1), 1, GFLAGS),
> + GATE(0, "aclk_bus_src_dpll", "dpll", CLK_IGNORE_UNUSED,
> + RV1108_CLKGATE_CON(1), 2, GFLAGS),
> + COMPOSITE_NOGATE(ACLK_PRE, "aclk_bus_pre", mux_aclk_bus_src_p, 0,
> + RV1108_CLKSEL_CON(2), 8, 2, MFLAGS, 0, 5, DFLAGS),
> + COMPOSITE_NOMUX(HCLK_BUS, "hclk_bus_pre", "aclk_bus_pre", 0,
> + RV1108_CLKSEL_CON(3), 0, 5, DFLAGS,
> + RV1108_CLKGATE_CON(1), 4, GFLAGS),
you're adding a (new / second) hclk_bus_pre here, but only drop the
old in patch 7. Please structure patch-contents in a way that each patch
is self-contained and works on its own ... aka the clock tree should not
get worse if only patch 6 is applied (like in a random git bisect), but
here the state is bad between these 2 patches.
hclk_bus_pre also is only _one_ example and there are probably more of
those hiding in these clock patches. So please fix these issues.
Thanks
Heiko
next prev parent reply other threads:[~2017-08-07 22:57 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 8:25 [PATCH v2 00/23] Support more devices on rockchip rv1108 Andy Yan
2017-08-02 8:29 ` [PATCH v2 02/23] clk: rockchip: rename the clk id for HCLK_I2S1_2CH Andy Yan
2017-08-08 15:37 ` Heiko Stuebner
2017-08-02 8:30 ` [PATCH v2 03/23] clk: rockchip: fix up the indentation stuff for RV1108 SoC Andy Yan
2017-08-08 15:38 ` Heiko Stuebner
2017-08-02 8:32 ` [PATCH v2 04/23] clk: rockchip: support more rates for cpuclk Andy Yan
[not found] ` <1501662743-11920-1-git-send-email-andy.yan-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-08-07 22:52 ` Heiko Stuebner
2017-08-02 8:33 ` [PATCH v2 06/23] clk: rockchip: support more clks for rv1108 Andy Yan
2017-08-07 22:57 ` Heiko Stuebner [this message]
2017-08-02 8:34 ` [PATCH v2 07/23] clk: rockchip: fix up some clks describe error for rv1108 SoC Andy Yan
2017-08-02 8:35 ` [PATCH v2 08/23] clk: rockchip: rename some of clks " Andy Yan
2017-08-02 8:36 ` [PATCH v2 09/23] clk: rockchip: add some critical clocks " Andy Yan
2017-08-02 8:41 ` [PATCH v2 11/23] dt-bindings: i2c: rk3x: add support for rv1108 Andy Yan
2017-08-10 16:15 ` Rob Herring
2017-08-02 8:44 ` [PATCH v2 13/23] ARM: dts: rockchip: add i2c dt node " Andy Yan
2017-08-02 8:46 ` [PATCH v2 14/23] spi: rockchip: add compatible string for rv1108 spi Andy Yan
2017-08-10 16:15 ` Rob Herring
2017-08-14 16:45 ` Applied "spi: rockchip: add compatible string for rv1108 spi" to the spi tree Mark Brown
2017-08-02 8:46 ` [PATCH v2 15/23] ARM: dts: rockchip: add spi dt node for rv1108 Andy Yan
[not found] ` <1501662303-11687-1-git-send-email-andy.yan-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-08-02 8:28 ` [PATCH v2 01/23] clk: rockchip: add more clk ids " Andy Yan
2017-08-08 15:37 ` Heiko Stuebner
2017-08-02 8:33 ` [PATCH v2 05/23] clk: rockchip: fix up the pll clks error for rv1108 SoC Andy Yan
[not found] ` <1501662784-11973-1-git-send-email-andy.yan-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-08-07 22:52 ` Heiko Stuebner
2017-08-02 8:47 ` [PATCH v2 16/23] dt-bindings: pwm: add description for rv1108 pwm Andy Yan
[not found] ` <1501663675-12591-1-git-send-email-andy.yan-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-08-10 16:17 ` Rob Herring
2017-08-02 8:48 ` [PATCH v2 17/23] ARM: dts: rockchip: add pwm dt node for rv1108 Andy Yan
2017-08-02 8:49 ` [PATCH v2 18/23] ARM: dts: rockchip: add watchdog " Andy Yan
2017-08-02 8:54 ` [PATCH v2 20/23] ARM: dts: rockchip: add saradc support " Andy Yan
2017-08-02 8:56 ` [PATCH v2 21/23] ARM: dts: rockchip: add pwm backlight for rv1108 evb Andy Yan
2017-08-02 8:52 ` [PATCH v2 19/23] dt-bindings: adc: add description for rv1108 saradc Andy Yan
2017-08-10 16:18 ` Rob Herring
2017-08-12 11:13 ` Jonathan Cameron
2017-08-02 8:59 ` [PATCH v2 22/23] ARM: dts: rockchip: add pmic rk805 dt node for rv1108 evb Andy Yan
2017-08-02 9:00 ` [PATCH v2 23/23] ARM: dts: rockchip: add accelerometer bma250e " Andy Yan
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=11738434.oWbxbgkgjP@phil \
--to=heiko@sntech.de \
--cc=andy.yan@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=shawn.lin@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;
as well as URLs for NNTP newsgroup(s).