From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 3/3] clk: rockchip: rk3288: make all niu clocks critical
Date: Sun, 22 Jan 2017 13:07:53 +0100 [thread overview]
Message-ID: <4474818.6v0yI33TyK@phil> (raw)
In-Reply-To: <CAFLEztTwyjqz0-2LriDp2WAyPR-g28RZT3VPA5vfSK5SSHTx8Q@mail.gmail.com>
Am Sonntag, 22. Januar 2017, 17:02:17 CET schrieb Jacob Chen:
> 2017-01-18 13:42 GMT+08:00 Jacob Chen <jacob-chen@iotwrt.com>:
> > NIU clocks are related to the interconnect and it's important to other
> > blocks. Since we don't have a driver to handle it, we should always
> > enable it to avoid casually close.
> >
> > Make all of them critical,so that we don't have to each clock on its own
> > once things break.
> >
> > Signed-off-by: Jacob Chen <jacob-chen@iotwrt.com>
> > ---
> >
> > drivers/clk/rockchip/clk-rk3288.c | 7 +++++++
> > 1 file changed, 7 insertions(+)
> >
> > diff --git a/drivers/clk/rockchip/clk-rk3288.c
> > b/drivers/clk/rockchip/clk-rk3288.c index 3d02aa2..c50386c 100644
> > --- a/drivers/clk/rockchip/clk-rk3288.c
> > +++ b/drivers/clk/rockchip/clk-rk3288.c
> > @@ -808,8 +808,15 @@ static struct rockchip_clk_branch
> > rk3288_clk_branches[] __initdata = {>
> > static const char *const rk3288_critical_clocks[] __initconst = {
> >
> > "aclk_cpu",
> > "aclk_peri",
> >
> > + "aclk_peri_niu",
> > + "aclk_vio0_niu",
> > + "aclk_vio1_niu",
> > + "aclk_rga_niu",
> >
> > "hclk_peri",
> >
> > + "hclk_vio_niu",
> > + "pclk_alive_niu",
> >
> > "pclk_pd_pmu",
> >
> > + "pclk_pmu_niu",
> >
> > };
> >
> > static void __iomem *rk3288_cru_base;
> >
> > --
> > 2.7.4
>
> I just got an another bug that caused by closed niu clock.
> Making niu clock always enabled is really useful, it could save me a
> lot of time.....
>
> I just wonder why we don't do that before. Would it have great impact
> on power consumption?
The niu clocks so far seemed to rely on the CLK_IGNORE_UNUSED flag. So all was
well as long as nothing changed in the clock tree above those and I guess with
more supported peripherals, some now make changes to the more common clocks
and thus disable the nui clocks by accident.
next prev parent reply other threads:[~2017-01-22 12:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 5:42 [PATCH v2 1/3] clk: rockchip: add rk3288 vip_out clock ids Jacob Chen
2017-01-18 5:42 ` [PATCH v2 2/3] clk: rockchip: use " Jacob Chen
2017-01-18 5:42 ` [PATCH v2 3/3] clk: rockchip: rk3288: make all niu clocks critical Jacob Chen
2017-01-22 9:02 ` Jacob Chen
2017-01-22 12:07 ` Heiko Stuebner [this message]
2017-01-23 0:26 ` [PATCH v2 1/3] clk: rockchip: add rk3288 vip_out clock ids 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=4474818.6v0yI33TyK@phil \
--to=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.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