[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ad2c72e8-4608-9527-146d-43aa006e1306@linaro.org>
Date: Tue, 12 Apr 2022 10:51:29 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Johnson Wang <johnson.wang@...iatek.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
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 2/2] PM / devfreq: mediatek: Introduce MediaTek CCI
devfreq driver
On 12/04/2022 10:39, Johnson Wang wrote:
>>> +static struct platform_driver mtk_ccifreq_platdrv = {
>>> + .probe = mtk_ccifreq_probe,
>>> + .remove = mtk_ccifreq_remove,
>>> + .driver = {
>>> + .name = "mtk-ccifreq",
>>> + .of_match_table = of_match_ptr(mtk_ccifreq_machines),
>>
>> You use of_match_ptr() so is it possible to build it without OF? If
>> so,
>> then mtk_ccifreq_machines needs maybe_unused.
>>
>
> No, this driver must be built with OF due to our CPU arch.
COMPILE_TEST does not use your arch... There are stubs for most of
of-like functions, so !OF should build anyway.
> Should I add some dependencies in Kconfig to ensure OF is enabled?
There are different ways to solve it and it depends on what goal do you
want to achieve? One ways is to use maybe_unused and of_match_ptr. Other
way is to do not use them (skip both).
Best regards,
Krzysztof
Powered by blists - more mailing lists