[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <924e2208-d939-0243-9780-ae1b8cbd2c49@gmail.com>
Date: Thu, 14 Apr 2022 05:54:31 +0900
From: Chanwoo Choi <cwchoi00@...il.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
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 22. 4. 12. 18:17, Krzysztof Kozlowski wrote:
> 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.
I think that 'Documentation/devicetree/bindings/arm/mediatek' is proper.
--
Best Regards,
Samsung Electronics
Chanwoo Choi
Powered by blists - more mailing lists