Linux Power Management development
 help / color / mirror / Atom feed
From: qianfan <qianfanguijin@163.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Jernej Škrabec" <jernej.skrabec@gmail.com>,
	linux-sunxi@lists.linux.dev, "Rob Herring" <robh+dt@kernel.org>,
	"Maxime Ripard" <mripard@kernel.org>,
	"Chen-Yu Tsai" <wens@csie.org>,
	"Rafael J . Wysocki" <rafael@kernel.org>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH v2] drivers: cpufreq: sun8i-r40: Add cpufreq support
Date: Thu, 12 May 2022 14:22:33 +0800	[thread overview]
Message-ID: <4e5a263d-462b-b17a-d4c2-2b8b02faa589@163.com> (raw)
In-Reply-To: <20220512045838.tvixosxbey5ksp6j@vireshk-i7>



在 2022/5/12 12:58, Viresh Kumar 写道:
> On 12-05-22, 12:34, qianfan wrote:
>> Actually I'm not make sure the difference, seems both of them can work.
>> Most of allwinner device_id is added in allowlist, so I did this.
> For OPP V1 the cpufreq device isn't created by default and hence the allowlist
> allows us to know the devices for which the device shall be created.
>
> For OPP V2, we have the compatible string available and with help of that we
> create a device without need of any entry to any list. The blocklist however
> allows us to skip creating the device for some platforms, which don't want it.
>
> As your case is opp-v2 and you want the device, you aren't required to add entry
> anywhere.
I read the source code again and understand the behaivors.
And I will it from allowlist.

Thanks
>


      reply	other threads:[~2022-05-12  6:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-10  0:36 [PATCH v2] drivers: cpufreq: sun8i-r40: Add cpufreq support qianfanguijin
2022-05-11 20:13 ` Jernej Škrabec
2022-05-12  4:34   ` qianfan
2022-05-12  4:58     ` Viresh Kumar
2022-05-12  6:22       ` qianfan [this message]

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=4e5a263d-462b-b17a-d4c2-2b8b02faa589@163.com \
    --to=qianfanguijin@163.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jernej.skrabec@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=mripard@kernel.org \
    --cc=rafael@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=viresh.kumar@linaro.org \
    --cc=wens@csie.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox