Hello Trent, On Fri, Nov 30, 2018 at 05:21:40PM +0000, Trent Piepho wrote: > On Fri, 2018-11-30 at 07:47 +0100, Uwe Kleine-König wrote: > > The driver data's member variable just caches the transfer's speed_hz > > member. All users of the former now have access directly to the latter. > > So fix them to use the uncached value and remove the cache. > > What should have been done with this is to compare the next transfer's > speed_hz to this cached value, and not preprogram the clock if it has > not changed. Since usually it doesn't change between transfers. Hmm, yes, this could be done, but I'm not sure the additional effort brings a performance advantage. If you have the energy to do test that, feel free to implement it, preferably on top of my cleanup commit. Best regards Uwe -- Pengutronix e.K. | Uwe Kleine-König | Industrial Linux Solutions | http://www.pengutronix.de/ |