Quoting Stephen Boyd (2019-04-12 11:31:43) > We don't need to hold the 'clocks_mutex' here when we're creating a clk > pointer from a clk_lookup structure. Instead, we just need to make sure > that the lookup doesn't go away while we dereference the lookup pointer > to extract the clk_hw pointer out of it. Let's move things around > slightly so that we have a new function to get the clk_hw out of the > lookup with the right locking and then chain the two together for what > used to be __clk_get_sys(). > > Cc: Miquel Raynal <[email protected]> > Cc: Jerome Brunet <[email protected]> > Cc: Russell King <[email protected]> > Cc: Michael Turquette <[email protected]> > Cc: Jeffrey Hugo <[email protected]> > Cc: Chen-Yu Tsai <[email protected]> > Signed-off-by: Stephen Boyd <[email protected]> > ---
Applied to clk-next
