mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: MyungJoo Ham <myungjoo.ham@samsung.com>
To: 최찬우 <cw00.choi@samsung.com>
Cc: "kgene@kernel.org" <kgene@kernel.org>,
	박경민 <kyungmin.park@samsung.com>,
	"rafael.j.wysocki@intel.com" <rafael.j.wysocki@intel.com>,
	"mark.rutland@arm.com" <mark.rutland@arm.com>,
	"ABHILASH KESAVAN" <a.kesavan@samsung.com>,
	"tomasz.figa@gmail.com" <tomasz.figa@gmail.com>,
	"Krzysztof Kozlowski" <k.kozlowski@samsung.com>,
	"Bartlomiej Zolnierkiewicz" <b.zolnierkie@samsung.com>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	대인기 <inki.dae@samsung.com>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-samsung-soc@vger.kernel.org"
	<linux-samsung-soc@vger.kernel.org>
Subject: Re: Re: [PATCHv3 1/8] devfreq: exynos: Add generic exynos memory bus frequency driver
Date: Tue, 13 Jan 2015 09:07:21 +0000 (GMT)	[thread overview]
Message-ID: <2009992739.970611421140038667.JavaMail.weblogic@epmlwas05d> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 2867 bytes --]

>  
> Dear Myungjoo,
>
>On 01/13/2015 05:42 PM, MyungJoo Ham wrote:
>>>   
>>>  This patch adds the generic exynos bus frequency driver for memory bus
>>> with DEVFREQ framework. The Samsung Exynos SoCs have the common architecture
>>> for memory bus between DRAM memory and MMC/sub IP in SoC. This driver can
>>> support the memory bus frequency driver for Exynos SoCs.
>>>
>>> Each memory bus block has a clock for memory bus speed and frequency
>>> table which is changed according to the utilization of memory bus on runtime.
>>> And then each memory bus group has the one more memory bus blocks and
>>> OPP table (including frequency and voltage), regulator, devfreq-event
>>> devices.
>>>
>>> There are a little difference about the number of memory bus because each Exynos
>>> SoC have the different sub-IP and different memory bus speed. In spite of this
>>> difference among Exynos SoCs, we can support almost Exynos SoC by adding
>>> unique data of memory bus to devicetree file.
>>>
>>> Cc: Myungjoo Ham <myungjoo.ham@samsung.com>
>>> Cc: Kyungmin Park <kyungmin.park@samsung.com>
>>> Cc: Kukjin Kim <kgene@kernel.org>
>>> Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
>>> ---
>>>  drivers/devfreq/Kconfig          |  15 +
>>>  drivers/devfreq/Makefile         |   1 +
>>>  drivers/devfreq/exynos-busfreq.c | 589 +++++++++++++++++++++++++++++++++++++++
>>>  3 files changed, 605 insertions(+)
>>>  create mode 100644 drivers/devfreq/exynos-busfreq.c
>> 
>> Exynos drivers are located at drivers/devfreq/exynos/
>> Please relocate/rename exynos-busfreq.c
>
>OK. I'll move it at drivers/devfreq/exynos directory.
>Do you prefer 'exynos-bus.c' instead of 'exynos-busfreq.c'?
>If you reply, I'll change it.

exynos-bus looks more pretty :)

>
>> 
>> []
>> 
>>> diff --git a/drivers/devfreq/exynos-busfreq.c b/drivers/devfreq/exynos-busfreq.c
>>> new file mode 100644
>>> index 0000000..b180f43
>>> --- /dev/null
>>> +++ b/drivers/devfreq/exynos-busfreq.c
>> 
>> []
>> 
>>> +
>>> +#define BUS_SATURATION_RATIO	40
>> 
>> In order to be a common driver, this should be tunable.
>> 
>> Because .dts is supposed to have hardware configuration only,
>> you may keep a table of { chip-name, saturation ratio} in this
>> driver and look up the saturation ratio based on the chip-name.
>
>OK, I'll add new property for saturation_ratio.
>
>I'll implement to use default saturation_ratio value ,
>if dt node don't include saturation_ratio property.

Yes. I didn't talk with DT maintainers and I do not have much
experience with DT; however, it appears that such values are not
recommended to be in DTS files and this value is determined by
the SoC model number without complications in the driver file.

ÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a­¢f£¢·hšïêÿ‘êçz_è®\x03(­éšŽŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨è­Ú&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥

             reply	other threads:[~2015-01-13  9:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-13  9:07 MyungJoo Ham [this message]
2015-01-13 10:29 ` Chanwoo Choi

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=2009992739.970611421140038667.JavaMail.weblogic@epmlwas05d \
    --to=myungjoo.ham@samsung.com \
    --cc=a.kesavan@samsung.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=cw00.choi@samsung.com \
    --cc=inki.dae@samsung.com \
    --cc=k.kozlowski@samsung.com \
    --cc=kgene@kernel.org \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=robh+dt@kernel.org \
    --cc=tomasz.figa@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

all inboxes | Powered by JetHome®