Skip to content

ARM: OMAP2+: clock code move under clk driver

Michael Turquette linux-arm-kernel linux-clk linux-omap 1 version New

Get series with b4
b4 am 20150603231136.6017.65683@quantum

Versions newest first

  1. v3 Latest0 of 27 patches 0 repliesNew

Patches in v3 No applies recorded yet

None of the 27 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v3 yet.

Read the v3 thread

Cover letter [PATCHv3 00/27] ARM: OMAP2+: clock code move under clk driver

Quoting Tero Kristo (2015-06-03 05:33:46)

Quoted 41 lines · Tony Lindgren
Quoted 40 lines · Tero Kristo
Quoted 27 lines · Felipe Balbi
Quoted 26 lines · Tony Lindgren
Quoted 14 lines · Tony Lindgren
Quoted 13 lines · Tero Kristo
Quoted 9 lines

Hi,

As requested, posting v3 with somewhat changed diff parameters and diffstat attached. Just some minor Makefile changes compared to v2, these were discussed under that set.

Set has been pushed to:
- tree: https://github.com/t-kristo/linux-pm.git
- branch: for-4.2/ti-clk-move

Looks like this causes a build error for at least omap2 only .config:

Quoted 7 lines
Quoted 7 lines

drivers/clk/ti/dpll3xxx.o:(.rodata+0x1c): multiple definition of `clkhwops_omap3_dpll' drivers/clk/ti/dpll.o:(.rodata+0x0): first defined here

You may want to create a file selecting ARCH_OMAP2PLUS=y, then point KCONFIG_ALLCONFIG to that file for make randconfig. Then just build randconfigs :) Usually the issues like this are exposed within few randconfig builds, some take longer if the options have dependencies.

alternatively, just clone the repository at [1] and use the example script provided in README.md.

Quoted 7 lines
Quoted 2 lines

[1] https://github.com/felipebalbi/omap-seeds

Ok, I pushed an updated branch named: for-4.2/ti-clk-move-v4

This definitely compiles with OMAP2 / OMAP3 / OMAP4 / OMAP5 / DRA7 / AM33xx / AM43xx only setups (tried it out.)

Thanks yeah seems to work for me now.

Regards,

Quoted 8 lines
Quoted 2 lines

Tony

Question to Mike / Stephen, any chance of getting this in during the 4.2 merge anymore seeing we are already at 4.1-rc6?

I can send a pull request if yes. Otherwise I just wait until we are past the next merge.

Hi Tero,

I'd like more time for any regressions this introduces to be fixed, so lets push back to next merge window. The always-wrong-but-never-by-much crystal ball[0] predicts June 14. This is less than two weeks away, so the wait should be short.

[0] http://phb-crystal-ball.org/

Thanks,
Mike

Quoted 2 lines

-Tero