16:59 <ecdhe> I just tested 5.13-rc6 (both the device tree and the kernel in parity.) I have the same earlycon boot output as before, and nothing post earlycon.

17:22 <ecdhe> NishanthMenon: I also tried the zImage and .dtb from linux-ti-staging and there was no earlycon output at all (must not be enabled by default and my .bbappend that adds a defconfig to enable it didn't match that older version's recipe.)

17:23 <ecdhe> NishanthMenon: * I also tried the zImage and .dtb from linux-ti-staging ** v4.19

17:23 <ecdhe> So I'm unable to boot with either 4.19 or 5.13-rc6 when kernel and dtb are kept in parity

17:24 <ecdhe> Will try 5.10 before I quit (though I think this is the kernel/dtb pair I started with)

18:10 <ecdhe> Just attempted to boot the zImage and am3517-evm.dtb files from 5.10 and also 5.4. Same issue as 5.13-rc6: earlycon output shows ti_clk_get_reg_addr() errors but no boot.

18:38 <NishanthMenon> ecdhe, linux-staging with TI vendor kernel is NOT tested on omap3 or am3517 for sure. So, the best bet you'd have is upstream based kernels

18:39 <NishanthMenon> ecdhe, might be good to share the log in pastebin for 5.13-rcX kernel with list.

18:39 <NishanthMenon> ecdhe, linux-omap@vger.kernel.org <linux-omap@vger.kernel.org>

18:47 <ecdhe> NishanthMenon: I will consider that!

18:52 <ecdhe> kristo: some new information. I added printk() at the start of both omap2_clk_provider_init() and ti_clk_get_reg_addr(). From the earlycon output, it appears that omap2_clk_provider_init() is never called, which is exactly why ti_clk_get_reg_addr() is failing.

18:53 <Pali> NishanthMenon: Hi! I would like to ask if you know something about missing Appendix C in SPRUIL1 documentation (TI J721E CDNS).

18:54 <NishanthMenon> Pali, hehe.. sounds familiar topic

18:54 <NishanthMenon> i had'nt followed up after i filed the ticket. let me check

18:54 <ecdhe> kristo: I assume this means the am3517-evm device tree source is out of order.

18:55 <ecdhe> NishanthMenon: I joined the list. I need to characterize my issue a little more before I ask for help.

18:57 <NishanthMenon> Pali, i cant seem to find the ticket. let me try filing one again..

19:02 <Pali> ok! hopefully somebody find that missing Appendix

19:03 <NishanthMenon> Pali, Can you add a feedback on https://www.ti.com/feedbackform/techdocfeedback?litnum=SPRUIL1B&partnum=

19:04 <Pali> ok, I will try

19:04 <NishanthMenon> I filed an internal ticket J7APPS-2144 -> you could refer to that as well.

19:08 <NishanthMenon> Pali, the difference is this: when you use the ti.com feedback -> it gets tracked at a TI corporate level. when I file a ticket, it is at the tech docs team level.. :D

19:09 <NishanthMenon> they can ignore me, but they wont be able to ignore you :D

19:18 <Pali> So lets see :-) I have filled that "corporate level form"

19:18 <Pali> And I find out that there is also reference to missing Appendix B from PCIe section... so not only Appendix C is missing

19:42 <NishanthMenon> Pali, ouch