skiboot 5.10.2 release notes

Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
(cherry picked from commit f14716595ee54cd3f55baaeae3c98bc16e7926b6)
Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>

1 files changed, 29 insertions, 0 deletions

diff --git a/doc/release-notes/skiboot-5.10.2.rst b/doc/release-notes/skiboot-5.10.2.rst
new file mode 100644
index 00000000..9c828dfd
--- /dev/null
+++ b/doc/release-notes/skiboot-5.10.2.rst
@@ -0,0 +1,29 @@
+.. _skiboot-5.10.2:
+
+==============
+skiboot-5.10.2
+==============
+
+skiboot 5.10.2 was released on Tuesday March 6th, 2018. It replaces
+:ref:`skiboot-5.10.1` as the current stable release in the 5.10.x series.
+
+Over :ref:`skiboot-5.10.1`, we have one improvement:
+
+- Tie tm-suspend fw-feature and opal_reinit_cpus() together
+
+  Currently opal_reinit_cpus(OPAL_REINIT_CPUS_TM_SUSPEND_DISABLED)
+  always returns OPAL_UNSUPPORTED.
+
+  This ties the tm suspend fw-feature to the
+  opal_reinit_cpus(OPAL_REINIT_CPUS_TM_SUSPEND_DISABLED) so that when tm
+  suspend is disabled, we correctly report it to the kernel.  For
+  backwards compatibility, it's assumed tm suspend is available if the
+  fw-feature is not present.
+
+  Currently hostboot will clear fw-feature(TM_SUSPEND_ENABLED) on P9N
+  DD2.1. P9N DD2.2 will set fw-feature(TM_SUSPEND_ENABLED).  DD2.0 and
+  below has TM disabled completely (not just suspend).
+
+  We are using opal_reinit_cpus() to determine this setting (rather than
+  the device tree/HDAT) as some future firmware may let us change this
+  dynamically after boot. That is not the case currently though.