Re: [PATCH v2] PM: add kernel parameter to disable asynchronous suspend/resume

[Randy Dunlap <rdunlap@infradead.org>]

On 7/8/25 8:58 AM, Tudor Ambarus wrote:
> 
> 
> On 7/8/25 4:36 PM, Randy Dunlap wrote:
>> Hi,
>>
> 
> Hi, Randy!
> 
>> On 7/8/25 8:16 AM, Tudor Ambarus wrote:
>>
>>> ---
>>>  Documentation/admin-guide/kernel-parameters.txt | 11 +++++++++++
>>>  kernel/power/main.c                             |  9 +++++++++
>>>  2 files changed, 20 insertions(+)
>>>
>>> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
>>> index f1f2c0874da9ddfc95058c464fdf5dabaf0de713..33ca6b881b1d77bdeea765b19291a90b2a82e8a3 100644
>>> --- a/Documentation/admin-guide/kernel-parameters.txt
>>> +++ b/Documentation/admin-guide/kernel-parameters.txt
>>> @@ -5000,6 +5000,17 @@
>>>  			that number, otherwise (e.g., 'pmu_override=on'), MMCR1
>>>  			remains 0.
>>>  
>>
>> This should be more like:
>>
>>
>> 	pm_async=off	[PM]
>>
>> or
>>
>>> +	pm_async	[PM]
>>
>> 	pm_async=	[PM]
>> 			Format: off
> 
> Indeed. I see this second description, "kernel_param=", largely used in
> the existing kernel parameters, so maybe that's what I shall follow.
> However, I don't really know which format to choose, I see:
> 
> Format: <string>
> Format: { off }
> Format: {off}
> Format: { "off" }
> Format: {"off"}
> Format: off
> 
> Any idea if there's an already agreed string format?

Hi,
AFAIK there isn't one. Just choose one. :)

I would go with the first choice that I listed
but it's up to you.

-- 
~Randy