public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Steve Sakoman <sakoman@gmail.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH/RFC] ARM: OMAP: Initialize MADC clock divider and clock
Date: Wed, 3 Jun 2009 13:28:17 -0700	[thread overview]
Message-ID: <20090603202817.GH5026@atomide.com> (raw)
In-Reply-To: <5e088bd90906031310v6324b157k97d8ba6c71ea5c6f@mail.gmail.com>

* Steve Sakoman <sakoman@gmail.com> [090603 13:10]:
> Tony,
> 
> I noticed your comment requesting all twl4030 patches be submitted to
> mainline.  I assume this patch falls into that category too?

Yeah, we should try to make all the patches against mainline now.
 
> Also for those listening in -- no comments on this patch yet!  Does
> that mean it looks good?   ;-)

You should send it to:

$ grep -a7 "MULTIFUNCTION DEVICES" MAINTAINERS
P:      Samuel Ortiz
M:      sameo@linux.intel.com
L:      linux-kernel@vger.kernel.org
T:      git git://git.kernel.org/pub/scm/linux/kernel/git/sameo/mfd-2.6.git
S:      Supported
F:      drivers/mfd/

Tony
 
> Steve
> 
> On Sat, May 30, 2009 at 6:40 AM, Steve Sakoman <sakoman@gmail.com> wrote:
> > Though the comment in clocks_init claims to initialize the MADC
> > clocks, it wasn't actually being done.  This patch implements minimal
> > MADC clock initialization.
> >
> > Compile/run tested on Overo (prior to patch MADC access would always timeout)
> >
> > diff --git a/drivers/mfd/twl4030-core.c b/drivers/mfd/twl4030-core.c
> > index 769b34b..c5ca36d 100644
> > --- a/drivers/mfd/twl4030-core.c
> > +++ b/drivers/mfd/twl4030-core.c
> > @@ -159,6 +159,7 @@
> >
> >  /* Few power values */
> >  #define R_CFG_BOOT                     0x05
> > +#define R_GPBR1                                0x0C
> >  #define R_PROTECT_KEY                  0x0E
> >
> >  /* access control values for R_PROTECT_KEY */
> > @@ -166,6 +167,10 @@
> >  #define KEY_UNLOCK2                    0xec
> >  #define KEY_LOCK                       0x00
> >
> > +/* MADC clock values for R_GPBR1 */
> > +#define MADC_HFCLK_EN                  0x80
> > +#define DEFAULT_MADC_CLK_EN            0x10
> > +
> >  /* some fields in R_CFG_BOOT */
> >  #define HFCLK_FREQ_19p2_MHZ            (1 << 0)
> >  #define HFCLK_FREQ_26_MHZ              (2 << 0)
> > @@ -717,6 +722,11 @@ static void __init clocks_init(struct device *dev)
> >        ctrl |= HIGH_PERF_SQ;
> >        e |= unprotect_pm_master();
> >        /* effect->MADC+USB ck en */
> > +
> > +       if (twl_has_madc())
> > +               e |= twl4030_i2c_write_u8(TWL4030_MODULE_INTBR,
> > +                               MADC_HFCLK_EN | DEFAULT_MADC_CLK_EN, R_GPBR1);
> > +
> >        e |= twl4030_i2c_write_u8(TWL4030_MODULE_PM_MASTER, ctrl, R_CFG_BOOT);
> >        e |= protect_pm_master();
> >
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2009-06-03 20:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-30 13:40 [PATCH/RFC] ARM: OMAP: Initialize MADC clock divider and clock Steve Sakoman
2009-05-30 13:45 ` Steve Sakoman
2009-06-03 20:10 ` Steve Sakoman
2009-06-03 20:28   ` Tony Lindgren [this message]

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=20090603202817.GH5026@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=sakoman@gmail.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