From: "Heiko Stübner" <heiko@sntech.de>
To: Xing Zheng <zhengxing@rock-chips.com>
Cc: linux-rockchip@lists.infradead.org, huangtao@rock-chips.com,
jay.xu@rock-chips.com, elaine.zhang@rock-chips.com,
dianders@chromium.org,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/4] clk: rockchip: fix big.LITTLE cores alternate reparent failed
Date: Sun, 27 Mar 2016 23:26:52 +0200 [thread overview]
Message-ID: <1608479.lxyeMomFsd@diego> (raw)
In-Reply-To: <1458974276-10325-2-git-send-email-zhengxing@rock-chips.com>
Am Samstag, 26. M=E4rz 2016, 14:37:53 schrieb Xing Zheng:
> On the RK3399, the order of the core's parents are LPLL/BPLL/DPLL/GPL=
L,
> there is incorrect to select bit_0 and bit_1 as the main and alternat=
e
> parents for LPLL/BPLL. They should be configurable.
>=20
> Signed-off-by: Xing Zheng <zhengxing@rock-chips.com>
I've folded this fix into the original patch [0]
Thanks
Heiko
[0] https://git.kernel.org/cgit/linux/kernel/git/mmind/linux-rockchip.g=
it/commit/?h=3Dv4.7-clk/next&id=3D268aebaa2410152bf91ea1ede6b284ff81388=
22d
WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <heiko@sntech.de>
To: Xing Zheng <zhengxing@rock-chips.com>
Cc: linux-rockchip@lists.infradead.org, huangtao@rock-chips.com,
jay.xu@rock-chips.com, elaine.zhang@rock-chips.com,
dianders@chromium.org,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/4] clk: rockchip: fix big.LITTLE cores alternate reparent failed
Date: Sun, 27 Mar 2016 23:26:52 +0200 [thread overview]
Message-ID: <1608479.lxyeMomFsd@diego> (raw)
In-Reply-To: <1458974276-10325-2-git-send-email-zhengxing@rock-chips.com>
Am Samstag, 26. März 2016, 14:37:53 schrieb Xing Zheng:
> On the RK3399, the order of the core's parents are LPLL/BPLL/DPLL/GPLL,
> there is incorrect to select bit_0 and bit_1 as the main and alternate
> parents for LPLL/BPLL. They should be configurable.
>
> Signed-off-by: Xing Zheng <zhengxing@rock-chips.com>
I've folded this fix into the original patch [0]
Thanks
Heiko
[0] https://git.kernel.org/cgit/linux/kernel/git/mmind/linux-rockchip.git/commit/?h=v4.7-clk/next&id=268aebaa2410152bf91ea1ede6b284ff8138822d
WARNING: multiple messages have this Message-ID (diff)
From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 1/4] clk: rockchip: fix big.LITTLE cores alternate reparent failed
Date: Sun, 27 Mar 2016 23:26:52 +0200 [thread overview]
Message-ID: <1608479.lxyeMomFsd@diego> (raw)
In-Reply-To: <1458974276-10325-2-git-send-email-zhengxing@rock-chips.com>
Am Samstag, 26. M?rz 2016, 14:37:53 schrieb Xing Zheng:
> On the RK3399, the order of the core's parents are LPLL/BPLL/DPLL/GPLL,
> there is incorrect to select bit_0 and bit_1 as the main and alternate
> parents for LPLL/BPLL. They should be configurable.
>
> Signed-off-by: Xing Zheng <zhengxing@rock-chips.com>
I've folded this fix into the original patch [0]
Thanks
Heiko
[0] https://git.kernel.org/cgit/linux/kernel/git/mmind/linux-rockchip.git/commit/?h=v4.7-clk/next&id=268aebaa2410152bf91ea1ede6b284ff8138822d
next prev parent reply other threads:[~2016-03-27 21:26 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-26 6:37 [PATCH v5 0/4] Add more clock compatible features and support the RK3399 clock Xing Zheng
2016-03-26 6:37 ` Xing Zheng
2016-03-26 6:37 ` [PATCH v5 1/4] clk: rockchip: fix big.LITTLE cores alternate reparent failed Xing Zheng
2016-03-26 6:37 ` Xing Zheng
2016-03-26 8:26 ` kbuild test robot
2016-03-26 8:26 ` kbuild test robot
2016-03-26 8:26 ` kbuild test robot
2016-03-27 21:26 ` Heiko Stübner [this message]
2016-03-27 21:26 ` Heiko Stübner
2016-03-27 21:26 ` Heiko Stübner
[not found] ` <1458974276-10325-1-git-send-email-zhengxing-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-03-26 6:37 ` [PATCH v5 2/4] dt-bindings: add bindings for rk3399 clock controller Xing Zheng
2016-03-26 6:37 ` Xing Zheng
2016-03-26 6:37 ` Xing Zheng
[not found] ` <1458974276-10325-3-git-send-email-zhengxing-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-03-27 23:52 ` Heiko Stübner
2016-03-27 23:52 ` Heiko Stübner
2016-03-27 23:52 ` Heiko Stübner
2016-03-28 0:07 ` Heiko Stuebner
2016-03-28 0:07 ` Heiko Stuebner
2016-03-28 3:24 ` Xing Zheng
2016-03-28 3:24 ` Xing Zheng
2016-03-28 3:24 ` Xing Zheng
2016-03-28 2:51 ` Xing Zheng
2016-03-28 2:51 ` Xing Zheng
2016-03-26 6:37 ` [PATCH v5 3/4] clk: rockchip: add dt-binding header for rk3399 Xing Zheng
2016-03-26 6:37 ` Xing Zheng
2016-03-26 6:37 ` [PATCH v5 4/4] clk: rockchip: add clock controller for the RK3399 Xing Zheng
2016-03-26 6:37 ` Xing Zheng
2016-03-26 8:41 ` kbuild test robot
2016-03-26 8:41 ` kbuild test robot
2016-03-26 8:41 ` kbuild test robot
2016-03-28 0:13 ` Heiko Stuebner
2016-03-28 0:13 ` Heiko Stuebner
2016-03-28 0:13 ` Heiko Stuebner
2016-03-28 6:11 ` Xing Zheng
2016-03-28 6:11 ` Xing Zheng
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=1608479.lxyeMomFsd@diego \
--to=heiko@sntech.de \
--cc=dianders@chromium.org \
--cc=elaine.zhang@rock-chips.com \
--cc=huangtao@rock-chips.com \
--cc=jay.xu@rock-chips.com \
--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=sboyd@codeaurora.org \
--cc=zhengxing@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.