All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sylwester Nawrocki <snjw23@gmail.com>
To: Thomas Abraham <thomas.ab@samsung.com>
Cc: linux-samsung-soc@vger.kernel.org, kgene.kim@samsung.com,
	ben-linux@fluff.org
Subject: Re: [PATCH 5/6] ARM: SAMSUNG: Add clkdev support for exynos4
Date: Sat, 19 Mar 2011 13:02:23 +0100	[thread overview]
Message-ID: <4D849B4F.8020401@gmail.com> (raw)
In-Reply-To: <1300521019-13612-6-git-send-email-thomas.ab@samsung.com>

Hi Thomas,

On 03/19/2011 08:50 AM, Thomas Abraham wrote:
> Add clkdev support for Samsung's exynos4 platforms.
>
> Cc: Ben Dooks<ben-linux@fluff.org>
> Signed-off-by: Thomas Abraham<thomas.ab@samsung.com>
> ---
>   arch/arm/mach-exynos4/Kconfig               |    1 +
>   arch/arm/mach-exynos4/clock.c               |   57 +++++++++++++++++++++++++++
>   arch/arm/mach-exynos4/include/mach/clkdev.h |    7 +++
>   arch/arm/mach-exynos4/time.c                |    2 +
>   arch/arm/plat-samsung/pwm-clock.c           |   10 +++++
>   5 files changed, 77 insertions(+), 0 deletions(-)
>   create mode 100644 arch/arm/mach-exynos4/include/mach/clkdev.h
>
> diff --git a/arch/arm/mach-exynos4/Kconfig b/arch/arm/mach-exynos4/Kconfig
> index a021b52..58451c3 100644
> --- a/arch/arm/mach-exynos4/Kconfig
> +++ b/arch/arm/mach-exynos4/Kconfig
> @@ -110,6 +110,7 @@ config MACH_SMDKC210
>   config MACH_SMDKV310
>   	bool "SMDKV310"
>   	select CPU_EXYNOS4210
> +	select CLKDEV_LOOKUP
>   	select S3C_DEV_RTC
>   	select S3C_DEV_WDT
>   	select S3C_DEV_I2C1
> diff --git a/arch/arm/mach-exynos4/clock.c b/arch/arm/mach-exynos4/clock.c
> index 871f9d5..0b46326 100644
> --- a/arch/arm/mach-exynos4/clock.c
> +++ b/arch/arm/mach-exynos4/clock.c
> @@ -404,41 +404,49 @@ static struct clk init_clocks_off[] = {
>   		.ctrlbit	= (1<<24),
...
>   	}, {
>   		.name		= "fimc",
> +		.devname	= "s5p-fimc.0",

This clock belongs to s5p-fimc driver however for exynos4 the platform
device name is "exynos4-fimc". So the above line needs to be:

+		.devname	= "exynos4-fimc.0",

>   		.id		= 0,
>   		.enable		= exynos4_clk_ip_cam_ctrl,
>   		.ctrlbit	= (1<<  0),
>   	}, {
>   		.name		= "fimc",
> +		.devname	= "s5p-fimc.1",

Ditto.

>   		.id		= 1,
>   		.enable		= exynos4_clk_ip_cam_ctrl,
>   		.ctrlbit	= (1<<  1),
>   	}, {
>   		.name		= "fimc",
> +		.devname	= "s5p-fimc.2",

Ditto.

>   		.id		= 2,
>   		.enable		= exynos4_clk_ip_cam_ctrl,
>   		.ctrlbit	= (1<<  2),
>   	}, {
>   		.name		= "fimc",
> +		.devname	= "s5p-fimc.3",

Ditto.

>   		.id		= 3,
>   		.enable		= exynos4_clk_ip_cam_ctrl,
>   		.ctrlbit	= (1<<  3),
>   	}, {
...
> @@ -909,6 +950,7 @@ static struct clksrc_clk clksrcs[] = {
>   	}, {
>   		.clk		= {
>   			.name		= "sclk_cam",
> +			.devname	= "s5pv310-fimc.0",

As s5pv310 has been renamed to exynos4 the above line should be:

+			.devname	= "exynos4-fimc.0",

In fact "sclk_cam" clocks are not really tied to any FIMC instance,
however IMHO keeping the current configuration is best thing to do
at this stage. I intend to add a platform device for a media device
driver which will integrate all FIMC entities and then assign both
sclk_cam clocks to that platform device.

>   			.id		= 0,
>   			.enable		= exynos4_clksrc_mask_cam_ctrl,
>   			.ctrlbit	= (1<<  16),
> @@ -919,6 +961,7 @@ static struct clksrc_clk clksrcs[] = {
>   	}, {
>   		.clk		= {
>   			.name		= "sclk_cam",
> +			.devname	= "s5pv310-fimc.1",

+			.devname	= "exynos4-fimc.1",

>   			.id		= 1,
>   			.enable		= exynos4_clksrc_mask_cam_ctrl,
>   			.ctrlbit	= (1<<  20),
> @@ -929,6 +972,7 @@ static struct clksrc_clk clksrcs[] = {
>   	}, {
>   		.clk		= {
>   			.name		= "sclk_fimc",
> +			.devname	= "s5pv310-fimc.0",

+			.devname	= "exynos4-fimc.0",

I'm going to fix the name in the driver during a coming rc period.
This is were the driver name for exynos4 is being fixed up:
http://tinyurl.com/638a9og

>   			.id		= 0,
>   			.enable		= exynos4_clksrc_mask_cam_ctrl,
>   			.ctrlbit	= (1<<  0),
> @@ -939,6 +983,7 @@ static struct clksrc_clk clksrcs[] = {
>   	}, {
>   		.clk		= {
>   			.name		= "sclk_fimc",
> +			.devname	= "s5pv310-fimc.1",

Ditto.

>   			.id		= 1,
>   			.enable		= exynos4_clksrc_mask_cam_ctrl,
>   			.ctrlbit	= (1<<  4),
> @@ -949,6 +994,7 @@ static struct clksrc_clk clksrcs[] = {
>   	}, {
>   		.clk		= {
>   			.name		= "sclk_fimc",
> +			.devname	= "s5pv310-fimc.2",

Ditto.

>   			.id		= 2,
>   			.enable		= exynos4_clksrc_mask_cam_ctrl,
>   			.ctrlbit	= (1<<  8),
> @@ -959,6 +1005,7 @@ static struct clksrc_clk clksrcs[] = {
>   	}, {
>   		.clk		= {
>   			.name		= "sclk_fimc",
> +			.devname	= "s5pv310-fimc.3",

Ditto.

>   			.id		= 3,
>   			.enable		= exynos4_clksrc_mask_cam_ctrl,
>   			.ctrlbit	= (1<<  12),

--
Thanks,
Sylwester Nawrocki

  parent reply	other threads:[~2011-03-19 12:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-19  7:50 [PATCH 0/6] Prerequisite patches for device tree for Samsung's Exynos4 platform Thomas Abraham
2011-03-19  7:50 ` [PATCH 1/6] ARM: EXYNOS4: Fix addruart macro Thomas Abraham
2011-03-19  7:50 ` [PATCH 2/6] serial: samsung: Fix unintended usage of uart port 0 as console Thomas Abraham
2011-03-19  7:50 ` [PATCH 3/6] serial: s5pv210: Remove redundant console_initcall Thomas Abraham
2011-03-19  7:50 ` [PATCH 4/6] ARM: SAMSUNG: Add clkdev support Thomas Abraham
2011-03-19  7:50 ` [PATCH 5/6] ARM: SAMSUNG: Add clkdev support for exynos4 Thomas Abraham
2011-03-19  9:42   ` Seungwhan Youn
2011-03-19 12:02   ` Sylwester Nawrocki [this message]
2011-03-19  7:50 ` [PATCH 6/6] ARM: Remove clkdev.o build in arch/arm/common/Makefile Thomas Abraham
2011-03-25  8:35   ` Kukjin Kim
2011-03-25  8:35     ` 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=4D849B4F.8020401@gmail.com \
    --to=snjw23@gmail.com \
    --cc=ben-linux@fluff.org \
    --cc=kgene.kim@samsung.com \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=thomas.ab@samsung.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.