From: Kevin Hilman <khilman@ti.com>
To: Tero Kristo <t-kristo@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCHv3 09/11] omap4: twl: added pmic startup / shutdown times
Date: Fri, 04 Nov 2011 14:21:01 -0700 [thread overview]
Message-ID: <877h3f7feq.fsf@ti.com> (raw)
In-Reply-To: <1317835031-8201-10-git-send-email-t-kristo@ti.com> (Tero Kristo's message of "Wed, 5 Oct 2011 20:17:09 +0300")
Tero Kristo <t-kristo@ti.com> writes:
> Signed-off-by: Tero Kristo <t-kristo@ti.com>
Missing descriptive changelog.
> ---
> arch/arm/mach-omap2/omap_twl.c | 17 +++++++++++++++++
> 1 files changed, 17 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/omap_twl.c b/arch/arm/mach-omap2/omap_twl.c
> index 62ed050..c095cf2 100644
> --- a/arch/arm/mach-omap2/omap_twl.c
> +++ b/arch/arm/mach-omap2/omap_twl.c
> @@ -55,6 +55,13 @@ static bool __initdata twl_sr_enable_autoinit;
> #define REG_SMPS_OFFSET 0xE0
> #define SMARTREFLEX_ENABLE BIT(3)
>
> +struct twl_lp_description {
> + u32 osc_shut_time;
> + u32 osc_start_time;
These are unused.
Also, how are oscillator setup/shutdown times related to the PMIC?
> + u32 pmic_shut_time;
> + u32 pmic_start_time;
> +};
> +
> static unsigned long twl4030_vsel_to_uv(const u8 vsel)
> {
> return (((vsel * 125) + 6000)) * 100;
> @@ -220,9 +227,15 @@ static struct omap_voltdm_pmic omap4_core_pmic = {
> .uv_to_vsel = twl6030_uv_to_vsel,
> };
>
> +static struct twl_lp_description omap4_pmic_lp_desc = {
> + .pmic_shut_time = 500,
> + .pmic_start_time = 500,
> +};
> +
> int __init omap4_twl_init(void)
> {
> struct voltagedomain *voltdm;
> + struct twl_lp_description *desc;
>
> if (!cpu_is_omap44xx())
> return -ENODEV;
> @@ -236,6 +249,10 @@ int __init omap4_twl_init(void)
> voltdm = voltdm_lookup("core");
> omap_voltage_register_pmic(voltdm, &omap4_core_pmic);
>
> + desc = &omap4_pmic_lp_desc;
> +
> + omap_pm_set_pmic_lp_time(desc->pmic_start_time, desc->pmic_shut_time);
> +
> return 0;
> }
See comment on 5/11. IMO, the PMIC timings should just be going into
omap_voltdm_pmic along with slew_rate, step_size etc. I don't follow
why we need a different mechanism to customize these timings that is
different from the rest of the PMIC settings.
Kevin
next prev parent reply other threads:[~2011-11-04 21:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 17:17 [PATCHv3 00/11] voltage domain cleanup Tero Kristo
2011-10-05 17:17 ` [PATCHv3 01/11] OMAP3+: PM: VP: use uV for max and min voltage limits Tero Kristo
2011-10-05 17:17 ` [PATCHv3 02/11] omap: voltage: add definitions for omap_vp_param and omap_vc_param Tero Kristo
2011-10-05 17:17 ` [PATCHv3 03/11] omap3: add vp and vc parameter data Tero Kristo
2011-11-04 20:22 ` Kevin Hilman
2011-10-05 17:17 ` [PATCHv3 04/11] omap4: " Tero Kristo
2011-11-04 20:22 ` Kevin Hilman
2011-10-05 17:17 ` [PATCHv3 05/11] OMAP2+: PM: provide mechanism to describe overall behavior of osc and PMIC Tero Kristo
2011-11-04 21:02 ` Kevin Hilman
2011-10-05 17:17 ` [PATCHv3 06/11] omap3+: vc: use new vc_params and vp_params in parameter calculations Tero Kristo
2011-11-04 21:11 ` Kevin Hilman
2011-10-05 17:17 ` [PATCHv3 07/11] omap3+: vp: use new vp_params for calculating vddmin and vddmax Tero Kristo
2011-11-04 21:13 ` Kevin Hilman
2011-10-05 17:17 ` [PATCHv3 08/11] omap3+: voltage: remove obsolete parameters Tero Kristo
2011-11-04 21:17 ` Kevin Hilman
2011-10-05 17:17 ` [PATCHv3 09/11] omap4: twl: added pmic startup / shutdown times Tero Kristo
2011-11-04 21:21 ` Kevin Hilman [this message]
2011-11-04 21:21 ` Kevin Hilman
2011-10-05 17:17 ` [PATCHv3 10/11] omap3+: use lp params for calculating clock setup times Tero Kristo
2011-11-04 21:38 ` Kevin Hilman
2011-11-15 17:22 ` Tero Kristo
2011-11-17 0:10 ` Kevin Hilman
2011-10-05 17:17 ` [PATCHv3 11/11] omap4: use lp params for calculating pmic " Tero Kristo
2011-11-04 20:49 ` Kevin Hilman
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=877h3f7feq.fsf@ti.com \
--to=khilman@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=t-kristo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox