[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190723020450.z2pqwetkn2tfhacq@vireshk-i7>
Date: Tue, 23 Jul 2019 07:34:50 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Sylwester Nawrocki <s.nawrocki@...sung.com>
Cc: krzk@...nel.org, robh+dt@...nel.org, vireshk@...nel.org,
devicetree@...r.kernel.org, kgene@...nel.org,
pankaj.dubey@...sung.com, linux-samsung-soc@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-pm@...r.kernel.org, b.zolnierkie@...sung.com,
m.szyprowski@...sung.com
Subject: Re: [PATCH v2 0/9] Exynos Adaptive Supply Voltage support
On 18-07-19, 16:30, Sylwester Nawrocki wrote:
> This is second iteration of patch series adding ASV (Adaptive Supply
> Voltage) support for Exynos SoCs. The first one can be found at:
> https://lore.kernel.org/lkml/20190404171735.12815-1-s.nawrocki@samsung.com
>
> The main changes comparing to the first (RFC) version are:
> - moving ASV data tables from DT to the driver,
> - converting the chipid and the ASV drivers to use regmap,
> - converting the ASV driver to proper platform driver.
>
> I tried the opp-supported-hw bitmask approach as in the Qualcomm CPUFreq
> DT bindings but it resulted in too many OPPs and DT nodes, around 200
> per CPU cluster. So the ASV OPP tables are now in the ASV driver, as in
> downstream kernels.
Hmm. Can you explain why do you have so many OPPs? How many
frequencies do you actually support per cluster and what all varies
per frequency based on hw ? How many hw version do u have ?
I am asking as the OPP core can be improved to support your case if
possible. But I need to understand the problem first.
--
viresh
Powered by blists - more mailing lists