[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0ef8f2c3-fd16-041b-3304-b167a2a36ff9@linaro.org>
Date: Fri, 8 Apr 2022 13:49:00 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Rex-BC Chen <rex-bc.chen@...iatek.com>, rafael@...nel.org,
viresh.kumar@...aro.org, robh+dt@...nel.org, krzk+dt@...nel.org
Cc: matthias.bgg@...il.com, jia-wei.chang@...iatek.com,
roger.lu@...iatek.com, hsinyi@...gle.com, linux-pm@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org,
Project_Global_Chrome_Upstream_Group@...iatek.com
Subject: Re: [PATCH V2 01/15] dt-bindings: cpufreq: mediatek: Add MediaTek CCI
property
On 08/04/2022 12:24, Rex-BC Chen wrote:
>>
>> You need to describe the type. I am a bit confused whether this is a
>> cci
>> (so cci-control-port property?) or an interconnect (so interconnect
>> property)... It does not look like a generic property, so you need
>> vendor prefix.
>
> Hello Krzysztof,
>
> Thanks for your review.
>
> Yes, this cci is not arm's cci (cci-control-port property), and it's
> mediatek's cci. I will revise this name to "mtk-cci" in next version.
Vendor is "mediatek" and comma comes after it. See devicetree spec
paragraph 2.3.1.
>
>>
>>> + For details, please refer to
>>> + Documentation/devicetree/bindings/devfreq/mtk-cci.yaml
>>
>> Such file does not exist.
>
> This mediatek cci is still upstreaming in this patch:
> message-id:20220408052150.22536-2-johnson.wang@...iatek.com
>
> Do you have suggestion that I should put this reference?
> Or I just remove it and describe the mediatek cci in detail?
It's ok, but you need to keep path/filename updated.
Best regards,
Krzysztof
Powered by blists - more mailing lists