sbefifo userspace api

[Patrick Williams]

On Tue, Feb 21, 2017 at 02:34:18AM +1100, Alistair Popple wrote:
> I would also be interested in the answer to the inverse - why put them
> in the kernel? There's the OCC hwmon driver - what chip-ops does that
> need? Just get/putscom? If that's the case I thought we were already
> exposing scom chip-op operations via an OpenFSI master?

When the P9 chip has security enabled, you cannot even issue SCOM
operations without going through the SBE FIFO.  The SBE provides a
white-list filtering system that prevents the majority of the SCOM space
from being accessed.  We will need a "SCOM over FIFO" driver on top of
FSI.

-- 
Patrick Williams
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20170221/70b0afc6/attachment.sig>