From: Tony Lindgren <tony@atomide.com>
To: Igor Grinberg <grinberg@compulab.co.il>
Cc: Kevin Hilman <khilman@ti.com>, Paul Walmsley <paul@pwsan.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Jon Hunter <jon-hunter@ti.com>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
Vaibhav Hiremath <hvaibhav@ti.com>
Subject: Re: [PATCH v3 1/2] ARM: OMAP2+: timer: remove CONFIG_OMAP_32K_TIMER
Date: Wed, 21 Nov 2012 10:23:42 -0800 [thread overview]
Message-ID: <20121121182342.GX18567@atomide.com> (raw)
In-Reply-To: <1353395835-17390-1-git-send-email-grinberg@compulab.co.il>
* Igor Grinberg <grinberg@compulab.co.il> [121119 23:19]:
> CONFIG_OMAP_32K_TIMER is kind of standing on the single zImage way.
> Make OMAP2+ timer code independant from the CONFIG_OMAP_32K_TIMER
> setting.
> To remove the dependancy, several conversions/additions had to be done:
> 1) Timer initialization functions are named by the platform
> name and the clock source in use.
> This also makes it possible to define and use the GPTIMER as the
> clock source instead of the 32K timer on platforms that do not have
> the 32K timer ip block or the 32K timer is not wired on the board.
> Currently, the the timer is chosen in the machine_desc structure on
> per board basis. Later, DT should be used to choose the timer.
> 2) Settings under the CONFIG_OMAP_32K_TIMER option are used as defaults
> and those under !CONFIG_OMAP_32K_TIMER are removed.
> This removes the CONFIG_OMAP_32K_TIMER on OMAP2+ timer code.
> 3) Since we have all the timers defined inside machine_desc structure
> and we no longer need the fallback to gp_timer clock source in case
> 32k_timer clock source is unavailable (namely on AM33xx), we no
> longer need the #ifdef around omap2_sync32k_clocksource_init()
> function. Remove the #ifdef CONFIG_OMAP_32K_TIMER around the
> omap2_sync32k_clocksource_init() function.
Thanks for cleaning this up. Applying both into omap-for-v3.8/timer.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/2] ARM: OMAP2+: timer: remove CONFIG_OMAP_32K_TIMER
Date: Wed, 21 Nov 2012 10:23:42 -0800 [thread overview]
Message-ID: <20121121182342.GX18567@atomide.com> (raw)
In-Reply-To: <1353395835-17390-1-git-send-email-grinberg@compulab.co.il>
* Igor Grinberg <grinberg@compulab.co.il> [121119 23:19]:
> CONFIG_OMAP_32K_TIMER is kind of standing on the single zImage way.
> Make OMAP2+ timer code independant from the CONFIG_OMAP_32K_TIMER
> setting.
> To remove the dependancy, several conversions/additions had to be done:
> 1) Timer initialization functions are named by the platform
> name and the clock source in use.
> This also makes it possible to define and use the GPTIMER as the
> clock source instead of the 32K timer on platforms that do not have
> the 32K timer ip block or the 32K timer is not wired on the board.
> Currently, the the timer is chosen in the machine_desc structure on
> per board basis. Later, DT should be used to choose the timer.
> 2) Settings under the CONFIG_OMAP_32K_TIMER option are used as defaults
> and those under !CONFIG_OMAP_32K_TIMER are removed.
> This removes the CONFIG_OMAP_32K_TIMER on OMAP2+ timer code.
> 3) Since we have all the timers defined inside machine_desc structure
> and we no longer need the fallback to gp_timer clock source in case
> 32k_timer clock source is unavailable (namely on AM33xx), we no
> longer need the #ifdef around omap2_sync32k_clocksource_init()
> function. Remove the #ifdef CONFIG_OMAP_32K_TIMER around the
> omap2_sync32k_clocksource_init() function.
Thanks for cleaning this up. Applying both into omap-for-v3.8/timer.
Regards,
Tony
next prev parent reply other threads:[~2012-11-21 18:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-18 15:06 [PATCH v2 1/2] ARM: OMAP2+: timer: remove CONFIG_OMAP_32K_TIMER Igor Grinberg
2012-11-18 15:06 ` Igor Grinberg
2012-11-18 15:06 ` [PATCH 2/2] ARM: OMAP3: cm-t3517: use GPTIMER for system clock Igor Grinberg
2012-11-18 15:06 ` Igor Grinberg
2012-11-20 7:17 ` [PATCH v3 1/2] ARM: OMAP2+: timer: remove CONFIG_OMAP_32K_TIMER Igor Grinberg
2012-11-20 7:17 ` Igor Grinberg
2012-11-21 18:23 ` Tony Lindgren [this message]
2012-11-21 18:23 ` Tony Lindgren
2012-11-19 10:42 ` [PATCH v2 " Santosh Shilimkar
2012-11-19 10:42 ` Santosh Shilimkar
2012-11-19 16:27 ` Jon Hunter
2012-11-19 16:27 ` Jon Hunter
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=20121121182342.GX18567@atomide.com \
--to=tony@atomide.com \
--cc=grinberg@compulab.co.il \
--cc=hvaibhav@ti.com \
--cc=jon-hunter@ti.com \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=santosh.shilimkar@ti.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.