* [PATCH] PM / devfreq: Fix build issues with devfreq disabled
@ 2023-01-23 15:37 ` Rob Clark
0 siblings, 0 replies; 10+ messages in thread
From: Rob Clark @ 2023-01-23 15:37 UTC (permalink / raw)
To: linux-pm
Cc: dri-devel, freedreno, Krzysztof Kozlowski, Rob Clark,
MyungJoo Ham, Kyungmin Park, Chanwoo Choi, Chia-I Wu, open list
From: Rob Clark <robdclark@chromium.org>
The existing no-op shims for when PM_DEVFREQ (or an individual governor)
only do half the job. The governor specific config/tuning structs need
to be available to avoid compile errors in drivers using devfreq.
Fixes: 6563f60f14cb ("drm/msm/gpu: Add devfreq tuning debugfs")
Signed-off-by: Rob Clark <robdclark@chromium.org>
---
Assuming this doesn't conflict with anything else landing via another
tree, an a-b to land this via drm/msm-next would let us un-break builds.
(And also start removing "select DEVFREQ_GOV_SIMPLE_ONDEMAND"s added in
various places to try to work around this issue.)
include/linux/devfreq.h | 7 ++-----
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/include/linux/devfreq.h b/include/linux/devfreq.h
index 4dc7cda4fd46..7fd704bb8f3d 100644
--- a/include/linux/devfreq.h
+++ b/include/linux/devfreq.h
@@ -273,8 +273,8 @@ void devm_devfreq_unregister_notifier(struct device *dev,
struct devfreq *devfreq_get_devfreq_by_node(struct device_node *node);
struct devfreq *devfreq_get_devfreq_by_phandle(struct device *dev,
const char *phandle_name, int index);
+#endif /* CONFIG_PM_DEVFREQ */
-#if IS_ENABLED(CONFIG_DEVFREQ_GOV_SIMPLE_ONDEMAND)
/**
* struct devfreq_simple_ondemand_data - ``void *data`` fed to struct devfreq
* and devfreq_add_device
@@ -292,9 +292,7 @@ struct devfreq_simple_ondemand_data {
unsigned int upthreshold;
unsigned int downdifferential;
};
-#endif
-#if IS_ENABLED(CONFIG_DEVFREQ_GOV_PASSIVE)
enum devfreq_parent_dev_type {
DEVFREQ_PARENT_DEV,
CPUFREQ_PARENT_DEV,
@@ -337,9 +335,8 @@ struct devfreq_passive_data {
struct notifier_block nb;
struct list_head cpu_data_list;
};
-#endif
-#else /* !CONFIG_PM_DEVFREQ */
+#if !defined(CONFIG_PM_DEVFREQ)
static inline struct devfreq *devfreq_add_device(struct device *dev,
struct devfreq_dev_profile *profile,
const char *governor_name,
--
2.38.1
^ permalink raw reply related [flat|nested] 10+ messages in thread
* [PATCH] PM / devfreq: Fix build issues with devfreq disabled
@ 2023-01-23 15:37 ` Rob Clark
0 siblings, 0 replies; 10+ messages in thread
From: Rob Clark @ 2023-01-23 15:37 UTC (permalink / raw)
To: linux-pm
Cc: Rob Clark, open list, Krzysztof Kozlowski, Chanwoo Choi,
Kyungmin Park, MyungJoo Ham, dri-devel, freedreno
From: Rob Clark <robdclark@chromium.org>
The existing no-op shims for when PM_DEVFREQ (or an individual governor)
only do half the job. The governor specific config/tuning structs need
to be available to avoid compile errors in drivers using devfreq.
Fixes: 6563f60f14cb ("drm/msm/gpu: Add devfreq tuning debugfs")
Signed-off-by: Rob Clark <robdclark@chromium.org>
---
Assuming this doesn't conflict with anything else landing via another
tree, an a-b to land this via drm/msm-next would let us un-break builds.
(And also start removing "select DEVFREQ_GOV_SIMPLE_ONDEMAND"s added in
various places to try to work around this issue.)
include/linux/devfreq.h | 7 ++-----
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/include/linux/devfreq.h b/include/linux/devfreq.h
index 4dc7cda4fd46..7fd704bb8f3d 100644
--- a/include/linux/devfreq.h
+++ b/include/linux/devfreq.h
@@ -273,8 +273,8 @@ void devm_devfreq_unregister_notifier(struct device *dev,
struct devfreq *devfreq_get_devfreq_by_node(struct device_node *node);
struct devfreq *devfreq_get_devfreq_by_phandle(struct device *dev,
const char *phandle_name, int index);
+#endif /* CONFIG_PM_DEVFREQ */
-#if IS_ENABLED(CONFIG_DEVFREQ_GOV_SIMPLE_ONDEMAND)
/**
* struct devfreq_simple_ondemand_data - ``void *data`` fed to struct devfreq
* and devfreq_add_device
@@ -292,9 +292,7 @@ struct devfreq_simple_ondemand_data {
unsigned int upthreshold;
unsigned int downdifferential;
};
-#endif
-#if IS_ENABLED(CONFIG_DEVFREQ_GOV_PASSIVE)
enum devfreq_parent_dev_type {
DEVFREQ_PARENT_DEV,
CPUFREQ_PARENT_DEV,
@@ -337,9 +335,8 @@ struct devfreq_passive_data {
struct notifier_block nb;
struct list_head cpu_data_list;
};
-#endif
-#else /* !CONFIG_PM_DEVFREQ */
+#if !defined(CONFIG_PM_DEVFREQ)
static inline struct devfreq *devfreq_add_device(struct device *dev,
struct devfreq_dev_profile *profile,
const char *governor_name,
--
2.38.1
^ permalink raw reply related [flat|nested] 10+ messages in thread
* RE: [PATCH] PM / devfreq: Fix build issues with devfreq disabled
[not found] ` <CGME20230123153745epcas1p17e57cf83ed371e86258139473befc615@epcms1p1>
@ 2023-01-25 4:04 ` MyungJoo Ham
0 siblings, 0 replies; 10+ messages in thread
From: MyungJoo Ham @ 2023-01-25 4:04 UTC (permalink / raw)
To: Rob Clark, linux-pm
Cc: dri-devel, freedreno, Krzysztof Kozlowski, Rob Clark,
Kyungmin Park, Chanwoo Choi, Chia-I Wu, open list
>Sender : Rob Clark <robdclark@gmail.com>
>Date : 2023-01-24 00:37 (GMT+9)
>Title : [PATCH] PM / devfreq: Fix build issues with devfreq disabled
>
>From: Rob Clark <robdclark@chromium.org>
>
>The existing no-op shims for when PM_DEVFREQ (or an individual governor)
>only do half the job. The governor specific config/tuning structs need
>to be available to avoid compile errors in drivers using devfreq.
>
>Fixes: 6563f60f14cb ("drm/msm/gpu: Add devfreq tuning debugfs")
>Signed-off-by: Rob Clark <robdclark@chromium.org>
Doesn't this imply that DRM_MSM should depend on PM_DEVFREQ ?
It appears that gpu/drm/msm/DRM_MSM uses PM_DEVFREQ without actually
declaring the dependency on PM_DEVFREQ.
You cannot use SIMPLE_ONDEMAND without DEVFREQ.
Cheers,
MyungJoo
>---
>Assuming this doesn't conflict with anything else landing via another
>tree, an a-b to land this via drm/msm-next would let us un-break builds.
>(And also start removing "select DEVFREQ_GOV_SIMPLE_ONDEMAND"s added in
>various places to try to work around this issue.)
>
> include/linux/devfreq.h | 7 ++-----
> 1 file changed, 2 insertions(+), 5 deletions(-)
>
>diff --git a/include/linux/devfreq.h b/include/linux/devfreq.h
>index 4dc7cda4fd46..7fd704bb8f3d 100644
>--- a/include/linux/devfreq.h
>+++ b/include/linux/devfreq.h
>@@ -273,8 +273,8 @@ void devm_devfreq_unregister_notifier(struct device *dev,
> struct devfreq *devfreq_get_devfreq_by_node(struct device_node *node);
> struct devfreq *devfreq_get_devfreq_by_phandle(struct device *dev,
> const char *phandle_name, int index);
>+#endif /* CONFIG_PM_DEVFREQ */
>
>-#if IS_ENABLED(CONFIG_DEVFREQ_GOV_SIMPLE_ONDEMAND)
> /**
> * struct devfreq_simple_ondemand_data - ``void *data`` fed to struct devfreq
> * and devfreq_add_device
>@@ -292,9 +292,7 @@ struct devfreq_simple_ondemand_data {
> unsigned int upthreshold;
> unsigned int downdifferential;
> };
>-#endif
>
>-#if IS_ENABLED(CONFIG_DEVFREQ_GOV_PASSIVE)
> enum devfreq_parent_dev_type {
> DEVFREQ_PARENT_DEV,
> CPUFREQ_PARENT_DEV,
>@@ -337,9 +335,8 @@ struct devfreq_passive_data {
> struct notifier_block nb;
> struct list_head cpu_data_list;
> };
>-#endif
>
>-#else /* !CONFIG_PM_DEVFREQ */
>+#if !defined(CONFIG_PM_DEVFREQ)
> static inline struct devfreq *devfreq_add_device(struct device *dev,
> struct devfreq_dev_profile *profile,
> const char *governor_name,
>--
>2.38.1
>
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: [PATCH] PM / devfreq: Fix build issues with devfreq disabled
@ 2023-01-25 4:04 ` MyungJoo Ham
0 siblings, 0 replies; 10+ messages in thread
From: MyungJoo Ham @ 2023-01-25 4:04 UTC (permalink / raw)
To: Rob Clark, linux-pm
Cc: Rob Clark, open list, Krzysztof Kozlowski, Chanwoo Choi,
Kyungmin Park, dri-devel, freedreno
>Sender : Rob Clark <robdclark@gmail.com>
>Date : 2023-01-24 00:37 (GMT+9)
>Title : [PATCH] PM / devfreq: Fix build issues with devfreq disabled
>
>From: Rob Clark <robdclark@chromium.org>
>
>The existing no-op shims for when PM_DEVFREQ (or an individual governor)
>only do half the job. The governor specific config/tuning structs need
>to be available to avoid compile errors in drivers using devfreq.
>
>Fixes: 6563f60f14cb ("drm/msm/gpu: Add devfreq tuning debugfs")
>Signed-off-by: Rob Clark <robdclark@chromium.org>
Doesn't this imply that DRM_MSM should depend on PM_DEVFREQ ?
It appears that gpu/drm/msm/DRM_MSM uses PM_DEVFREQ without actually
declaring the dependency on PM_DEVFREQ.
You cannot use SIMPLE_ONDEMAND without DEVFREQ.
Cheers,
MyungJoo
>---
>Assuming this doesn't conflict with anything else landing via another
>tree, an a-b to land this via drm/msm-next would let us un-break builds.
>(And also start removing "select DEVFREQ_GOV_SIMPLE_ONDEMAND"s added in
>various places to try to work around this issue.)
>
> include/linux/devfreq.h | 7 ++-----
> 1 file changed, 2 insertions(+), 5 deletions(-)
>
>diff --git a/include/linux/devfreq.h b/include/linux/devfreq.h
>index 4dc7cda4fd46..7fd704bb8f3d 100644
>--- a/include/linux/devfreq.h
>+++ b/include/linux/devfreq.h
>@@ -273,8 +273,8 @@ void devm_devfreq_unregister_notifier(struct device *dev,
> struct devfreq *devfreq_get_devfreq_by_node(struct device_node *node);
> struct devfreq *devfreq_get_devfreq_by_phandle(struct device *dev,
> const char *phandle_name, int index);
>+#endif /* CONFIG_PM_DEVFREQ */
>
>-#if IS_ENABLED(CONFIG_DEVFREQ_GOV_SIMPLE_ONDEMAND)
> /**
> * struct devfreq_simple_ondemand_data - ``void *data`` fed to struct devfreq
> * and devfreq_add_device
>@@ -292,9 +292,7 @@ struct devfreq_simple_ondemand_data {
> unsigned int upthreshold;
> unsigned int downdifferential;
> };
>-#endif
>
>-#if IS_ENABLED(CONFIG_DEVFREQ_GOV_PASSIVE)
> enum devfreq_parent_dev_type {
> DEVFREQ_PARENT_DEV,
> CPUFREQ_PARENT_DEV,
>@@ -337,9 +335,8 @@ struct devfreq_passive_data {
> struct notifier_block nb;
> struct list_head cpu_data_list;
> };
>-#endif
>
>-#else /* !CONFIG_PM_DEVFREQ */
>+#if !defined(CONFIG_PM_DEVFREQ)
> static inline struct devfreq *devfreq_add_device(struct device *dev,
> struct devfreq_dev_profile *profile,
> const char *governor_name,
>--
>2.38.1
>
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH] PM / devfreq: Fix build issues with devfreq disabled
2023-01-25 4:04 ` MyungJoo Ham
@ 2023-01-25 4:31 ` Rob Clark
-1 siblings, 0 replies; 10+ messages in thread
From: Rob Clark @ 2023-01-25 4:31 UTC (permalink / raw)
To: myungjoo.ham
Cc: Rob Clark, linux-pm, open list, Krzysztof Kozlowski,
Chanwoo Choi, Kyungmin Park, dri-devel, freedreno
On Tue, Jan 24, 2023 at 8:04 PM MyungJoo Ham <myungjoo.ham@samsung.com> wrote:
>
> >Sender : Rob Clark <robdclark@gmail.com>
> >Date : 2023-01-24 00:37 (GMT+9)
> >Title : [PATCH] PM / devfreq: Fix build issues with devfreq disabled
> >
> >From: Rob Clark <robdclark@chromium.org>
> >
> >The existing no-op shims for when PM_DEVFREQ (or an individual governor)
> >only do half the job. The governor specific config/tuning structs need
> >to be available to avoid compile errors in drivers using devfreq.
> >
> >Fixes: 6563f60f14cb ("drm/msm/gpu: Add devfreq tuning debugfs")
> >Signed-off-by: Rob Clark <robdclark@chromium.org>
>
> Doesn't this imply that DRM_MSM should depend on PM_DEVFREQ ?
>
> It appears that gpu/drm/msm/DRM_MSM uses PM_DEVFREQ without actually
> declaring the dependency on PM_DEVFREQ.
> You cannot use SIMPLE_ONDEMAND without DEVFREQ.
Possibly that would resolve some issues, and that might have been my
mistake in assuming that depending on SIMPLE_ONDEMAND implied a
dependency on DEFREQ (which seems like a reasonable assumption, IMHO)
But AFAICT some kernel configs that could otherwise use DRM_MSM don't
support PM_DEVFREQ.. either way, lets solve this properly and remove
needless dependencies on devfreq.
BR,
-R
> Cheers,
> MyungJoo
>
> >---
> >Assuming this doesn't conflict with anything else landing via another
> >tree, an a-b to land this via drm/msm-next would let us un-break builds.
> >(And also start removing "select DEVFREQ_GOV_SIMPLE_ONDEMAND"s added in
> >various places to try to work around this issue.)
> >
> > include/linux/devfreq.h | 7 ++-----
> > 1 file changed, 2 insertions(+), 5 deletions(-)
> >
> >diff --git a/include/linux/devfreq.h b/include/linux/devfreq.h
> >index 4dc7cda4fd46..7fd704bb8f3d 100644
> >--- a/include/linux/devfreq.h
> >+++ b/include/linux/devfreq.h
> >@@ -273,8 +273,8 @@ void devm_devfreq_unregister_notifier(struct device *dev,
> > struct devfreq *devfreq_get_devfreq_by_node(struct device_node *node);
> > struct devfreq *devfreq_get_devfreq_by_phandle(struct device *dev,
> > const char *phandle_name, int index);
> >+#endif /* CONFIG_PM_DEVFREQ */
> >
> >-#if IS_ENABLED(CONFIG_DEVFREQ_GOV_SIMPLE_ONDEMAND)
> > /**
> > * struct devfreq_simple_ondemand_data - ``void *data`` fed to struct devfreq
> > * and devfreq_add_device
> >@@ -292,9 +292,7 @@ struct devfreq_simple_ondemand_data {
> > unsigned int upthreshold;
> > unsigned int downdifferential;
> > };
> >-#endif
> >
> >-#if IS_ENABLED(CONFIG_DEVFREQ_GOV_PASSIVE)
> > enum devfreq_parent_dev_type {
> > DEVFREQ_PARENT_DEV,
> > CPUFREQ_PARENT_DEV,
> >@@ -337,9 +335,8 @@ struct devfreq_passive_data {
> > struct notifier_block nb;
> > struct list_head cpu_data_list;
> > };
> >-#endif
> >
> >-#else /* !CONFIG_PM_DEVFREQ */
> >+#if !defined(CONFIG_PM_DEVFREQ)
> > static inline struct devfreq *devfreq_add_device(struct device *dev,
> > struct devfreq_dev_profile *profile,
> > const char *governor_name,
> >--
> >2.38.1
> >
>
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH] PM / devfreq: Fix build issues with devfreq disabled
@ 2023-01-25 4:31 ` Rob Clark
0 siblings, 0 replies; 10+ messages in thread
From: Rob Clark @ 2023-01-25 4:31 UTC (permalink / raw)
To: myungjoo.ham
Cc: linux-pm, dri-devel, freedreno, Krzysztof Kozlowski, Rob Clark,
Kyungmin Park, Chanwoo Choi, Chia-I Wu, open list
On Tue, Jan 24, 2023 at 8:04 PM MyungJoo Ham <myungjoo.ham@samsung.com> wrote:
>
> >Sender : Rob Clark <robdclark@gmail.com>
> >Date : 2023-01-24 00:37 (GMT+9)
> >Title : [PATCH] PM / devfreq: Fix build issues with devfreq disabled
> >
> >From: Rob Clark <robdclark@chromium.org>
> >
> >The existing no-op shims for when PM_DEVFREQ (or an individual governor)
> >only do half the job. The governor specific config/tuning structs need
> >to be available to avoid compile errors in drivers using devfreq.
> >
> >Fixes: 6563f60f14cb ("drm/msm/gpu: Add devfreq tuning debugfs")
> >Signed-off-by: Rob Clark <robdclark@chromium.org>
>
> Doesn't this imply that DRM_MSM should depend on PM_DEVFREQ ?
>
> It appears that gpu/drm/msm/DRM_MSM uses PM_DEVFREQ without actually
> declaring the dependency on PM_DEVFREQ.
> You cannot use SIMPLE_ONDEMAND without DEVFREQ.
Possibly that would resolve some issues, and that might have been my
mistake in assuming that depending on SIMPLE_ONDEMAND implied a
dependency on DEFREQ (which seems like a reasonable assumption, IMHO)
But AFAICT some kernel configs that could otherwise use DRM_MSM don't
support PM_DEVFREQ.. either way, lets solve this properly and remove
needless dependencies on devfreq.
BR,
-R
> Cheers,
> MyungJoo
>
> >---
> >Assuming this doesn't conflict with anything else landing via another
> >tree, an a-b to land this via drm/msm-next would let us un-break builds.
> >(And also start removing "select DEVFREQ_GOV_SIMPLE_ONDEMAND"s added in
> >various places to try to work around this issue.)
> >
> > include/linux/devfreq.h | 7 ++-----
> > 1 file changed, 2 insertions(+), 5 deletions(-)
> >
> >diff --git a/include/linux/devfreq.h b/include/linux/devfreq.h
> >index 4dc7cda4fd46..7fd704bb8f3d 100644
> >--- a/include/linux/devfreq.h
> >+++ b/include/linux/devfreq.h
> >@@ -273,8 +273,8 @@ void devm_devfreq_unregister_notifier(struct device *dev,
> > struct devfreq *devfreq_get_devfreq_by_node(struct device_node *node);
> > struct devfreq *devfreq_get_devfreq_by_phandle(struct device *dev,
> > const char *phandle_name, int index);
> >+#endif /* CONFIG_PM_DEVFREQ */
> >
> >-#if IS_ENABLED(CONFIG_DEVFREQ_GOV_SIMPLE_ONDEMAND)
> > /**
> > * struct devfreq_simple_ondemand_data - ``void *data`` fed to struct devfreq
> > * and devfreq_add_device
> >@@ -292,9 +292,7 @@ struct devfreq_simple_ondemand_data {
> > unsigned int upthreshold;
> > unsigned int downdifferential;
> > };
> >-#endif
> >
> >-#if IS_ENABLED(CONFIG_DEVFREQ_GOV_PASSIVE)
> > enum devfreq_parent_dev_type {
> > DEVFREQ_PARENT_DEV,
> > CPUFREQ_PARENT_DEV,
> >@@ -337,9 +335,8 @@ struct devfreq_passive_data {
> > struct notifier_block nb;
> > struct list_head cpu_data_list;
> > };
> >-#endif
> >
> >-#else /* !CONFIG_PM_DEVFREQ */
> >+#if !defined(CONFIG_PM_DEVFREQ)
> > static inline struct devfreq *devfreq_add_device(struct device *dev,
> > struct devfreq_dev_profile *profile,
> > const char *governor_name,
> >--
> >2.38.1
> >
>
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: Re: [PATCH] PM / devfreq: Fix build issues with devfreq disabled
[not found] ` <CGME20230123153745epcas1p17e57cf83ed371e86258139473befc615@epcms1p3>
@ 2023-01-25 5:46 ` MyungJoo Ham
0 siblings, 0 replies; 10+ messages in thread
From: MyungJoo Ham @ 2023-01-25 5:46 UTC (permalink / raw)
To: Rob Clark, Chanwoo Choi
Cc: linux-pm, dri-devel, freedreno, Krzysztof Kozlowski, Rob Clark,
Kyungmin Park, Chia-I Wu, open list
>On Tue, Jan 24, 2023 at 8:04 PM MyungJoo Ham <myungjoo.ham@samsung.com> wrote:
>>
>> >Sender : Rob Clark <robdclark@gmail.com>
>> >Date : 2023-01-24 00:37 (GMT+9)
>> >Title : [PATCH] PM / devfreq: Fix build issues with devfreq disabled
>> >
>> >From: Rob Clark <robdclark@chromium.org>
>> >
>> >The existing no-op shims for when PM_DEVFREQ (or an individual governor)
>> >only do half the job. The governor specific config/tuning structs need
>> >to be available to avoid compile errors in drivers using devfreq.
>> >
>> >Fixes: 6563f60f14cb ("drm/msm/gpu: Add devfreq tuning debugfs")
>> >Signed-off-by: Rob Clark <robdclark@chromium.org>
>>
>> Doesn't this imply that DRM_MSM should depend on PM_DEVFREQ ?
>>
>> It appears that gpu/drm/msm/DRM_MSM uses PM_DEVFREQ without actually
>> declaring the dependency on PM_DEVFREQ.
>> You cannot use SIMPLE_ONDEMAND without DEVFREQ.
>
>Possibly that would resolve some issues, and that might have been my
>mistake in assuming that depending on SIMPLE_ONDEMAND implied a
>dependency on DEFREQ (which seems like a reasonable assumption, IMHO)
>
>But AFAICT some kernel configs that could otherwise use DRM_MSM don't
>support PM_DEVFREQ.. either way, lets solve this properly and remove
>needless dependencies on devfreq.
>
>BR,
>-R
Ok. You are enabling struct and enum only and that looks harmless.
PTAL, Chanwoo.
Acked-by: MyungJoo Ham <myungjoo.ham@samsung.com>
Cheers,
MyungJoo.
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: Re: [PATCH] PM / devfreq: Fix build issues with devfreq disabled
@ 2023-01-25 5:46 ` MyungJoo Ham
0 siblings, 0 replies; 10+ messages in thread
From: MyungJoo Ham @ 2023-01-25 5:46 UTC (permalink / raw)
To: Rob Clark, Chanwoo Choi
Cc: Rob Clark, linux-pm, open list, Krzysztof Kozlowski,
Kyungmin Park, dri-devel, freedreno
>On Tue, Jan 24, 2023 at 8:04 PM MyungJoo Ham <myungjoo.ham@samsung.com> wrote:
>>
>> >Sender : Rob Clark <robdclark@gmail.com>
>> >Date : 2023-01-24 00:37 (GMT+9)
>> >Title : [PATCH] PM / devfreq: Fix build issues with devfreq disabled
>> >
>> >From: Rob Clark <robdclark@chromium.org>
>> >
>> >The existing no-op shims for when PM_DEVFREQ (or an individual governor)
>> >only do half the job. The governor specific config/tuning structs need
>> >to be available to avoid compile errors in drivers using devfreq.
>> >
>> >Fixes: 6563f60f14cb ("drm/msm/gpu: Add devfreq tuning debugfs")
>> >Signed-off-by: Rob Clark <robdclark@chromium.org>
>>
>> Doesn't this imply that DRM_MSM should depend on PM_DEVFREQ ?
>>
>> It appears that gpu/drm/msm/DRM_MSM uses PM_DEVFREQ without actually
>> declaring the dependency on PM_DEVFREQ.
>> You cannot use SIMPLE_ONDEMAND without DEVFREQ.
>
>Possibly that would resolve some issues, and that might have been my
>mistake in assuming that depending on SIMPLE_ONDEMAND implied a
>dependency on DEFREQ (which seems like a reasonable assumption, IMHO)
>
>But AFAICT some kernel configs that could otherwise use DRM_MSM don't
>support PM_DEVFREQ.. either way, lets solve this properly and remove
>needless dependencies on devfreq.
>
>BR,
>-R
Ok. You are enabling struct and enum only and that looks harmless.
PTAL, Chanwoo.
Acked-by: MyungJoo Ham <myungjoo.ham@samsung.com>
Cheers,
MyungJoo.
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Re: [PATCH] PM / devfreq: Fix build issues with devfreq disabled
2023-01-25 5:46 ` MyungJoo Ham
@ 2023-01-27 3:08 ` Rob Clark
-1 siblings, 0 replies; 10+ messages in thread
From: Rob Clark @ 2023-01-27 3:08 UTC (permalink / raw)
To: myungjoo.ham
Cc: Chanwoo Choi, linux-pm, dri-devel, freedreno,
Krzysztof Kozlowski, Rob Clark, Kyungmin Park, Chia-I Wu,
open list
On Tue, Jan 24, 2023 at 9:46 PM MyungJoo Ham <myungjoo.ham@samsung.com> wrote:
>
> >On Tue, Jan 24, 2023 at 8:04 PM MyungJoo Ham <myungjoo.ham@samsung.com> wrote:
> >>
> >> >Sender : Rob Clark <robdclark@gmail.com>
> >> >Date : 2023-01-24 00:37 (GMT+9)
> >> >Title : [PATCH] PM / devfreq: Fix build issues with devfreq disabled
> >> >
> >> >From: Rob Clark <robdclark@chromium.org>
> >> >
> >> >The existing no-op shims for when PM_DEVFREQ (or an individual governor)
> >> >only do half the job. The governor specific config/tuning structs need
> >> >to be available to avoid compile errors in drivers using devfreq.
> >> >
> >> >Fixes: 6563f60f14cb ("drm/msm/gpu: Add devfreq tuning debugfs")
> >> >Signed-off-by: Rob Clark <robdclark@chromium.org>
> >>
> >> Doesn't this imply that DRM_MSM should depend on PM_DEVFREQ ?
> >>
> >> It appears that gpu/drm/msm/DRM_MSM uses PM_DEVFREQ without actually
> >> declaring the dependency on PM_DEVFREQ.
> >> You cannot use SIMPLE_ONDEMAND without DEVFREQ.
> >
> >Possibly that would resolve some issues, and that might have been my
> >mistake in assuming that depending on SIMPLE_ONDEMAND implied a
> >dependency on DEFREQ (which seems like a reasonable assumption, IMHO)
> >
> >But AFAICT some kernel configs that could otherwise use DRM_MSM don't
> >support PM_DEVFREQ.. either way, lets solve this properly and remove
> >needless dependencies on devfreq.
> >
> >BR,
> >-R
>
> Ok. You are enabling struct and enum only and that looks harmless.
>
> PTAL, Chanwoo.
>
> Acked-by: MyungJoo Ham <myungjoo.ham@samsung.com>
Thanks, if possible, an ack to land this via msm-next would avoid
build break headaches with COMPILE_TEST=y and other more obscure
setups
BR,
-R
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Re: [PATCH] PM / devfreq: Fix build issues with devfreq disabled
@ 2023-01-27 3:08 ` Rob Clark
0 siblings, 0 replies; 10+ messages in thread
From: Rob Clark @ 2023-01-27 3:08 UTC (permalink / raw)
To: myungjoo.ham
Cc: Rob Clark, linux-pm, open list, Krzysztof Kozlowski,
Chanwoo Choi, Kyungmin Park, dri-devel, freedreno
On Tue, Jan 24, 2023 at 9:46 PM MyungJoo Ham <myungjoo.ham@samsung.com> wrote:
>
> >On Tue, Jan 24, 2023 at 8:04 PM MyungJoo Ham <myungjoo.ham@samsung.com> wrote:
> >>
> >> >Sender : Rob Clark <robdclark@gmail.com>
> >> >Date : 2023-01-24 00:37 (GMT+9)
> >> >Title : [PATCH] PM / devfreq: Fix build issues with devfreq disabled
> >> >
> >> >From: Rob Clark <robdclark@chromium.org>
> >> >
> >> >The existing no-op shims for when PM_DEVFREQ (or an individual governor)
> >> >only do half the job. The governor specific config/tuning structs need
> >> >to be available to avoid compile errors in drivers using devfreq.
> >> >
> >> >Fixes: 6563f60f14cb ("drm/msm/gpu: Add devfreq tuning debugfs")
> >> >Signed-off-by: Rob Clark <robdclark@chromium.org>
> >>
> >> Doesn't this imply that DRM_MSM should depend on PM_DEVFREQ ?
> >>
> >> It appears that gpu/drm/msm/DRM_MSM uses PM_DEVFREQ without actually
> >> declaring the dependency on PM_DEVFREQ.
> >> You cannot use SIMPLE_ONDEMAND without DEVFREQ.
> >
> >Possibly that would resolve some issues, and that might have been my
> >mistake in assuming that depending on SIMPLE_ONDEMAND implied a
> >dependency on DEFREQ (which seems like a reasonable assumption, IMHO)
> >
> >But AFAICT some kernel configs that could otherwise use DRM_MSM don't
> >support PM_DEVFREQ.. either way, lets solve this properly and remove
> >needless dependencies on devfreq.
> >
> >BR,
> >-R
>
> Ok. You are enabling struct and enum only and that looks harmless.
>
> PTAL, Chanwoo.
>
> Acked-by: MyungJoo Ham <myungjoo.ham@samsung.com>
Thanks, if possible, an ack to land this via msm-next would avoid
build break headaches with COMPILE_TEST=y and other more obscure
setups
BR,
-R
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2023-01-27 3:08 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-01-23 15:37 [PATCH] PM / devfreq: Fix build issues with devfreq disabled Rob Clark
2023-01-23 15:37 ` Rob Clark
[not found] ` <CGME20230123153745epcas1p17e57cf83ed371e86258139473befc615@epcms1p1>
2023-01-25 4:04 ` MyungJoo Ham
2023-01-25 4:04 ` MyungJoo Ham
2023-01-25 4:31 ` Rob Clark
2023-01-25 4:31 ` Rob Clark
[not found] ` <CGME20230123153745epcas1p17e57cf83ed371e86258139473befc615@epcms1p3>
2023-01-25 5:46 ` MyungJoo Ham
2023-01-25 5:46 ` MyungJoo Ham
2023-01-27 3:08 ` Rob Clark
2023-01-27 3:08 ` Rob Clark
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.