All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tang Yizhou <tangyizhou@huawei.com>
To: Alex Shi <seakeel@gmail.com>
Cc: Yanteng Si <siyanteng@loongson.cn>, Alex Shi <alexs@kernel.org>,
	"Linux Doc Mailing List" <linux-doc@vger.kernel.org>,
	Jonathan Corbet <corbet@lwn.net>, <zhengbin13@huawei.com>
Subject: Re: [PATCH] doc/zh-CN: Update cpu-freq/core.rst to make it more readable
Date: Wed, 1 Dec 2021 21:33:24 +0800	[thread overview]
Message-ID: <4ace4916-9cd2-1f18-7fb0-2a2e9feee667@huawei.com> (raw)
In-Reply-To: <CAJy-Amk1iYsJQcerQG+JCE-ARyyvtUYGLminhZhW6aBj1vfSNQ@mail.gmail.com>



On 2021/12/1 16:31, Alex Shi wrote:
> On Tue, Nov 30, 2021 at 11:06 PM Tang Yizhou <tangyizhou@huawei.com> wrote:
>>
>> Signed-off-by: Tang Yizhou <tangyizhou@huawei.com>
>> ---
>>  .../translations/zh_CN/cpu-freq/core.rst      | 20 +++++++++----------
>>  1 file changed, 10 insertions(+), 10 deletions(-)
>>
>> diff --git a/Documentation/translations/zh_CN/cpu-freq/core.rst b/Documentation/translations/zh_CN/cpu-freq/core.rst
>> index 0c6fd447ced6..bf83cad70b68 100644
>> --- a/Documentation/translations/zh_CN/cpu-freq/core.rst
>> +++ b/Documentation/translations/zh_CN/cpu-freq/core.rst
>> @@ -29,10 +29,10 @@ CPUFreq核心和CPUFreq通知器的通用说明
>>  ======================
>>
>>  cpufreq核心代码位于drivers/cpufreq/cpufreq.c中。这些cpufreq代码为CPUFreq架构的驱
>> -动程序(那些操作硬件切换频率的代码)以及 "通知器 "提供了一个标准化的接口。
>> -这些是设备驱动程序或需要了解策略变化的其它内核部分(如 ACPI 热量管理)或所有频率更改(除
>> -计时代码外),甚至需要强制确定速度限制的通知器(如 ARM 架构上的 LCD 驱动程序)。
>> -此外, 内核 "常数" loops_per_jiffy会根据频率变化而更新。
>> +动程序(那些执行硬件频率切换的代码)以及 "通知器" 提供了一个标准化的接口。
>> +包括设备驱动程序;需要了解策略变化(如 ACPI 热量管理),或所有频率变化(如计时代码),
>> +甚至需要强制限制为指定频率(如 ARM 架构上的 LCD 驱动程序)的其它内核组件。
>> +此外,内核 "常数" loops_per_jiffy 会根据频率变化而更新。
>>
>>  cpufreq策略的引用计数由 cpufreq_cpu_get 和 cpufreq_cpu_put 来完成,以确保 cpufreq 驱
>>  动程序被正确地注册到核心中,并且驱动程序在 cpufreq_put_cpu 被调用之前不会被卸载。这也保证
>> @@ -41,7 +41,7 @@ cpufreq策略的引用计数由 cpufreq_cpu_get 和 cpufreq_cpu_put 来完成,
>>  2. CPUFreq 通知器
>>  ====================
>>
>> -CPUFreq通知器符合标准的内核通知器接口。
>> +CPUFreq通知器遵循标准的内核通知器接口。
>>  关于通知器的细节请参阅 linux/include/linux/notifier.h。
>>
>>  这里有两个不同的CPUfreq通知器 - 策略通知器和转换通知器。
>> @@ -69,20 +69,20 @@ CPUFreq通知器符合标准的内核通知器接口。
>>
>>  第三个参数是一个包含如下值的结构体cpufreq_freqs:
>>
>> -=====  ====================
>> -cpu    受影响cpu的编号
>> +====== ===============================
> 
> LGTM,
> Reviewed-by: Alex Shi <alexs@kernel.org>
> 
> BTW, please make sure the '=' count is right. -- I didn't count them. :)

I have checked the HTML page. There is no problem. Thanks.

> 
>> +policy 指向struct cpufreq_policy的指针
>>  old    旧频率
>>  new    新频率
>>  flags  cpufreq驱动的标志
>> -=====  ====================
>> +====== ===============================
>>
>>  3. 含有Operating Performance Point (OPP)的CPUFreq表的生成
>>  ==================================================================
>>  关于OPP的细节请参阅 Documentation/power/opp.rst
>>
>>  dev_pm_opp_init_cpufreq_table -
>> -       这个功能提供了一个随时可用的转换程序,用来将OPP层关于可用频率的内部信息翻译成一种容易提供给
>> -       cpufreq的格式。
>> +       这个函数提供了一个随时可用的转换例程,用来将OPP层关于可用频率的内部信息翻译成一种
>> +       cpufreq易于理解格式。
>>
>>         .. Warning::
>>
>> --
>> 2.17.1
>>

Tang

  reply	other threads:[~2021-12-01 13:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-30 15:34 [PATCH] doc/zh-CN: Update cpu-freq/core.rst to make it more readable Tang Yizhou
2021-12-01  8:31 ` Alex Shi
2021-12-01 13:33   ` Tang Yizhou [this message]
2021-12-02  9:53 ` teng sterling
2021-12-02 12:26   ` Tang Yizhou
2021-12-03  2:29     ` teng sterling

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4ace4916-9cd2-1f18-7fb0-2a2e9feee667@huawei.com \
    --to=tangyizhou@huawei.com \
    --cc=alexs@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=seakeel@gmail.com \
    --cc=siyanteng@loongson.cn \
    --cc=zhengbin13@huawei.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.