Message ID | 20120504170533.GO4141@pengutronix.de |
---|---|
State | New |
Headers | show |
On Fri, May 04, 2012 at 07:05:33PM +0200, Sascha Hauer wrote: > Currently we are still missing the clk patches for next in -next. It > should be fine to have these in arm-soc since probably no non-arm > architecture will convert to the clock framework in the next two weeks. Actually I've a patch which I keep pushing to the x86 maintainers to enable the clock API there (ideally we'd enable it on all architectures that don't currently have one of their own straight off). > So Mike, please consider sending the following pull request to Arnd: Seconded! I'd also like to get the wm831x driver in there, I've not been looking at it since it doesn't seem sensible to put the effort in until we've got stuff flowing into -next.
On Fri, May 04, 2012 at 07:05:33PM +0200, Sascha Hauer wrote: > Erm, no, this is not a pull request, more a request for a pull request. > > Currently we are still missing the clk patches for next in -next. It > should be fine to have these in arm-soc since probably no non-arm > architecture will convert to the clock framework in the next two weeks. > > Then finally we could merge SoC clk code in the arm-soc tree. BTW there > are lready spear clk patches in the arm-soc tree which conflict with > Mikes branch so Viresh might have to fix them (maybe he sent the fixes > already to the list, can't remember) > > > So Mike, please consider sending the following pull request to Arnd: > And please do not forget to pick up the patch below, Mike. Sascha Hauer (1): clk: add a fixed factor clock Since Russell has published his clkdev branch, with above patch picked up on clk-next, I have everything ready to send my platform porting. Thanks, Shawn
On Sat, May 05, 2012 at 02:10:18PM +0800, Shawn Guo wrote: > And please do not forget to pick up the patch below, Mike. > > Sascha Hauer (1): > clk: add a fixed factor clock > > Since Russell has published his clkdev branch, with above patch picked > up on clk-next, I have everything ready to send my platform porting. > Mike, I haven't seen the following fixup being picked up. Can you please do? http://thread.gmane.org/gmane.linux.ports.arm.msm/2614/focus=2637
On Sat, May 5, 2012 at 2:23 AM, Shawn Guo <shawn.guo@linaro.org> wrote: > On Sat, May 05, 2012 at 02:10:18PM +0800, Shawn Guo wrote: >> And please do not forget to pick up the patch below, Mike. >> >> Sascha Hauer (1): >> clk: add a fixed factor clock >> >> Since Russell has published his clkdev branch, with above patch picked >> up on clk-next, I have everything ready to send my platform porting. >> > Mike, I haven't seen the following fixup being picked up. Can you > please do? > > http://thread.gmane.org/gmane.linux.ports.arm.msm/2614/focus=2637 Will do. Regards, Mike
On Fri, May 4, 2012 at 10:45 AM, Mark Brown <broonie@opensource.wolfsonmicro.com> wrote: > On Fri, May 04, 2012 at 07:05:33PM +0200, Sascha Hauer wrote: > I'd also like to get the wm831x driver in there, I've not been looking > at it since it doesn't seem sensible to put the effort in until we've > got stuff flowing into -next. One thing to think about is the fact that CONFIG_COMMON_CLK pulls in clkdev. x86 doesn't have an arch/x86/include/asm/clkdev.h last time I looked. Regards, Mike
On Sun, May 06, 2012 at 07:20:18PM -0700, Turquette, Mike wrote: > On Fri, May 4, 2012 at 10:45 AM, Mark Brown > > On Fri, May 04, 2012 at 07:05:33PM +0200, Sascha Hauer wrote: > > I'd also like to get the wm831x driver in there, I've not been looking > > at it since it doesn't seem sensible to put the effort in until we've > > got stuff flowing into -next. > One thing to think about is the fact that CONFIG_COMMON_CLK pulls in > clkdev. x86 doesn't have an arch/x86/include/asm/clkdev.h last time I > looked. Everything seemed to manage to build happily enough when I was testing, this is how I was build testing, though I'm not immediately sure why looking again. This does seem like we're stuck in the same failure that we're in with gpiolib, and obviously the -next issues get in the way too :(