Commit f20ce779 authored by Kumar Sanghvi's avatar Kumar Sanghvi Committed by David S. Miller

Documentation: Update Phonet doc for Pipe controller changes

Updates to Phonet doc for Pipe controller 'connect' socket
implementation and changes related to socket options.
Signed-off-by: default avatarKumar Sanghvi <kumar.sanghvi@stericsson.com>
Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
parent b3d62553
...@@ -199,33 +199,29 @@ between itself and a remote pipe-end point (e.g. modem). ...@@ -199,33 +199,29 @@ between itself and a remote pipe-end point (e.g. modem).
The implementation adds socket options at SOL_PNPIPE level: The implementation adds socket options at SOL_PNPIPE level:
PNPIPE_CREATE PNPIPE_PIPE_HANDLE
It accepts an integer argument where-in It accepts an integer argument for setting value of pipe handle.
lower order 16 bits: pn_dev and pn_port pair for remote pep.
higher order 16 bits: 8 bit pipe-handle
It sends a PNS_PEP_CONNECT_REQ on sequenced socket itself. On getting
PNS_PEP_CONNECT_RESP, it sends PNS_PEP_CONNECT_REQ to remote pep. On
getting response from remote pep, it selects the best possible Flow
control mechanism supported by remote-pep (modem) and then it sends
PNS_PEP_CREATED_IND to the sequenced socket and to the remote pep.
It then updates the pipe state associated with the sequenced socket to
be PIPE_DISABLED.
PNPIPE_ENABLE accepts one integer value (int). If set to zero, the pipe PNPIPE_ENABLE accepts one integer value (int). If set to zero, the pipe
is disabled. If the value is non-zero, the pipe is enabled. If the pipe is disabled. If the value is non-zero, the pipe is enabled. If the pipe
is not (yet) connected, ENOTCONN is error is returned. is not (yet) connected, ENOTCONN is error is returned.
PNPIPE_DESTROY The implementation also adds socket 'connect'. On calling the 'connect', pipe
This will send out PNS_PEP_DISCONNECT_REQ on the sequenced socket and will be created between the source socket and the destination, and the pipe
the remote pep. state will be set to PIPE_DISABLED.
It will also update the pipe state associated with the sequenced socket
to PIPE_IDLE
After a pipe has been created and enabled successfully, the Pipe data can be After a pipe has been created and enabled successfully, the Pipe data can be
exchanged between the host-pep and remote-pep (modem). exchanged between the host-pep and remote-pep (modem).
User-space would typically follow below sequence with Pipe controller:-
-socket
-bind
-setsockopt for PNPIPE_PIPE_HANDLE
-connect
-setsockopt for PNPIPE_ENCAP_IP
-setsockopt for PNPIPE_ENABLE
Authors Authors
------- -------
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment