[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d46621fc-94d1-8c33-76e9-00825763719b@189.cn>
Date: Tue, 11 Apr 2023 18:44:32 +0800
From: Sui Jingfeng <15330273260@....cn>
To: Emil Velikov <emil.l.velikov@...il.com>
Cc: Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>,
Thomas Zimmermann <tzimmermann@...e.de>,
David Airlie <airlied@...il.com>,
Daniel Vetter <daniel@...ll.ch>,
Sumit Semwal <sumit.semwal@...aro.org>,
Christian Koenig <christian.koenig@....com>,
linaro-mm-sig@...ts.linaro.org, Li Yi <liyi@...ngson.cn>,
linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org,
nathan@...nel.org, linux-media@...r.kernel.org,
loongson-kernel@...ts.loongnix.cn
Subject: Re: [PATCH v10 2/2] drm: add kms driver for loongson display
controller
Hi,
On 2023/4/4 22:10, Emil Velikov wrote:
>> +static const struct dev_pm_ops lsdc_pm_ops = {
>> + .suspend = lsdc_pm_suspend,
>> + .resume = lsdc_pm_resume,
>> + .freeze = lsdc_pm_freeze,
>> + .thaw = lsdc_pm_thaw,
>> + .poweroff = lsdc_pm_freeze,
>> + .restore = lsdc_pm_resume,
>> +};
>> +
> The above section (and functions) should probably be wrapped in a
> CONFIG_PM_SLEEP block.
>
I agree with you.
I see imx-drm has this guard, but it's for embedded platform.
But I also see drm/ast and drm/radeon also didn't add this.
Maybe S3/S4 support is mandatory for PC platform?
Coding this way to force the kernel to enable PM_SLEEP option, otherwise
there a pile of driver won't get compiled.
At lease drm/ast and drm/radeon is usable on LoongArch/Mips/X86-64 platform.
Powered by blists - more mailing lists