cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kukjin Kim <kgene.kim@samsung.com>
To: 'MyungJoo Ham' <myungjoo.ham@gmail.com>
Cc: linux-samsung-soc@vger.kernel.org, cpufreq@vger.kernel.org,
	davej@redhat.com, 'Jaecheol Lee' <jc.lee@samsung.com>
Subject: RE: [PATCH 5/5] [CPUFREQ] EXYNOS4210: Add support ASV feature
Date: Sat, 05 Nov 2011 10:25:33 +0900	[thread overview]
Message-ID: <02e001cc9b59$d09ff400$71dfdc00$%kim@samsung.com> (raw)
In-Reply-To: <CAJ0PZbQEHXpRdCkcAwNwtK7AmH=nxG+KjOcw91gwagAvFr_pxA@mail.gmail.com>

MyungJoo Ham wrote:
> 
> Hello,
> 
Hi,

I got the comments from Jaecheol Lee but his mail client has some problem so
I'm sending instead.

> On Wed, Nov 2, 2011 at 9:43 PM, Kukjin Kim <kgene.kim@samsung.com> wrote:
> []
> > +static void __init set_volt_table(void)
> > +{
> > +       unsigned int tmp, i, asv_group = 0;
> > +
> > +       tmp = __raw_readl(S5P_INFORM2);
> 
> As I've mentioned in the ASV patch thread, do we really need to use an
> INFORM register simply to save the id of supported voltage ranges?
> 
> Why aren't we using an extern variable here? For example, "extern int
> asv_group_id;" and define it at "asv.h" or somewhere else.
> 
> At reboot, we are going to init ASV driver and will get the ASV value
> again; thus, we don't need to use such a preserving register anyway.
> At suspend/resume, the value in RAM does not disappear and the IPL
> does not care this value; thus, it is meaningless to use INFORM2 for
> this value.
> 
ASV feature had been implemented in bootloader hence inform register was
used to return the result value to cpufreq driver. If there is no problem to
use the inform register why don't you keep this manner.

(snip)

Thanks.

Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.

  reply	other threads:[~2011-11-05  1:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-02 12:43 [PATCH 5/5] EXYNOS4210: Add support ASV feature Kukjin Kim
2011-11-03  5:11 ` MyungJoo Ham
2011-11-05  1:25   ` Kukjin Kim [this message]
2011-11-07  4:23     ` [PATCH 5/5] [CPUFREQ] " MyungJoo Ham

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='02e001cc9b59$d09ff400$71dfdc00$%kim@samsung.com' \
    --to=kgene.kim@samsung.com \
    --cc=cpufreq@vger.kernel.org \
    --cc=davej@redhat.com \
    --cc=jc.lee@samsung.com \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=myungjoo.ham@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox