提交 54823af9 编写于 作者: G Georgi Djakov 提交者: Stephen Boyd

clk: qcom: Always add factor clock for xo clocks

Currently the RPM/RPM-SMD clock drivers do not register the xo clocks,
so we should always add factor clock. When we later add xo clocks support
into the drivers, we should update this function to skip registration.
By doing so we avoid any DT dependencies.
Signed-off-by: NGeorgi Djakov <georgi.djakov@linaro.org>
Signed-off-by: NStephen Boyd <sboyd@codeaurora.org>
上级 1001354c
...@@ -153,15 +153,12 @@ int qcom_cc_register_board_clk(struct device *dev, const char *path, ...@@ -153,15 +153,12 @@ int qcom_cc_register_board_clk(struct device *dev, const char *path,
const char *name, unsigned long rate) const char *name, unsigned long rate)
{ {
bool add_factor = true; bool add_factor = true;
struct device_node *node;
/* The RPM clock driver will add the factor clock if present */ /*
if (IS_ENABLED(CONFIG_QCOM_RPMCC)) { * TODO: The RPM clock driver currently does not support the xo clock.
node = of_find_compatible_node(NULL, NULL, "qcom,rpmcc"); * When xo is added to the RPM clock driver, we should change this
if (of_device_is_available(node)) * function to skip registration of xo factor clocks.
add_factor = false; */
of_node_put(node);
}
return _qcom_cc_register_board_clk(dev, path, name, rate, add_factor); return _qcom_cc_register_board_clk(dev, path, name, rate, add_factor);
} }
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册