Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6717FC61DA4 for ; Fri, 27 Jan 2023 03:08:09 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232177AbjA0DII (ORCPT ); Thu, 26 Jan 2023 22:08:08 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42262 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231266AbjA0DIF (ORCPT ); Thu, 26 Jan 2023 22:08:05 -0500 Received: from mail-oa1-x2b.google.com (mail-oa1-x2b.google.com [IPv6:2001:4860:4864:20::2b]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 752CA227A1; Thu, 26 Jan 2023 19:08:03 -0800 (PST) Received: by mail-oa1-x2b.google.com with SMTP id 586e51a60fabf-16346330067so4931662fac.3; Thu, 26 Jan 2023 19:08:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=eWVjgWC+CRaiVU6jf3be0WvlqWbyqa4cbGUte3LE0QY=; b=SvGlwWDC+KblJS2mqQCluTm269HgIQaXn+HLtXa7cMZkrTaP7lnJrOIR33mFaXXtH/ 8cL8KrnTBBZBGVXsgQ1DKAHWIM1+EKPpFW4p8IgxhR84Xbv3LigkPTByRA4kMaEdj6TU k7Kv1PNhnRA8GIoxbImSjJVcnIGMd9W4vnrh7KM6GtdcdB294Ly2ExbAI4DPIRsycidq ebpds6vqjuZg4C56lG2puV681tfO6LsMOE0MJ0KcEX5tTtzSLpp1IujIkVVhugeAFgp9 cvAJNHs9DU6/eY5NWUZIL8O6Ph//ikJT+Lk7G/rojhpgq5p2I7AuJy6bEG+5t5c459tI xUFg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=eWVjgWC+CRaiVU6jf3be0WvlqWbyqa4cbGUte3LE0QY=; b=osUSeku/sP88UW/fmIhl0IgJ5hEaMz7tsq4ANNqgk4hTplAKS8QMG8uTA69E1EIZ8f lcAhQsEhme9lnsx6jmJRNv5ue+xI4Z2VFf5AfV1gG4Ta2doUhhmfvEMDxcdcqV2OM74N 1UM6X9MInzTNkoJ3xePre6Ffm6ooNrGNxHOLg6Imm8lFb1wB2SP2abJT52v36/1tH3x4 LFNPOa6MAUxfTYyjr0UTSzqVO/v1mBnF9N27ZDMA8i1/FUbx5WvHwg0tLzQd5GD54iPw tro+IxOIfFrjfVzArNZp8PUspW2IvRyOnhCPOdf9+FmUAyKfHUKwcClsrkviA/z0Fmqc UMnA== X-Gm-Message-State: AFqh2koVJAGiwEyHBWif0QmVpLDqz6XG5Pd+QMz370sZHKKEyFU5eP/c 727sKVSxlvq7+4xcXoAlEXgQ+k22K3QEfB4VtpU= X-Google-Smtp-Source: AMrXdXtwNNbWR+EBpOWIEthHcrNWHYhATjGinf4U7RAj7/ORzz2dj7jhO7LE+yBhT7G/zMVkJANBNpaCoJ1m0UeBexw= X-Received: by 2002:a05:6870:44d0:b0:15b:96b8:e2be with SMTP id t16-20020a05687044d000b0015b96b8e2bemr2351141oai.38.1674788882705; Thu, 26 Jan 2023 19:08:02 -0800 (PST) MIME-Version: 1.0 References: <20230123153745.3185032-1-robdclark@gmail.com> <20230125040403epcms1p1646e9668b87df3e9c344ad58d39b6eb6@epcms1p1> <20230125054626epcms1p38d34dc65cbc9cb29dd707a4b2cac8fb4@epcms1p3> In-Reply-To: <20230125054626epcms1p38d34dc65cbc9cb29dd707a4b2cac8fb4@epcms1p3> From: Rob Clark Date: Thu, 26 Jan 2023 19:08:01 -0800 Message-ID: Subject: Re: Re: [PATCH] PM / devfreq: Fix build issues with devfreq disabled To: myungjoo.ham@samsung.com Cc: Chanwoo Choi , "linux-pm@vger.kernel.org" , "dri-devel@lists.freedesktop.org" , "freedreno@lists.freedesktop.org" , Krzysztof Kozlowski , Rob Clark , Kyungmin Park , Chia-I Wu , open list Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jan 24, 2023 at 9:46 PM MyungJoo Ham wrote: > > >On Tue, Jan 24, 2023 at 8:04 PM MyungJoo Ham wrote: > >> > >> >Sender : Rob Clark > >> >Date : 2023-01-24 00:37 (GMT+9) > >> >Title : [PATCH] PM / devfreq: Fix build issues with devfreq disabled > >> > > >> >From: Rob Clark > >> > > >> >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 > >> > >> 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 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