Linux Samsung SOC development
 help / color / mirror / Atom feed
From: Kukjin Kim <kgene.kim@samsung.com>
To: 'MyungJoo Ham' <myungjoo.ham@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org, ben-linux@fluff.org
Subject: RE: [PATCH 02/14] ARM: S5PV310: Removed unused clock
Date: Fri, 20 Aug 2010 16:10:01 +0900	[thread overview]
Message-ID: <00b201cb4036$b7e1c7b0$27a55710$%kim@samsung.com> (raw)
In-Reply-To: <AANLkTinjDBxahumErXmXXDW2FLxFi6oXpu-jZa+xzYhF@mail.gmail.com>

MyungJoo Ham wrote:
> 
> Hello,
> 
Hi :-)

> On Wed, Aug 18, 2010 at 11:01 PM, Kukjin Kim <kgene.kim@samsung.com> wrote:
> > This pach removed unused clock on S5PV310/S5PC210.
> >
> > Signed-off-by: Kukjin Kim <kgene.kim@samsung.com>
> 
> In this patch, you've removed corem0, corem1, cores, periph, atclk,
> and pclk_dbg, which are directly affected by cpu-freq drivers. As long
> as CPUFREQ uses clocks under 800MHz, corem0, corem1, cores, and
> periph's dividers should be updated and as long as CPUFREQ uses clocks
> over 800MHz, atclk and pclk_dbg's dividers should also be updated.
> Although in the cpu-freq patches of S5PV210, the cpu-freq driver did
> not use the clock framework and accessed clock registers directly, I
> thought cpu-freq should consider using the clock framework later as,
> sometimes, other drivers and modules are interested in the values
> related with this domain (e.g., for the stability issues,
> suspend-to-mem/disk may want to read and save the clock rates of CPU).
> 
> Do you think CPUFREQ should keep accessing the clock registers
> directly? or should start using clock frameworks later?
> 
> ps. If we are going to change the bus speed as well (as in S5PV210's
> 100MHz mode), we may need to access aclk_cored, aclk_corep, and
> aclk_acp as well.
> 

Basically, no need to control them when changed frequency because can be restored original value.
But I think need to check it again.

Thanks.

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

  reply	other threads:[~2010-08-20  7:09 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-18 14:01 [PATCH 00/14] ARM: S5PV310: Updates clock Kukjin Kim
2010-08-18 14:01 ` [PATCH 01/14] ARM: S5PV310: Adds clock addresses for S5PV310 Kukjin Kim
2010-08-18 14:01 ` [PATCH 02/14] ARM: S5PV310: Removed unused clock Kukjin Kim
2010-08-19  2:57   ` MyungJoo Ham
2010-08-20  7:10     ` Kukjin Kim [this message]
2010-08-18 14:01 ` [PATCH 03/14] ARM: S5PV310: Adds clkset_aclk for removing clkset_aclk_xxx Kukjin Kim
2010-08-18 14:01 ` [PATCH 04/14] ARM: S5PV310: Fix on PLL setting for S5PV310 Kukjin Kim
2010-08-18 14:01 ` [PATCH 05/14] ARM: S5PV310: Adds clk_sclk_usbphy0, _usbphy1, and _hdmiphy Kukjin Kim
2010-08-18 14:01 ` [PATCH 06/14] ARM: S5PV310: Should be clk_sclk_apll not clk_mout_apll Kukjin Kim
2010-08-18 14:01 ` [PATCH 07/14] ARM: S5PV310: Adds printing ACLK200, ACLK100, ACLK160 and ACLK133 Kukjin Kim
2010-08-18 14:01 ` [PATCH 08/14] ARM: S5PV310: Adds enable and ctrlbit for clk_vpllsrc Kukjin Kim
2010-08-18 14:01 ` [PATCH 09/14] ARM: S5PV310: Adds SDMMC clock for S5PV310 Kukjin Kim
2010-08-18 14:01 ` [PATCH 10/14] ARM: S5PV310: Adds uart clocks Kukjin Kim
2010-08-19  8:40   ` MyungJoo Ham
2010-08-20  6:58     ` Kukjin Kim
2010-08-18 14:01 ` [PATCH 11/14] ARM: S5PV310: Bug fix on uclk1 and sclk_pwm Kukjin Kim
2010-08-18 14:01 ` [PATCH 12/14] ARM: S5PV310: Add various clocks Kukjin Kim
2010-08-19  8:52   ` MyungJoo Ham
2010-08-20  7:00     ` Kukjin Kim
2010-08-18 14:01 ` [PATCH 13/14] ARM: S5PV310: Add video clocks Kukjin Kim
2010-08-19 10:04   ` MyungJoo Ham
2010-08-19 10:28     ` MyungJoo Ham
2010-08-20  7:35       ` Kukjin Kim
2010-08-18 14:01 ` [PATCH 14/14] ARM: S5PV310: Adds various special clocks Kukjin Kim
2010-08-23  2:05 ` [PATCH 00/14] ARM: S5PV310: Updates clock Kyungmin Park
2010-08-23  2:21   ` Kukjin Kim

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='00b201cb4036$b7e1c7b0$27a55710$%kim@samsung.com' \
    --to=kgene.kim@samsung.com \
    --cc=ben-linux@fluff.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --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