On Mon, 16 Oct 2023 at 06:24, Viresh Kumar <viresh.kumar@xxxxxxxxxx> wrote: > > On 11-10-23, 15:59, Dmitry Baryshkov wrote: > > On Wed, 11 Oct 2023 at 15:52, Rob Herring <robh+dt@xxxxxxxxxx> wrote: > > > > > > On Wed, Oct 11, 2023 at 6:27 AM Dmitry Baryshkov > > > <dmitry.baryshkov@xxxxxxxxxx> wrote: > > > > > > > > The qcom-cpufreq-nvmem module uses of_find_next_cache_node() function, > > > > so export it to be available to the modules. > > > > > > You really should be using the cacheinfo API which has already parsed > > > the cache nodes. > > > > > > Also, why do you need a platform_device? I don't see a driver. > > > cacheinfo already creates a struct device, so kind of weird to have 2 > > > devices. > > > > The driver is pending as a part of the series at [1]. We need to scale > > the L2 supplies and clock frequency following the core frequency > > changes. > > Guys, can we please resolve this soon ? I had to revert the patches > for the time being to avoid these failures. Rob pointed out that I should rework my code to use the cacheinfo device for the L2 cache. This means that L2 device population should be dropped from cpufreq. I'll post newer series as soon as I finish the implementation. -- With best wishes Dmitry
