On 09/04, Stephen Boyd wrote: > In the near future we're going to move the prepare lock to be a > per-clock ww_mutex. __clk_lookup() is called very deep in the > set-rate path and we would like to avoid having to take all the > locks in the clock tree to search for a clock (basically > defeating the purpose of introducing per-clock locks). Introduce > a new list that contains all clocks registered in the system and > walk this list until the clock is found. > > Signed-off-by: Stephen Boyd <sboyd@xxxxxxxxxxxxxx> > --- Actually this won't work. We can't grab the list lock while the prepare lock is held. So we need to do the debugfs stuff with a different lock and do it outside of the prepare lock. -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
