Quoting Alexandru Ardelean (2019-11-07 23:17:18) > From: Michael Hennerich <michael.hennerich@xxxxxxxxxx> > > For an external clock source, which is gated via a GPIO, the > rate change should typically be propagated to the parent clock. > > The situation where we are requiring this propagation, is when an > external clock is connected to override an internal clock (which typically > has a fixed rate). The external clock can have a different rate than the > internal one, and may also be variable, thus requiring the rate > propagation. > > This rate change wasn't propagated until now, and it's unclear about cases > where this shouldn't be propagated. Thus, it's unclear whether this is > fixing a bug, or extending the current driver behavior. Also, it's unsure > about whether this may break any existing setups; in the case that it does, > a device-tree property may be added to disable this flag. > > Signed-off-by: Michael Hennerich <michael.hennerich@xxxxxxxxxx> > Signed-off-by: Alexandru Ardelean <alexandru.ardelean@xxxxxxxxxx> > --- Applied to clk-next Next time please send as a new topic instead of a reply to the original patch. Makes it easier for me to apply the patch.
