Lines Matching refs:hcf_service_nic
607 * - the received frame fits in the look ahead buffer, by the hcf_service_nic call that reported the Rx frame
609 * - if neither of the above implicit acks nor an explicit ack by the MSF, by the first hcf_service_nic after
610 * the hcf_service_nic that reported the Rx frame.
648 * invocation of hcf_service_nic is (apparently) called in the ISR when the ISR was activated as result of a
672 *6: ack the "old" Rx-event. See "Rx Buffer free strategy" in hcf_service_nic above for more explanation.
1468 * hcf_dma_rx_get must be called repeatedly by the MSF when hcf_service_nic signals availability of a rx frame
2341 * HCF_SUCCESS No SSN error ( or HCF_ERR_MIC already reported by hcf_service_nic)
2343 * reported by hcf_service_nic)
2360 * by hcf_service_nic in the lookahead buffer or be just behind it, i.e. the first byte not yet read.
2366 * o at entry: look ahead buffer as passed with hcf_service_nic is still accessible and unchanged
2374 * look ahead buffer by hcf_service_nic (i.e. the look ahead buffer size minus
2424 * - Asserting on being enabled/present is superfluous, since a non-zero IFB_lal implies that hcf_service_nic
2476 rc = check_mic( ifbp ); //prevents MIC error report if hcf_service_nic already consumed all
2528 * Resource Indicator periodically after calling hcf_service_nic.
2533 * a next hcf_service_nic it appears that the Resource has become available.
2804 *.MODULE int hcf_service_nic( IFBP ifbp, wci_bufp bufp, unsigned int len )
2831 * - IFB_LinkStat reflects new link status or 0x0000 if no change relative to previous hcf_service_nic call.
2833 * - IFB_LinkStat link status, 0x8000 reflects change relative to previous hcf_service_nic call.
2852 * If the frame is read completely by hcf_service_nic (i.e. the frame fits completely in the lookahead buffer),
2854 * Only if the frame is read completely by hcf_service_nic, hcf_service_nic checks the MIC and sets the return
2870 * hcf_service_nic returns:
2877 * hcf_service_nic is presumed to neither interrupt other HCF-tasks nor to be interrupted by other HCF-tasks.
2878 * A way to achieve this is to precede hcf_service_nic as well as all other HCF-tasks with a call to
2884 * hcf_service_nic services the following Hermes events:
2897 *!! hcf_service_nic does not service the following Hermes events:
2909 * zero. Former versions of the HCF handled WMP messages and supported a "monitor" mode in hcf_service_nic,
2915 * When hcf_service_nic reports the availability of a non-DMA message, the MSF can access that message by
2922 * - hcf_service_nic is called again
2926 * interrupt will cause hcf_service_nic to be called, which will cause the ack-ing of the "last" Rx-event
2930 * - hcf_service_nic is called without a prior call to hcf_connect.
2948 * hcf_service_nic is skipped. Since hcf_cntl turns into a NOP if Primary or Station F/W is incompatible,
2949 * hcf_service_nic is also skipped in those cases.
2950 * To prevent that hcf_service_nic reports bogus information to the MSF with all - possibly difficult to
2953 * HREG_EV_STAT, this is now also used in hcf_service_nic. The motivation to change strategy is partly
2956 * hcf_service_nic even more important.
2968 * alloc event is superficially serviced by hcf_service_nic to create a pseudo-resource with value
2977 * Note, the Ack of all of above events is handled at the end of hcf_service_nic
2981 * hcf_service_nic and that this depends on the IFB_RxLen initialization in the begin of hcf_service_nic.
3018 * to optimize the flow ( a better chance to get new Rx data in the next pass through hcf_service_nic ).
3032 * The HREG_EV_RX event is acknowledged by the first hcf_service_nic call after the
3033 * hcf_service_nic call that reported the occurrence of this event.
3054 hcf_service_nic( IFBP ifbp, wci_bufp bufp, unsigned int len )
3146 } else { /* IFB_RxFID is cleared, so you do not get another Rx_Ack at next entry of hcf_service_nic */
3162 } // hcf_service_nic
3242 * The MIC is separate for Tx and Rx, thus allowing hcf_send_msg to occur between hcf_service_nic and
3320 * The MIC is separate for Tx and Rx, thus allowing hcf_send_msg to occur between hcf_service_nic and
3849 * value by hcf_service_nic, IFB_RscInd has to be "corrected" again to its 0x0000 value.
3920 * hcf_service_nic has this behavior).
3939 /*1: here recovery logic for intervening BAP access between hcf_service_nic and hcf_rcv_msg COULD be added