[src-draft/trunk]: src/share/man/man9 Adapt to recent code changes

[Martin Husemann <martin%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src-all/rev/0b2881a7bed6
branches:  trunk
changeset: 375746:0b2881a7bed6
user:      Martin Husemann <martin%NetBSD.org@localhost>
date:      Wed Feb 09 11:58:30 2022 +0100

description:
Adapt to recent code changes

diffstat:

 share/man/man9/usbwifi.9 |  42 +++++++++++++++++++++++++++++++++++-------
 1 files changed, 35 insertions(+), 7 deletions(-)

diffs (84 lines):

diff -r 7832fccc8d99 -r 0b2881a7bed6 share/man/man9/usbwifi.9
--- a/share/man/man9/usbwifi.9  Wed Feb 09 11:58:03 2022 +0100
+++ b/share/man/man9/usbwifi.9  Wed Feb 09 11:58:30 2022 +0100
@@ -52,7 +52,7 @@
 .Ft void
 .Fn usbwifi_attach "struct usbwifi *uw"
 .Ft void
-.Fn usbwifi_ic_attach "struct usbwifi *uw" "int num_tx_chains" "int num_rx_chains" "int flags"
+.Fn usbwifi_ic_attach "struct usbwifi *uw" "int num_tx_chains" "int num_rx_chains" "int num_tx_pipes" "int num_rx_pipes" "int flags"
 .Ft void
 .Fn usbwifi_attach_finalize "struct usbwifi *uw"
 .Ft int
@@ -206,15 +206,18 @@ section for more details about these fun
 .Bl -tag -width 4n
 .It Fn usbwifi_attach uw
 Initial stage attach of a usb wifi device.
-.It Fn usbwifi_ic_attach uw num_tx_chains num_rx_chains flags
+.It Fn usbwifi_ic_attach uw num_tx_chains num_rx_chains num_tx_pipes num_rx_pipes flags
 Second stage of the usb wifi attachment.
 This will connect the wifi chip to the ieee80211 stack and make the
 device known to the relevant sysctls.
 .Fa num_tx_chains
-is the number of Tx chains and priorities (endpoints) available with
-this device.
+is the number of Tx chains this radio provides.
 .Fa num_rx_chains
-is the number of Rx chains (endpoints) available with this device.
+is the number of Rx chains this radio may use.
+.Fa num_tx_pipes
+is the number of Tx priorities (USB endpoints) available, and
+.Fa num_rx_pipes
+is the number of Rx priorities (USB endpoints) available with this device.
 .Fa flags
 is used to initialize the
 .Va "struct ieee80211com"
@@ -307,14 +310,36 @@ Device owned flags word.
 The
 .Nm
 framework will not touch this value.
-.It uw_rx_xfer_flags
+.It uw_rxpipes
+the number of receive endpoints on the USB interface.
+This value is set from the arguments to the
+.Fn usbwifi_ic_attach
+call.
+.It uw_txpipes
+the number of transmit endpoints (that is: priorities) on the USB interface.
+This value is set from the arguments to the
+.Fn usbwifi_ic_attach
+call.
+.It uw_rx_xfer_flags and uw_rx_xfer_timeout
 Passed to
 .Fn usbd_setup_xfer
 for receiving packets.
-.It uw_tx_xfer_flags
+Defaults for this are set in
+.Fn usbwifi_attach
+as
+.Va USBD_NO_TIMEOUT
+and
+.Va USBD_SHORT_XFER_OK .
+.It uw_tx_xfer_flags and uw_tx_xfer_timeout
 Passed to
 .Fn usbd_setup_xfer
 for sending packets.
+Defaults for this are set in
+.Fn usbwifi_attach
+as
+.Va USBD_NO_TIMEOUT
+and
+.Va USBD_FORCE_SHORT_XFER .
 .It uw_rx_list_cnt
 Number of chain elements to allocate for Rx (for each endpoint).
 .It uw_tx_list_cnt
@@ -329,6 +354,9 @@ The overall attachement happens in three
 First the USB device is identified and
 .Fn usbwifi_attach
 is called.
+This will fill in default values for callbacks and the USB transfer
+related values.
+The driver can ovveride these setting after the call.
 Then the device is configured and all endpoint/chain related parameters
 are filled in.
 Also radio capabilities are queried.