From: Rajendra Nayak <rnayak@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org
Subject: RE: handling clock nodes with both parent and divider selection
Date: Wed, 2 Feb 2011 09:38:21 +0530 [thread overview]
Message-ID: <d1eefcbf311a0a741569c792c860d227@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1102010931530.16671@utopia.booyaka.com>
> -----Original Message-----
> From: Paul Walmsley [mailto:paul@pwsan.com]
> Sent: Tuesday, February 01, 2011 10:03 PM
> To: Rajendra Nayak
> Cc: linux-omap@vger.kernel.org
> Subject: RE: handling clock nodes with both parent and divider selection
>
> On Tue, 1 Feb 2011, Rajendra Nayak wrote:
>
> > > -----Original Message-----
> > > From: Paul Walmsley [mailto:paul@pwsan.com]
> > > Sent: Tuesday, February 01, 2011 4:43 AM
> >
> > > At some point in the future, hopefully we'll be able to split all of
the
> > > multiplexers and dividers into their own struct clks, or struct
> > omap_clks,
> > > or something, so we don't have to implement these hacks. As I
> > understand
> > > it, that would be closer to the actual hardware, anyway. The right
time
> > > to do that would be after the clktype conversion...
> >
> > Ok, I am not completely sure what clktype conversion means, but will
> > wait for it.
>
> I'd suggest not waiting for it, but implementing something now, similar
to
> OMAP3, if it won't be too big of a hack.
Yup, I will. I just meant to say will wait for your patches to see what
clktype conversion meant, since I did not know of it.
Did not mean to say will wait for it to add the divider control
for aux clks :)
>
>
> - Paul
prev parent reply other threads:[~2011-02-02 4:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 14:06 handling clock nodes with both parent and divider selection Rajendra Nayak
2011-01-31 23:12 ` Paul Walmsley
2011-02-01 11:28 ` Rajendra Nayak
2011-02-01 16:33 ` Paul Walmsley
2011-02-02 4:08 ` Rajendra Nayak [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=d1eefcbf311a0a741569c792c860d227@mail.gmail.com \
--to=rnayak@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.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