On Thu, Feb 27, 2025 at 10:46:13AM +0000, André Draszik wrote: > Add support for specifying different register/mask/value combinations > for different types of reset. > > In particular, update the binding to allow platforms to specify the > following reset modes: soft, warm, cold, hard. > > Linux can perform different types of reset using its reboot= kernel > command line argument, and some platforms also wish to reset > differently based on whether or not e.g. contents of RAM should be > retained across the reboot. > > The new properties match the existing properties, just prefixed with > one of the reset modes mentioned above. This would be why we don't do "simple" or "generic" bindings. There's always one more variation needing yet more properties to handle it. We also draw the line at encoding register accesses into DT. If we wanted that, we would have created a language for doing that (or started using Forth in FDT). You need a specific binding for your h/w. If you can make it work with a "generic" driver, then that's great, but that's an OS decision which can change if needed. The binding can't change. Rob
