On 12/18/18 00:37, Stephen Boyd wrote:
Quoting Jorge Ramirez-Ortiz (2018-12-17 01:46:22)
Allow accessing the parent clock names required for the driver
operation by using the device tree node.
This permits extending the driver to other platforms without having to
modify its source code.
For backwards compatibility leave previous values as default.
Why do we need to maintain backwards compatibility? Isn't is required
that the nodes have clocks properties?
this driver -apcs clock controller- uses platform data (not DT) and
therefore it uses the DT from the parent node (mailbox).
And for the mailbox the clock property is optional.
So the APCS clock controller requires that the parent provides at least
one clock but the clock is not mandatory in the parent DT node.
For instance in the case of the msm8916, the parent only provides one
clock, just the pll.
am I required to modify that platform instead of maintaining backwards
compatibility?
