[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <25692922-7610-49bc-b33d-c799a13995cb@nvidia.com>
Date: Fri, 26 Sep 2025 11:33:13 +0100
From: Jon Hunter <jonathanh@...dia.com>
To: Jie Zhan <zhanjie9@...ilicon.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 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
--
nvpublic
Powered by blists - more mailing lists