ipath_init_chip.c File Reference

#include <linux/pci.h>
#include <linux/netdevice.h>
#include <linux/moduleparam.h>
#include <linux/slab.h>
#include <linux/stat.h>
#include <linux/vmalloc.h>
#include "ipath_kernel.h"
#include "ipath_common.h"

Go to the source code of this file.

Macros
#define	IPATH_MIN_USER_PORT_BUFCNT   7

Functions
	module_param_named (cfgports, ipath_cfgports, ushort, S_IRUGO)
	MODULE_PARM_DESC (cfgports,"Set max number of ports to use")
	module_param_call (kpiobufs, ipath_set_kpiobufs, param_get_ushort,&ipath_kpiobufs, S_IWUSR|S_IRUGO)
	MODULE_PARM_DESC (kpiobufs,"Set number of PIO buffers for driver")
int	ipath_init_chip (struct ipath_devdata *dd, int reinit)

Macro Definition Documentation

#define IPATH_MIN_USER_PORT_BUFCNT   7

Definition at line 47 of file ipath_init_chip.c.

Function Documentation

int ipath_init_chip	(	struct ipath_devdata *	dd,
		int	reinit
	)

ipath_init_chip - do the actual initialization sequence on the chip : the infinipath device : reinitializing, so don't allocate new memory

Do the actual initialization sequence on the chip. This is done both from the init routine called from the PCI infrastructure, and when we reset the chip, or detect that it was reset internally, or it's administratively re-enabled.

Memory allocation here and in called routines is only done in the first case (reinit == 0). We have to be careful, because even without memory allocation, we need to re-write all the chip registers TIDs, etc. after the reset or enable has completed.

Definition at line 708 of file ipath_init_chip.c.

module_param_call	(	kpiobufs	,
		ipath_set_kpiobufs	,
		param_get_ushort	,
		&	ipath_kpiobufs,
		S_IWUSR|	S_IRUGO
	)

module_param_named	(	cfgports	,
		ipath_cfgports	,
		ushort	,
		S_IRUGO
	)

MODULE_PARM_DESC	(	cfgports	,
		"Set max number of ports to use"
	)

MODULE_PARM_DESC	(	kpiobufs	,
		"Set number of PIO buffers for driver"
	)