[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <39152c86-ca11-2792-6b25-ae55ffb47b09@linaro.org>
Date: Tue, 12 Apr 2022 11:17:06 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Johnson Wang <johnson.wang@...iatek.com>, cw00.choi@...sung.com,
krzk+dt@...nel.org, robh+dt@...nel.org, kyungmin.park@...sung.com
Cc: khilman@...nel.org, linux-pm@...r.kernel.org,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org, jia-wei.chang@...iatek.com,
Project_Global_Chrome_Upstream_Group@...iatek.com
Subject: Re: [PATCH v2 1/2] dt-bindings: devfreq: mediatek: Add mtk cci
devfreq dt-bindings
On 11/04/2022 14:10, Johnson Wang wrote:
>> Also please put it in the "interconnect" directory.
>>
>
> I don't really know about "interconnect".
> However, it looks like a Linux framework about data transfer and "NoC".
>
> While this cci driver is more like a power managment which is
> responsible for adjusting voltages and frequencies.
> In my opinion, "devfreq" should be more suitable.
>
> Please correct me if my understanding is wrong.
devfreq is a Linux mechanism, not a real device/hardware. We try to put
the bindings in directories/subsystems matching the hardware, therefore
devfreq is not appropriate.
Whether interconnect - or other subsystem - is appropriate, I am not
sure. To me this looks exactly like bus bandwidth management and you
even use "interconnect" in several places. So interconnect matches.
Best regards,
Krzysztof
Powered by blists - more mailing lists