On Sun, Jul 13, 2008 at 02:23:17PM -0700, Andrew Morton wrote:That doesn't work. In this case, linux/clk.h _is_ the only source of the API. The API is just a defined set of functions. How an architecture or machine class implements it is at the discressiom of whoever's writing that code. The point being, that we have a fixed core API which drivers can use which is portable across different SoCs. However, there certainly are implementation specific issues which architecture code needs to know about - hence why the implementation has (until genclk) been left completely up to that code to decide and implement the interface. So, the only place for that documentation is the header file. Documenting an implementation will just confuse the issue and lead people into thinking that it somehow represents the way things should be done. Even genclk doesn't represent "The Way Things Should Be Done" - it's just yet another implementation of the interface. -- Russell King Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/ maintainer of: --
| Stephane Jourdois | Re: 2.6.21-rc4-mm1 [PATCH] init/missing_syscalls.h fix |
| David Brown | Re: Linux 2.6.21-rc2 |
| Andi Kleen | [PATCH] [1/12] x86: Work around mmio config space quirk on AMD Fam10h |
| david | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| David Miller | Re: [GIT]: Networking |
| David Woodhouse | Re: [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin" |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
git: | |
