From: Tomasz Figa <t.figa@samsung.com>
To: Naveen Krishna Chatradhi <ch.naveen@samsung.com>, wsa@the-dreams.de
Cc: linux-i2c@vger.kernel.org, sjg@chromium.org,
linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
ben-linux@fluff.org, grant.likely@secretlab.ca,
broonie@kernel.org, dianders@chromium.org, cpgs@samsung.com
Subject: Re: [PATCH v4] i2c: s3c2410: dont need CPU_FREQ transitions for exynos series
Date: Mon, 09 Dec 2013 17:09:19 +0100 [thread overview]
Message-ID: <1750845.YHGrteBMYZ@amdc1227> (raw)
In-Reply-To: <1385439767-18586-1-git-send-email-ch.naveen@samsung.com>
Hi Naveen,
On Tuesday 26 of November 2013 09:52:46 Naveen Krishna Chatradhi wrote:
> For Exynos4 and Exynos5 SoCs from Samsung the i2c clock is based
> on a fixed 66 MHz peripheral clock, and therefore is completely
> independent of the cpu frequency.
> Thus, registering for a CPU freq notifier is very wasteful.
>
> This patch modifes the code such that, i2c bus registers to
> cpu_freq_transition only if CONFIG_CPU_FREQ_S3C24XX is enabled.
>
> This change should save a bunch of cpufreq transitions calls
> which does not apply to exynos SoCs.
>
> Signed-off-by: Naveen Krishna Chatradhi <ch.naveen@samsung.com>
> Acked-by: Kyungmin Park <kyungmin.park@samsung.com>
> Reviewed-by: Doug Anderson <dianders@chromium.org>
> ---
> Changes since v3:
> As per discussion at https://patchwork.kernel.org/patch/3235091/
> Post f023f8dd59 commit we should be using
> ARM_S3C24XX_CPUFREQ instead of CPU_FREQ_S3C24XX
>
> upstrea linux kernel and linuxsamsung already has the commit
> f023f8dd59. Hence, rebasing the patch.
>
> drivers/i2c/busses/i2c-s3c2410.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Reviewed-by: Tomasz Figa <t.figa@samsung.com>
Wolfram, are you okay with this patch?
Best regards,
Tomasz
next prev parent reply other threads:[~2013-12-09 16:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 11:26 [PATCH] i2c: s3c2410: dont need CPU_FREQ transitions for exynos series Naveen Krishna Chatradhi
2013-10-12 2:22 ` Tomasz Figa
2013-10-12 2:28 ` Tomasz Figa
2013-10-12 5:42 ` Tomasz Figa
2013-10-12 6:36 ` Naveen Krishna Ch
2013-10-15 6:23 ` [PATCH v2] " Naveen Krishna Chatradhi
2013-10-15 6:56 ` Kyungmin Park
2013-10-15 15:38 ` Doug Anderson
2013-11-19 6:18 ` [PATCH v3] " Naveen Krishna Chatradhi
2013-11-25 23:41 ` Doug Anderson
2013-11-26 4:07 ` Naveen Krishna Ch
2013-11-26 4:22 ` [PATCH v4] " Naveen Krishna Chatradhi
2013-12-09 16:09 ` Tomasz Figa [this message]
2014-01-03 16:23 ` Wolfram Sang
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=1750845.YHGrteBMYZ@amdc1227 \
--to=t.figa@samsung.com \
--cc=ben-linux@fluff.org \
--cc=broonie@kernel.org \
--cc=ch.naveen@samsung.com \
--cc=cpgs@samsung.com \
--cc=dianders@chromium.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=sjg@chromium.org \
--cc=wsa@the-dreams.de \
/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;
as well as URLs for NNTP newsgroup(s).