NishanthMenon changed the topic of #linux-ti to: Linux development for TI SoCs | Logs: https://libera.irclog.whitequark.org/linux-ti/| paste logs in https://pastebin.ubuntu.com/ | Let it rock! Vendor SDK/kernel: Also see e2e.ti.com
ungeskriptet has quit [Remote host closed the connection]
florian_kc has quit [Ping timeout: 260 seconds]
ungeskriptet has joined #linux-ti
florian_kc has joined #linux-ti
cbeznea has joined #linux-ti
ikarso has joined #linux-ti
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #linux-ti
florian_kc has quit [Ping timeout: 272 seconds]
florian has joined #linux-ti
tlwoerner_ has joined #linux-ti
tlwoerner has quit [Ping timeout: 260 seconds]
goliath has joined #linux-ti
vigneshr has joined #linux-ti
<mwalle> NishanthMenon: did you see my mail regarding the assigned-clocks property? I don't think that is the culprit.
<NishanthMenon> mwalle: yes - tifs firmware will report 0 clk till the IP is activated
<mwalle> NishanthMenon: till the clock is enabled. but the real problem is caching (or rather when linux is caching the value) in linux
<mwalle> set_clock will just work fine. it's the TIFS will just mask the clock frequency (which is probably a stuid thing to do :o)
<mwalle> but that's another topic ;)
<mwalle> NishanthMenon: in short, I don't think the workaround i've posted (and that is in OOT driver) is correct
<mwalle> It looks like the clock driver has to be fixed
<NishanthMenon> vigneshr: ^^ can one of our power people look at this?
<mwalle> Though I don't have an idea right now how to do it. Except the NO_CACHING flag. Not sure how expensive that is, because it will propbably affect any clock
<NishanthMenon> mwalle: I suspect it might be expensive
<mwalle> NishanthMenon: I don't have any clue how linux is communicating with TIFS ;)
<NishanthMenon> From internal diagram (been a few years.. but i think this is till mostly valid.. reset - i think goes through psci now) https://usercontent.irccloud-cdn.com/file/AMmj4paT/image.png
<mwalle> NishanthMenon: For an outsider, thats rather hard to read. But apparently it goes through some kind of hardware mailbox between the cpu cores
<mwalle> also I assume "Framework IRQDomain" and genpd etc are the linux subsyss
<NishanthMenon> correct - it is a mailbox (a bit advanced version with DoS protection) that is used to communicate with Device manager for services. and yes, the CCF etc are linux frameworks
<NishanthMenon> this is more less the same if you see other protocols like scmi etc.. (sigh.. wish scmi was a little more scalable and safety concious, we would have switched to that)
<mwalle> Did you experience failures with TIs mails delivery system? I just got "The recipient's mailbox is full and can't accept messages now. Please try resending your message later". Quite funny :o
<mwalle> (Jayesh mailbox)
<mwalle> I also like how i get the mangled (internal) mail attached to the report *gg*
<NishanthMenon> mwalle: Jayesh is no longer with TI
<NishanthMenon> they do leave the mailbox active for some reason - i think it does get cleaned up later.. but it is irritating..
<mwalle> NishanthMenon: ok
florian_kc has joined #linux-ti
mripard has quit [Quit: WeeChat 4.7.0]
florian has quit [Quit: Ex-Chat]
florian_kc has quit [Ping timeout: 258 seconds]
goliath has quit [Quit: SIGSEGV]
florian has joined #linux-ti
goliath has joined #linux-ti
florian has quit [Ping timeout: 248 seconds]
florian has joined #linux-ti
ikarso has quit [Quit: Connection closed for inactivity]
ikarso has joined #linux-ti
cbeznea has quit [Ping timeout: 256 seconds]
goliath has quit [Quit: SIGSEGV]
tlwoerner_ has quit [Ping timeout: 256 seconds]
tlwoerner has joined #linux-ti
goliath has joined #linux-ti