IB/ipath: Change use of constants for TID type to defined values

Browse source

Define pkt rcvd 'type' in a way consistent with HW spec and chips.

The hardware considers received packets of type 0 to be expected, and
type 1 to be eager. The driver was calling the ipath_f_put_tid
functions using a variable called 'type' set to 0 for eager and to 1
for expected packets.  Worse, the iba6110 and iba6120 drivers used
those values inconsistently.  This was quite confusing.  Now
everything is consistent with the hardware.

Signed-off-by: Dave Olson <dave.olson@qlogic.com>
Signed-off-by: Roland Dreier <rolandd@cisco.com>

...

This commit is contained in:

Joan Eslinger 2007-06-18 14:24:39 -07:00 • committed by Roland Dreier

parent 1dd6a1be14

commit f716cdfe57

4 changed files with 24 additions and 15 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

12

drivers/infiniband/hw/ipath/ipath_file_ops.c

View file

10

drivers/infiniband/hw/ipath/ipath_iba6110.c

View file

14

drivers/infiniband/hw/ipath/ipath_iba6120.c

View file

3

drivers/infiniband/hw/ipath/ipath_init_chip.c

View file