From: Gregory CLEMENT <gregory.clement@bootlin.com> To: Viresh Kumar <viresh.kumar@linaro.org> Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>, linux-pm@vger.kernel.org, "Christian Neubert" <christian.neubert.86@gmail.com>, "Ilias Apalodimas" <ilias.apalodimas@linaro.org>, "Vincent Guittot" <vincent.guittot@linaro.org>, "Jason Cooper" <jason@lakedaemon.net>, "Andrew Lunn" <andrew@lunn.ch>, "Sebastian Hesselbarth" <sebastian.hesselbarth@gmail.com>, "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>, linux-arm-kernel@lists.infradead.org, "Antoine Tenart" <antoine.tenart@bootlin.com>, "Miquèl Raynal" <miquel.raynal@bootlin.com>, "Maxime Chevallier" <maxime.chevallier@bootlin.com>, stable@vger.kernel.org Subject: Re: [PATCH 1/2] cpufreq: armada-37xx: fix clock parenting Date: Wed, 13 Mar 2019 17:39:36 +0100 [thread overview] Message-ID: <87pnquvid3.fsf@FE-laptop> (raw) In-Reply-To: <20190311053130.qrobxd2wn75nrgbf@vireshk-i7> Hi Viresh, On lun., mars 11 2019, Viresh Kumar <viresh.kumar@linaro.org> wrote: > On 08-03-19, 17:47, Gregory CLEMENT wrote: [...] >> parent = clk_get_parent(clk); >> + >> + /* >> + * Unset parent clock to force the clock framework setting again >> + * the clock parent >> + */ >> + clk_set_parent(clk, NULL); >> + >> + /* >> + * For the Armada 37xx CPU clocks, setting the parent will >> + * actually configure the parent when DVFS is enabled. At >> + * hardware level it will be a different register from the one >> + * read when doing clk_get_parent that will be set with >> + * clk_set_parent. >> + */ >> clk_set_parent(clk, parent); >> } > > Maybe this should be done right from the clock driver instead? As cpufreq may or > maynot be enabled by default (Surely most of the people will always enable it, > but I am just trying to find the right place for doing this). The way we are > setting the clock parent isn't that great, and looks a bit hacky just because of > the way clock framework is. Maybe doing it directly, without getting clock > framework in between, from the clock driver may look sane ? I've just sent a patch following your suggestion to the clock mailing but keeping you in CC too. Gregory > > -- > viresh -- Gregory Clement, Bootlin Embedded Linux and Kernel engineering http://bootlin.com
WARNING: multiple messages have this Message-ID (diff)
From: Gregory CLEMENT <gregory.clement@bootlin.com> To: Viresh Kumar <viresh.kumar@linaro.org> Cc: "Andrew Lunn" <andrew@lunn.ch>, "Vincent Guittot" <vincent.guittot@linaro.org>, "Jason Cooper" <jason@lakedaemon.net>, "Christian Neubert" <christian.neubert.86@gmail.com>, "Antoine Tenart" <antoine.tenart@bootlin.com>, linux-pm@vger.kernel.org, "Ilias Apalodimas" <ilias.apalodimas@linaro.org>, "Rafael J. Wysocki" <rjw@rjwysocki.net>, stable@vger.kernel.org, "Maxime Chevallier" <maxime.chevallier@bootlin.com>, "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>, "Miquèl Raynal" <miquel.raynal@bootlin.com>, linux-arm-kernel@lists.infradead.org, "Sebastian Hesselbarth" <sebastian.hesselbarth@gmail.com> Subject: Re: [PATCH 1/2] cpufreq: armada-37xx: fix clock parenting Date: Wed, 13 Mar 2019 17:39:36 +0100 [thread overview] Message-ID: <87pnquvid3.fsf@FE-laptop> (raw) In-Reply-To: <20190311053130.qrobxd2wn75nrgbf@vireshk-i7> Hi Viresh, On lun., mars 11 2019, Viresh Kumar <viresh.kumar@linaro.org> wrote: > On 08-03-19, 17:47, Gregory CLEMENT wrote: [...] >> parent = clk_get_parent(clk); >> + >> + /* >> + * Unset parent clock to force the clock framework setting again >> + * the clock parent >> + */ >> + clk_set_parent(clk, NULL); >> + >> + /* >> + * For the Armada 37xx CPU clocks, setting the parent will >> + * actually configure the parent when DVFS is enabled. At >> + * hardware level it will be a different register from the one >> + * read when doing clk_get_parent that will be set with >> + * clk_set_parent. >> + */ >> clk_set_parent(clk, parent); >> } > > Maybe this should be done right from the clock driver instead? As cpufreq may or > maynot be enabled by default (Surely most of the people will always enable it, > but I am just trying to find the right place for doing this). The way we are > setting the clock parent isn't that great, and looks a bit hacky just because of > the way clock framework is. Maybe doing it directly, without getting clock > framework in between, from the clock driver may look sane ? I've just sent a patch following your suggestion to the clock mailing but keeping you in CC too. Gregory > > -- > viresh -- Gregory Clement, Bootlin Embedded Linux and Kernel engineering http://bootlin.com _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-03-13 16:39 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-03-08 16:47 [PATCH 0/2] Fix various issue on CPU freq for Armada 37xx Gregory CLEMENT 2019-03-08 16:47 ` Gregory CLEMENT 2019-03-08 16:47 ` [PATCH 1/2] cpufreq: armada-37xx: fix clock parenting Gregory CLEMENT 2019-03-08 16:47 ` Gregory CLEMENT 2019-03-11 5:31 ` Viresh Kumar 2019-03-11 5:31 ` Viresh Kumar 2019-03-13 16:39 ` Gregory CLEMENT [this message] 2019-03-13 16:39 ` Gregory CLEMENT 2019-03-14 12:13 ` Ilias Apalodimas 2019-03-14 12:13 ` Ilias Apalodimas 2019-03-08 16:47 ` [PATCH 2/2] cpufreq: armada-37xx: fix frequency calculation for opp Gregory CLEMENT 2019-03-08 16:47 ` Gregory CLEMENT 2019-03-11 5:33 ` Viresh Kumar 2019-03-11 5:33 ` Viresh Kumar 2019-04-29 9:53 ` Viresh Kumar 2019-04-29 9:53 ` Viresh Kumar
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=87pnquvid3.fsf@FE-laptop \ --to=gregory.clement@bootlin.com \ --cc=andrew@lunn.ch \ --cc=antoine.tenart@bootlin.com \ --cc=christian.neubert.86@gmail.com \ --cc=ilias.apalodimas@linaro.org \ --cc=jason@lakedaemon.net \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-pm@vger.kernel.org \ --cc=maxime.chevallier@bootlin.com \ --cc=miquel.raynal@bootlin.com \ --cc=rjw@rjwysocki.net \ --cc=sebastian.hesselbarth@gmail.com \ --cc=stable@vger.kernel.org \ --cc=thomas.petazzoni@bootlin.com \ --cc=vincent.guittot@linaro.org \ --cc=viresh.kumar@linaro.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: linkBe 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.