Platform framework communications

1 . An Information Handling System (IHS), comprising:

a plurality of hardware devices, each configured to be operated by one or more participants of a platform framework;

a processor; and

a memory coupled to the processor, the memory configured with program instructions stored thereon that, upon execution, cause the platform framework of the IHS to:

register a first of the one or more participants as configured to provide operation of a first of the plurality of hardware devices, wherein registration comprises specification of a handle that comprises a reference to an Inter-process Communication (IPC) resource of the IHS, for communication with the first participant in order to operate the first hardware device, wherein the handle is validated at least in part by Root-of-Trust hardware, wherein registration further comprises a specification of an API supported by the first participant, and wherein the API is represented as a structured file comprising JSON or XML;

provide the handle for communication with the first participant in operation of the first hardware device to a second of the one or more participants of the platform framework;

determine an update to the handle for communication with the first participant in operation of the first hardware device, wherein the first participant comprises a containerized workspace and wherein the update to the handle is determined in response to an error associated with the handle, at least in part as a result of migration of the containerized workspace from operation on the IHS to operation on a remote resource; and

notify the second participant of the updated handle for communication with the first participant in operation of the first hardware device,

wherein the executed instructions further cause the platform framework to determine whether the operation of the first hardware device by the first participant is in correspondence to operation of a kernel resource, generate a virtual platform framework participant configured to provide user-space access to capabilities of the kernel resource and configured to interface with the first participant in provision of operation of the kernel resource upon determination that operation of the first hardware device is in correspondence to operation of the kernel resource, generate a handle for communication with the virtual platform framework participant, and provide the second participant with the handle to the virtual platform framework participant instead of the handle for communication with the first participant.

2 . The IHS of claim 1 , wherein the first participant is configured to provide operation of the first hardware device by interface with at least one of a driver or firmware to operate the first hardware device.

3 . The IHS of claim 2 , wherein the handle is provided along with a token configured to correspond to a signature of the at least one of the driver and firmware to operate the first hardware device, and wherein the registration further comprises a specification of whether the token is configured to correspond only to the at least one of the driver and firmware used to operate the first hardware device or is also configured to correspond to additional software utilized by the first participant.

4 . The IHS of claim 3 , wherein, upon provision of the handle to the second participant, the second participant is configured to authenticate the token as signed by a trusted resource of the IHS.

5 . The IHS of claim 4 , wherein the trusted resource of the IHS is configured to sign the token upon validation that a signature calculated based on instructions by the at least one of the driver and firmware is determined to match the signature of the token.

6 . The IHS of claim 1 , wherein the update to the handle is determined in response to a plurality of errors detected by the platform framework.

7 . The IHS of claim 1 , wherein the handle supports an API (Application Programming Interface) configured to specify notifications that are generated by the first hardware device, and wherein the structured file is mapped to the first participant along with the communication handle and any token provided by the first participant.

8 . The IHS of claim 7 , wherein the API supported by the handle is further configured to specify operations of the first hardware device that are supported by the first participant.

9 . The IHS of claim 7 , wherein the notifications specified by the API supported by the handle comprise user presence detection notifications.

10 . The IHS of claim 7 , wherein the notifications specified by the API supported by the handle comprise notifications of a change in a physical posture of the IHS, and wherein the change in the physical posture comprises a transition among at least two of: a table posture, a display posture, a laptop posture, a stand posture, or a tent posture.

11 . The IHS of claim 8 , wherein the operations specified by the API supported by the handle comprise operations configured to capture images via a camera of the IHS.

12 . The IHS of claim 7 , wherein the API supported by the handle is further configured to specify operations configured to notify the first participant of policy changes related to the first hardware device.

13 . The IHS of claim 12 , wherein the first hardware device comprises a display of the IHS, and wherein the policy changes comprise changes to a display policy for initiation of privacy capabilities supported by the display, and wherein the privacy capabilities comprise at least one of: dim an output of the display, blur the output of the display, or transition the display to a low-power state with no output.

14 . A memory storage device configured with program instructions stored thereon that, upon execution by an Information Handling System (IHS) comprising a plurality of hardware devices, each configured to be operated by one or more participants of a platform framework, cause the IHS to:

register a first of the one or more participants as configured to provide operation of a first of the plurality of hardware devices, wherein registration comprises specification of a handle that comprises a reference to an Inter-process Communication (IPC) resource of the IHS, for communication with the first participant in order to operate the first hardware device, wherein the handle is validated at least in part by Root-of-Trust hardware, wherein registration further comprises a specification of an API supported by the first participant, wherein the API is represented as a structured file comprising JSON or XML mapped to the first participant along with the communication handle and any token provided by the first participant, wherein the first participant is configured to provide operation of the first hardware device by interface with at least one of a driver and firmware to operate the first hardware device, and wherein the registration further comprises a specification of whether the token is configured to correspond only to the at least one of the driver and firmware used to operate the first hardware device or is also configured to correspond to additional software utilized by the first participant;

provide the handle for communication with the first participant in operation of the first hardware device to a second of the one or more participants of the platform framework;

determine an update to the handle for communication with the first participant in operation of the first hardware device, wherein the first participant comprises a containerized workspace and wherein the update to the handle is determined in response to an error associated with the handle, at least in part as a result of migration of the containerized workspace from operation on the IHS to operation on a remote resource; and

notify the second participant of the updated handle for communication with the first participant in operation of the first hardware device, wherein notify comprises a user presence detection notification and a notification of a change in a physical posture of the IHS, and wherein the change in the physical posture comprises a transition among at least two of: a table posture, a display posture, a laptop posture, a stand posture, or a tent posture,

wherein the executed instructions further cause the platform framework to determine whether the operation of the first hardware device by the first participant is in correspondence to operation of a kernel resource, generate a virtual platform framework participant configured to provide user-space access to capabilities of the kernel resource and configured to interface with the first participant in provision of operation of the kernel resource upon determination that operation of the first hardware device is in correspondence to operation of the kernel resource, generate a handle for communication with the virtual platform framework participant, and provide the second participant with the handle to the virtual platform framework participant instead of the handle for communication with the first participant.

15 . A method, comprising:

registering one or more participants of a platform framework as providing operation of a plurality of hardware devices of an Information Handling System (IHS);

registering a first of the one or more participants as providing operation of a first of the plurality of hardware devices, wherein registration specifies a handle that comprises a reference to an Inter-process Communication (IPC) resource of the IHS, for communicating with the first participant in order to operate the first hardware device, wherein the handle is validated at least in part by Root-of-Trust hardware, wherein registration further specifies an API supported by the first participant, the API being represented as a structured file comprising JSON or XML mapped to the first participant along with the communication handle and any token provided by the first participant, wherein the first participant is configured to provide operation of the first hardware device by interface with at least one of a driver and firmware to operate the first hardware device, wherein the registration further comprises a specification of whether the token is configured to correspond only to the at least one of the driver and firmware used to operate the first hardware device or is also configured to correspond to additional software utilized by the first participant, wherein the API is configured to specify notifying the first participant of policy changes related to the first hardware device, wherein the first hardware device comprises a display of the IHS, wherein the policy changes comprise changes to a display policy for initiation of privacy capabilities supported by the display, and wherein the privacy capabilities comprise at least one of: dim an output of the display, blur the output of the display, or transition the display to a low-power state with no output;

providing the handle for communicating with the first participant in operation of the first hardware device to a second of the one or more participants of the platform framework;

determining an update to the handle used for communicating with the first participant in operation of the first hardware device, wherein the first participant comprises a containerized workspace and wherein the update to the handle is determined in response to an error associated with the handle, at least in part as a result of migration of the containerized workspace from operation on the IHS to operation on a remote resource; and

notifying the second participant of the updated handle for communicating with the first participant in operation of the first hardware device,

wherein the method further comprises: determining whether the operation of the first hardware device corresponds to operation of a kernel resource, generating a virtual platform framework participant that provides user-space access to capabilities of the kernel resource and interfaces with the first participant in provision of operation of the kernel resource in response to determining that the operation of the first hardware device corresponds to operation of the kernel resource, generating a handle for communication with the virtual platform framework participant, and providing the second participant with the handle to the virtual platform framework participant instead of the handle for communication with the first participant.