Commit a7611e84 authored by Clemens Ladisch's avatar Clemens Ladisch Committed by Stefan Richter

firewire: cdev: fix IR multichannel event documentation

State more precisely when fw_cdev_event_iso_interrupt_mc is sent.
While the comment tried to reflect an amibuity in the OHCI
specification, there is only one method that is useful in practice,
and this also matches all the hardware implementations I've tested.
Signed-off-by: default avatarClemens Ladisch <clemens@ladisch.de>
Signed-off-by: default avatarStefan Richter <stefanr@s5r6.in-berlin.de>
parent 0c0efbac
...@@ -267,9 +267,8 @@ struct fw_cdev_event_iso_interrupt { ...@@ -267,9 +267,8 @@ struct fw_cdev_event_iso_interrupt {
* *
* This event is sent in multichannel contexts (context type * This event is sent in multichannel contexts (context type
* %FW_CDEV_ISO_CONTEXT_RECEIVE_MULTICHANNEL) for &fw_cdev_iso_packet buffer * %FW_CDEV_ISO_CONTEXT_RECEIVE_MULTICHANNEL) for &fw_cdev_iso_packet buffer
* chunks that have the %FW_CDEV_ISO_INTERRUPT bit set. Whether this happens * chunks that have been completely filled and that have the
* when a packet is completed and/or when a buffer chunk is completed depends * %FW_CDEV_ISO_INTERRUPT bit set.
* on the hardware implementation.
* *
* The buffer is continuously filled with the following data, per packet: * The buffer is continuously filled with the following data, per packet:
* - the 1394 iso packet header as described at &fw_cdev_event_iso_interrupt, * - the 1394 iso packet header as described at &fw_cdev_event_iso_interrupt,
......
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