[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <d694df21-235f-422e-ba08-1eb442b376bd@hisilicon.com>
Date: Sun, 28 Sep 2025 10:01:56 +0800
From: Jie Zhan <zhanjie9@...ilicon.com>
To: Jon Hunter <jonathanh@...dia.com>, Dmitry Baryshkov
<dmitry.baryshkov@....qualcomm.com>, MyungJoo Ham <myungjoo.ham@...sung.com>,
Kyungmin Park <kyungmin.park@...sung.com>, Chanwoo Choi
<cw00.choi@...sung.com>, Dmitry Osipenko <digetx@...il.com>, Thierry Reding
<thierry.reding@...il.com>
CC: <linux-pm@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-tegra@...r.kernel.org>, <linux-arm-msm@...r.kernel.org>, Robie Basak
<robibasa@....qualcomm.com>
Subject: Re: [PATCH] devreq: move governor.h to a public header location
On 9/26/2025 6:33 PM, Jon Hunter wrote:
>
> On 26/09/2025 04:16, Jie Zhan wrote:
>>
>> Hi Dmitry,
>>
>> On 9/3/2025 9:43 PM, Dmitry Baryshkov wrote:
>>> Some device drivers (and out-of-tree modules) might want to define
>>> device-specific device governors. Rather than restricting all of them to
>>> be a part of drivers/devfreq/ (which is not possible for out-of-tree
>>> drivers anyway) move governor.h to include/linux/devfreq-governor.h and
>>> update all drivers to use it.
>>
>> For out-of-tree module compilation, can it add drivers/devfreq/ to the
>> include path?
>> I suppose this is unnecessary.
>
> The kernel header/source package created for most linux distros will not included this header because it is internal and so in that case it is necessary.
>
> Jon
>
Got it, thanks.
Powered by blists - more mailing lists