[Skiboot] [PATCH 10/12] opal: Enable backup topology.

Stewart Smith stewart at linux.vnet.ibm.com
Wed Apr 22 14:19:19 AEST 2015

Mahesh J Salgaonkar <mahesh at linux.vnet.ibm.com> writes:
> Whenever FSP makes any changes to backup topology as part of either
> routine hardware maintenance or fixing failed backup topology configuration,
> it sends out mailbox command xE6, s/c 0x06, mod 0, to enable/disable
> the backup topology. OPAL layer should keep itself up-to-date with accurate
> details of current topology configurations. This will help OPAL layer to
> successfully handle any TOD failover in future.
> The FSP can only request that the currently inactive (backup) topology be
> disabled or enabled. If the requested topology is currently the active
> topology, then fail this request with a 0xB8 (TOD topology in use) status
> as return code.
> For disable request, set the backup topology status as disabled.
> For enable request, scan all the available chips and find the new backup
> master chip by looking at TOD status register of each chip.
> Signed-off-by: Mahesh Salgaonkar <mahesh at linux.vnet.ibm.com>
> ---
>  hw/chiptod.c               |  106 ++++++++++++++++++++++++++++++++++++++++++++
>  include/fsp.h              |    9 ++++
>  platforms/ibm-fsp/common.c |    3 +

Should this be a platform call rather than having FSP code leak into
common hw code?

More information about the Skiboot mailing list