Index Index for
Section 9
Index Alphabetical
listing for S
Bottom of page Bottom of
page

slave(9r)

NAME

slave - VMEbus: Checks that the device is valid for this controller

SYNOPSIS

int slave( struct device *device, io_handle_t addr1 );

ARGUMENTS

device Specifies a pointer to the VMEbus device's device data structure. The VMEbus configuration code passes this pointer to the driver's slave() routine. The routine can thus reference such information as the logical unit number of the device, whether the device is functional, and the controller number associated with the controller that this device is connected to. addr1 Specifies an I/O handle that you can use to reference a device register located in the VMEbus address space. This I/O handle is created, passed, and can be used in the same manner as the addr1 I/O handle passed to probe(); see the reference description of probe(). If a second CSR was specified in a VBA_Option entry in the /etc/sysconfigtab file, the VMEbus configuration code passes information in the addr2 member of the device's controller data structure pointer. This member contains an I/O handle that you can use to reference a device register located in the VMEbus onboard memory. This I/O handle is created, stored, and can be used in the same manner as the second I/O handle described for probe(); see the reference description of probe().

ENTRY POINT

The driver data structure

DESCRIPTION

A device driver's slave() routine is called only for a controller that has slave devices connected to it. This routine is called once for each slave attached to the controller. The arguments you pass to the slave() routine differ according to the bus on which the driver operates. The SYNOPSIS section shows the arguments associated with a slave() routine for a VMEbus.

RETURN VALUES

The slave() routine returns a nonzero value if the device is present.

SEE ALSO

Kernel Routines: probe(9r)

Index Index for
Section 9
Index Alphabetical
listing for S
Top of page Top of
page