Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1159804 > unrolled thread
| Started by | Stephen Boyd <sboyd@codeaurora.org> |
|---|---|
| First post | 2015-06-06 03:20 +0200 |
| Last post | 2015-06-06 03:20 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH v2 1/5] clk: qcom: Add support for read-only rcg2 ops Stephen Boyd <sboyd@codeaurora.org> - 2015-06-06 03:20 +0200
| From | Stephen Boyd <sboyd@codeaurora.org> |
|---|---|
| Date | 2015-06-06 03:20 +0200 |
| Subject | Re: [PATCH v2 1/5] clk: qcom: Add support for read-only rcg2 ops |
| Message-ID | <pyaWd-1km-9@gated-at.bofh.it> |
On 06/05, Georgi Djakov wrote: > Some root clock generators can be controlled by other processors. In this > case modifying them is not recommended. By using the read-only operations, > the child clocks will be able to get information about their parent - like > rate etc. > > Suggested-by: Stephen Boyd <sboyd@codeaurora.org> > Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org> Do we actually need this? I think I wrote the clk ops for the RCG to make it skip doing anything if there isn't a frequency table. So to make a read-only RCG all we need to do is remove the frequency table? Sorry if I led you down the wrong path. -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to top | Article view | linux.kernel
csiph-web