From: Tony Lindgren <tony@atomide.com>
To: "Woodruff, Richard" <r-woodruff2@ti.com>
Cc: Linux-omap-open-source@linux.omap.com
Subject: Re: RMKs comments on latest OMAP upstream patches
Date: Sun, 23 Sep 2007 14:21:49 -0700 [thread overview]
Message-ID: <20070923212149.GB10076@atomide.com> (raw)
In-Reply-To: <3B6D69C3A9EBCA4BA5DA60D91302742901F3ED6C@dlee13.ent.ti.com>
* Woodruff, Richard <r-woodruff2@ti.com> [070921 01:31]:
> > > OMAP1:
> > > http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=4570/1
> > >
> > > OMAP2:
> > > http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=4571/1
Looks like Russell has applied these two patch series above!
> Hum, I should Russell's comment reference. Yes there is a clock register function, however, there is no, command to create a new node. Further you are not supposed to know what the node structure is. In the TI tree variant I did add a node create and destroy function. However, it does cheat and exports some parameters which imply internal knowledge of the clock structure.
>
> It would seem the best you could do was to pre-install some dummy nodes. However, you still need a way to fill in the function pointers... Again, need check his pointer.
For board specific GPIO clock control clk_register() with custom
enable/disable functions should work just fine though.
Tony
next prev parent reply other threads:[~2007-09-23 21:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-20 16:20 RMKs comments on latest OMAP upstream patches Dirk Behme
2007-09-21 1:59 ` Tony Lindgren
2007-09-21 8:31 ` Woodruff, Richard
2007-09-23 21:21 ` Tony Lindgren [this message]
2007-09-24 19:12 ` Dirk Behme
2007-10-16 18:35 ` Dirk Behme
2007-10-16 20:17 ` Tony Lindgren
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=20070923212149.GB10076@atomide.com \
--to=tony@atomide.com \
--cc=Linux-omap-open-source@linux.omap.com \
--cc=r-woodruff2@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