All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Koen Kooi <k.kooi@student.utwente.nl>
Cc: linux-omap@vger.kernel.org
Subject: Re: [beagleboard] Re: TWL4030 intermittent freakout on boot
Date: Mon, 12 May 2008 09:10:28 -0700	[thread overview]
Message-ID: <20080512161027.GB28999@atomide.com> (raw)
In-Reply-To: <D7C4A9C8-893A-4E80-AC68-D885D31A7397@student.utwente.nl>

* Koen Kooi <k.kooi@student.utwente.nl> [080510 02:43]:
> 
> Op 9 mei 2008, om 23:36 heeft Tony Lindgren het volgende geschreven:
> > * Dirk Behme <dirk.behme@googlemail.com> [080509 11:08]:
> >> Tony Lindgren wrote:
> >>>
> >> http://source.mvista.com/git/?p=linux-omap-2.6.git;a=commitdiff;h=0d81cf7e804c529c58d3054c1b9bdb7b3f1dec5d
> >>
> >> I don't know OMAP3 good enough yet, but which clock should we use on
> >> OMAP3 here?
> >
> > It should be osc_sys_ck for 34xx.
> >
> >> Does it make sense to use osc_ck for OMAP3 instead of osc_sys_ck,  
> >> too?
> >>
> >> E.g something like
> >>
> >> ...
> >> if (cpu_is_omap2430() || cpu_is_omap34xx())
> >>  osc = clk_get(NULL, "osc_ck");
> >> else
> >>  osc = clk_get(NULL, "osc_sys_ck");
> >> ...
> >
> > There's no osc_ck in clock34xx.h.
> 
> Does this patch make sense for omap3?
> 
> --- a/arch/arm/mach-omap2/pm.c
> +++ b/arch/arm/mach-omap2/pm.c
> @@ -779,7 +779,11 @@ int __init omap2_pm_init(void)
>          l = __raw_readl(OMAP24XX_PRCM_REVISION);
>          printk(KERN_INFO "PRCM revision %d.%d\n", (l >> 4) & 0x0f, l  
> & 0x0f);
> 
> -       osc_ck = clk_get(NULL, "osc_ck");
> +       if (cpu_is_omap2430() )
> +               osc_ck = clk_get(NULL, "osc_ck");
> +       else
> +               osc_ck = clk_get(NULL, "osc_sys_ck");
> +
>          if (IS_ERR(osc_ck)) {
>                  printk(KERN_ERR "could not get osc_ck\n");
>                  return -ENODEV;
> 
> 

Well it make sense, but does not alone help much. I think there will
be some 34xx PM patches hitting the list soonish.

Tony

  reply	other threads:[~2008-05-12 16:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-08 18:13 TWL4030 intermittent freakout on boot Paul Walmsley
2008-05-08 18:20 ` Koen Kooi
2008-05-08 18:28   ` Tony Lindgren
2008-05-08 18:33     ` Paul Walmsley
2008-05-08 18:42       ` Tony Lindgren
2008-05-09 18:08     ` [beagleboard] " Dirk Behme
2008-05-09 21:36       ` Tony Lindgren
2008-05-09 23:11         ` Steve Sakoman
2008-05-10  9:37           ` Dirk Behme
2008-05-10 13:42             ` Steve Sakoman
2008-05-10 14:57               ` Woodruff, Richard
2008-05-10 15:16                 ` Koen Kooi
2008-05-10  9:33         ` Koen Kooi
2008-05-12 16:10           ` Tony Lindgren [this message]
2008-05-12 16:17             ` Koen Kooi

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=20080512161027.GB28999@atomide.com \
    --to=tony@atomide.com \
    --cc=k.kooi@student.utwente.nl \
    --cc=linux-omap@vger.kernel.org \
    /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.