flash(9) [netbsd man page]

FLASH(9)						   BSD Kernel Developer's Manual						  FLASH(9)

NAME

     flash -- subsystem for flash-like memory devices

SYNOPSIS

     #include <dev/flash/flash.h>

     device_t
     flash_attach_mi(const struct flash_interface *fl, device_t dev);

DESCRIPTION

     Flash-like devices can register themselves to the flash layer with the flash_hw_if structure.  This structure has function pointers and other
     fields.

     The attachment can be done by calling flash_attach_mi() with this structure and the device's device_t as an argument.  Return value is the
     flash layer device.  The flash_interface structure is shown below.

     struct flash_interface {
	     int (*erase) (device_t, struct flash_erase_instruction *);
	     int (*read) (device_t, off_t, size_t, size_t *, uint8_t *);
	     int (*write) (device_t, off_t, size_t, size_t *, const uint8_t *);
	     int (*block_markbad)(device_t, uint64_t);
	     int (*block_isbad)(device_t, uint64_t);
	     int (*sync) (device_t);

	     int (*submit)(device_t, struct buf *);

	     /* storage for partition info */
	     struct flash_partition partition;

	     /* total size of mtd */
	     flash_addr_t size;
	     uint32_t page_size;
	     uint32_t erasesize;
	     uint32_t writesize;
	     uint32_t minor;
	     uint8_t type;
     };

SEE ALSO

     flash(4), nand(9)

AUTHORS

     Adam Hoka <ahoka@NetBSD.org>

BSD
								  March 31, 2011							       BSD

DEVICE_GET_STATE(9)					   BSD Kernel Developer's Manual				       DEVICE_GET_STATE(9)

NAME

     device_get_state, device_busy, device_unbusy, device_is_alive, device_is_attached -- manipulate device state

SYNOPSIS

     #include <sys/param.h>
     #include <sys/bus.h>

     device_state_t
     device_get_state(device_t dev);

     void
     device_busy(device_t dev);

     void
     device_unbusy(device_t dev);

     int
     device_is_alive(device_t dev);

     int
     device_is_attached(device_t dev);

DESCRIPTION

     The current state of a device is accessed by calling device_get_state() which returns DS_NOTPRESENT, DS_ALIVE, DS_ATTACHED or DS_BUSY
     (described in device(9)).	To test see if a device was successfully probed, call device_is_alive() which simply returns if the state is
     greater or equal to DS_ALIVE.  To test see if a device was successfully attached, call device_is_attached() which simply returns if the state
     is greater or equal to DS_ATTACHED.

     Each device has a busy count which is incremented when device_busy() is called and decremented when device_unbusy() is called.  Both routines
     return an error if the device state is less than DS_ATTACHED.

     When device_busy() is called on a device in the DS_ATTACHED state, the device changes to the DS_BUSY state.  When device_unbusy() is called
     and after decrementing, the busy count for the device is zero, the device changes to the DS_ATTACHED state.

SEE ALSO

     device(9)

AUTHORS

     This manual page was written by Doug Rabson.

BSD
								   June 16, 1998							       BSD