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
goliath has joined #linux-ti
ladis has joined #linux-ti
umbramalison has joined #linux-ti
umbramalison_alt has quit [Ping timeout: 272 seconds]
rob_w has joined #linux-ti
anshuld has quit [Quit: Connection closed for inactivity]
florian has joined #linux-ti
ladis has quit [Ping timeout: 265 seconds]
ladis has joined #linux-ti
rob_w has quit [Remote host closed the connection]
rob_w has joined #linux-ti
rob_w has quit [Ping timeout: 248 seconds]
rob_w has joined #linux-ti
florian_kc has joined #linux-ti
rob_w has quit [Ping timeout: 244 seconds]
dhruvag2000 has joined #linux-ti
<dhruvag2000> @pivi: The way we've been doing it in SDK by doing IRQ chaining has always been a bit hacky [1]. There's no plans ATM to upstream that hack. Why is it a hack? Well no padconfig interrupts are ever sent to the A53, directly or indirectly. So there's no clean way in linux to do IRQ chaining and configuring the wakeup. See [1] for further explanation. So, the approach that makes more sense is to support a wakeup pinctrl state.
<dhruvag2000> similar to how we've done it for https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/commit/drivers/net/can/m_can/m_can.c?h=ti-linux-6.12.y-cicd&id=e6aced8fa0f1dfdec3160a85f2a12708766fcefd&context=3&ignorews=0&dt=0 This will be required for any driver for eg. GPIO or UART that will be used indirectly to setup the wakeup pinctrl configuration. [1]
goliath has quit [Quit: SIGSEGV]
florian_kc has quit [Ping timeout: 276 seconds]
florian_kc has joined #linux-ti
goliath has joined #linux-ti
dhruvag2000 has quit [Quit: Connection closed for inactivity]