Re: [PATCH v11 0/7] Introduction of PSCR Framework and Related Components
Oleksij Rempel <[email protected]> Thu, 2 Jul 2026 06:21:00 +0200
| Newsgroups | dev.linux.lists.chrome-platform,org.kernel.vger.linux-kernel,org.kernel.vger.linux-pm |
|---|---|
| Message-ID | <[email protected]> |
Hi Faruque, On Wed, Jul 01, 2026 at 06:26:37PM +0530, Faruque Ansari wrote: > Hi Oleksij, > > On 29-Jun-26 5:11 PM, Oleksij Rempel wrote: > > Hi Faruque, > Thank You for sharing your rational behind and idea behind this framework ! > IMO it would be better to have a single framework to represent all the > reboot reasons of a system and not just the reboot reasons caused because of > errors > Ex capturing reboot reasons like ota, bootloader,recovery etc ... currently > nvmem reboot driver does not expose a sysfs/ABI which user app can use to > infer reboot reason ... > Also, it would be extend this framework to also support firmware triggered > reboot reasons ... > Do you have any plan to extend this framework to support userspace triggered > reboot reasons as well like bootloader, recovery, ota etc ? > And also extend the framework to support vendor specific reboot reasons > which can be triggered by firmware ? I have nothing against it. My imagination was limited only by some of existing problems :) > We can co-work to extend this framework ? Sure. Should I put it somewhere on git, so you can try your changes on top of it? > On representating nvmem cell to the framework - if not DT what is your plan > to represent it ? > > How would framework discover the nvmem cell if its not DT based ? I'll need to re-spin it and send a new version. Are you on linux plumbers conference this year? Best Regards, Oleksij -- Pengutronix e.K. | | Steuerwalder Str. 21 | http://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |