Re: [PATCH 2/2] PM / devfreq: qcom: Introduce CCI devfreq driver

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 01/02/2023 17:12, Dmitry Baryshkov wrote:
On 01/02/2023 17:17, Bryan O'Donoghue wrote:
On 01/02/2023 14:58, Dmitry Baryshkov wrote:
On 01/02/2023 16:45, Bryan O'Donoghue wrote:
On 01/02/2023 13:41, Dmitry Baryshkov wrote:
                          cci-cpufreq {
                                  target-dev = <&cci_cache>;
                                  cpu-to-dev-map-0 =
                                          <  200000  200000000 >,
                                          <  345600  200000000 >,
                                          <  400000  200000000 >,
                                          <  533330  297600000 >,
                                          <  800000  297600000 >,
                                          <  960000  297600000 >,
                                          < 1113600  297000000 >,
                                          < 1344000  595200000 >,
                                          < 1459200  595200000 >,
                                          < 1497600  595200000 >,
                                          < 1651200  595200000 >;
                                  cpu-to-dev-map-4 =
                                          <  200000 200000000 >,
                                          <  249600 200000000 >,
                                          <  499200 297600000 >,
                                          <  800000 297600000 >,
                                          <  998400 595200000 >,
                                          < 1113600 595200000 >;
These should map to existing opp entries.

I ended up doing the interconnect driver that maps a clock to the
interconnect. Then I can use it in the cpu opp tables.


Can you point us at what it is you are proposing ?

https://patchwork.kernel.org/project/linux-arm-msm/patch/20230120061417.2623751-9-dmitry.baryshkov@xxxxxxxxxx/

Is there no driver code too ?

There are two parts, one is the 'CBF clock' driver, which just provides a clock, another part actually connects the clock and interconnect. Initially I implemented it as a part of the CBF driver (see https://patchwork.kernel.org/project/linux-arm-msm/patch/20230120061417.2623751-5-dmitry.baryshkov@xxxxxxxxxx/), next revision will move the interconnect part to drivers/interconnect.


Ah so just to be clear - discussing with Dmitry - CCI has its own set of fuses.

We have fusebin settings for clusterX and CCI.

So, I think we agree this means a separate driver for cci is warranted.

---
bod



[Index of Archives]     [Device Tree Compilter]     [Device Tree Spec]     [Linux Driver Backports]     [Video for Linux]     [Linux USB Devel]     [Linux PCI Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Yosemite Backpacking]


  Powered by Linux