On Mon, 2017-01-09 at 10:22 +1030, Andrew Jeffery wrote: > Alternatively, in the style of your first para, we could push the > host > CPU state management into the kernel and expose a boot/reboot/power- > off > API to userspace. That would give us a place to hook calls for > configuring and cleaning up any host-dependent drivers on the BMC. That's nasty. Each machine has a subtly different way of controller host power, that would mean a different kernel driver for each of them, which we are trying to avoid. This is userspace policy. Cheers, Ben. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
