Thread (101 messages) 101 messages, 6 authors, 2013-11-06

Re: [PATCHv9 00/43] ARM: TI SoC clock DT conversion

From: Nishanth Menon <nm@ti.com>
Date: 2013-10-30 15:00:34
Also in: linux-arm-kernel, linux-omap

On 10/30/2013 03:23 AM, Tero Kristo wrote:
On 10/29/2013 06:19 PM, Nishanth Menon wrote:
quoted
On 10/25/2013 10:56 AM, Tero Kristo wrote:
<snip>
quoted
Testing done:
- omap3-beagle: boot + suspend/resume (ret + off)
- omap4-panda-es: boot + suspend/resume
- omap5-uevm: boot
- dra7-evm: boot
- am335x-bone: boot

Test branches available:

tree: https://github.com/t-kristo/linux-pm.git
<snip>
quoted
Fully functioning test branch: 3.12-rc6-dt-clks-v9
^^ I tested this branch (boot testing):
Beagle-XM: http://pastebin.com/50A1qtFq (crashes + clkdm issues, dpll5
failed to transition)
I just sent you a private email with a patch to try out, should fix the 
boot crash at least hopefully. Basically I forgot to convert one part of 
the kernel to the new regmap stuff for omap36xx.
it does bootup yes.
clkdm issues are caused by wrong data in omap_hwmod_3xxx_data.c, USB 
nodes are listing l3_init_clkdm for them, but this only exists on 
omap4+. Seems like some copy paste bug introduced by someone.

dpll5 part I am not too sure, can you check if the same happens with 
non-dt boot?
no-dt: http://pastebin.com/bYP9fTzH
dt: http://pastebin.com/xHup4L9Y

dpll5 warning seems to be only in dt-boot?
quoted
Panda-ES: http://pastebin.com/dWMp7D1z (bandgap_fclk not found)
OMAP5-UEVM: http://pastebin.com/pHEx6Yzg (omap-gpmc 50000000.gpmc:
error: clk_get)
Again, I don't think this is related to this series, but rather to 
missing/wrong hwmod data.
seems the bandgap_fclk stuff is generated from
drivers/thermal/ti-soc-thermal/omap4-thermal-data.c

anyways..
-Tero
quoted
DRA7-EVM: http://pastebin.com/uYNQ6Sss
BeagleBone-Black: http://pastebin.com/biGXS2vi
AM335x-evm: http://pastebin.com/K7qwJpCb
Btw, I also noticed the following section mimatches:
WARNING: vmlinux.o(.text+0x2abd4): Section mismatch in reference from
the function prcm_probe() to the (unknown reference) .init.data:(unknown)
The function prcm_probe() references
the (unknown reference) __initdata (unknown).
This is often because prcm_probe lacks a __initdata
annotation or the annotation of (unknown) is wrong.

WARNING: vmlinux.o(.data+0x3e30): Section mismatch in reference from
the variable prcm_driver to the (unknown reference) .init.data:(unknown)
The variable prcm_driver references
the (unknown reference) __initdata (unknown)
If the reference is valid then annotate the
variable with __init* or __refdata (see linux/init.h) or name the
variable:
*_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console


-- 
Regards,
Nishanth Menon
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help