Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit2257b74

Browse files
Tomas Winklergregkh
Tomas Winkler
authored andcommitted
mei: docs: add vtag ioctl documentation
Add structured documenation for the new vtag ioctlSigned-off-by: Tomas Winkler <tomas.winkler@intel.com>Link:https://lore.kernel.org/r/20200818115147.2567012-13-tomas.winkler@intel.comSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
1 parentaa207a0 commit2257b74

File tree

1 file changed

+37
-0
lines changed
  • Documentation/driver-api/mei

1 file changed

+37
-0
lines changed

‎Documentation/driver-api/mei/mei.rst‎

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -42,6 +42,11 @@ The session is terminated calling :c:func:`close(int fd)`.
4242

4343
A code snippet for an application communicating with Intel AMTHI client:
4444

45+
In order to support virtualization or sandboxing a trusted supervisor
46+
can use:c:macro:`MEI_CONNECT_CLIENT_IOCTL_VTAG` to create
47+
virtual channels with an Intel ME feature. Not all features support
48+
virtual channels such client with answer EOPNOTSUPP.
49+
4550
..code-block::C
4651
4752
struct mei_connect_client_data data;
@@ -110,6 +115,38 @@ Connect to firmware Feature/Client.
110115
data that can be sent or received. (e.g. if MTU=2K, can send
111116
requests up to bytes 2k and received responses up to 2k bytes).
112117

118+
IOCTL_MEI_CONNECT_CLIENT_VTAG:
119+
------------------------------
120+
121+
..code-block::none
122+
123+
Usage:
124+
125+
struct mei_connect_client_data_vtag client_data_vtag;
126+
127+
ioctl(fd, IOCTL_MEI_CONNECT_CLIENT_VTAG, &client_data_vtag);
128+
129+
Inputs:
130+
131+
struct mei_connect_client_data_vtag - contain the following
132+
Input field:
133+
134+
in_client_uuid - GUID of the FW Feature that needs
135+
to connect to.
136+
vtag - virtual tag [1, 255]
137+
138+
Outputs:
139+
out_client_properties - Client Properties: MTU and Protocol Version.
140+
141+
Error returns:
142+
143+
ENOTTY No such client (i.e. wrong GUID) or connection is not allowed.
144+
EINVAL Wrong IOCTL Number or tag == 0
145+
ENODEV Device or Connection is not initialized or ready.
146+
ENOMEM Unable to allocate memory to client internal data.
147+
EFAULT Fatal Error (e.g. Unable to access user input data)
148+
EBUSY Connection Already Open
149+
EOPNOTSUPP Vtag is not supported
113150
114151
IOCTL_MEI_NOTIFY_SET
115152
---------------------

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp