Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

smb(4) [linux man page]

SMB(4)							   BSD Kernel Interfaces Manual 						    SMB(4)

NAME
smb -- SMB generic I/O device driver SYNOPSIS
device smb DESCRIPTION
The smb character device driver provides generic i/o to any smbus(4) instance. In order to control SMB devices, use /dev/smb? with the ioctls described below. Any of these ioctl commands takes a pointer to struct smbcmd as its argument. #include <sys/types.h> struct smbcmd { char cmd; int count; u_char slave; union { char byte; short word; char *byte_ptr; short *word_ptr; struct { short sdata; short *rdata; } process; } data; }; The slave field is always used, and provides the address of the SMBus slave device to talk to. The slave address is specified in the seven most significant bits (i.e. ``left-justified''). The least significant bit of the slave address must be zero. Ioctl Description SMB_QUICK_WRITE The QuickWrite command just issues the device address with write intent to the bus, without transferring any data. SMB_QUICK_READ The QuickRead command just issues the device address with read intent to the bus, without transferring any data. SMB_SENDB The SendByte command sends the byte provided in the cmd field to the device. SMB_RECVB The ReceiveByte command reads a single byte from the device which will be returned in the cmd field. SMB_WRITEB The WriteByte command first sends the byte from the cmd field to the device, followed by the byte given in data.byte. SMB_WRITEW The WriteWord command first sends the byte from the cmd field to the device, followed by the word given in data.word. Note that the SMBus byte-order is little-endian by definition. SMB_READB The ReadByte command first sends the byte from the cmd field to the device, and then reads one byte of data from the device. The returned data will be stored in the location pointed to by data.byte_ptr. SMB_READW The ReadWord command first sends the byte from the cmd field to the device, and then reads one word of data from the device. The returned data will be stored in the location pointed to by data.word_ptr. SMB_PCALL The ProcedureCall command first sends the byte from the cmd field to the device, followed by the word provided in data.process.sdata. It then reads one word of data from the device, and returns it in the location pointed to by data.process.rdata. SMB_BWRITE The BlockWrite command first sends the byte from the cmd field to the device, followed by count bytes of data that are taken from the buffer pointed to by data.byte_ptr. The SMBus specification mandates that no more than 32 bytes of data can be transferred in a single block read or write command. This value is available in the constant SMB_MAXBLOCKSIZE. SMB_BREAD The BlockRead command first sends the byte from the cmd field to the device, and then reads count bytes of data that from the device. These data will be returned in the buffer pointed to by data.byte_ptr. The read(2) and write(2) system calls are not implemented by this driver. ERRORS
The ioctl(2) commands can cause the following driver-specific errors: [ENXIO] Device did not respond to selection. [EBUSY] Device still in use. [ENODEV] Operation not supported by device (not supposed to happen). [EINVAL] General argument error. [EWOULDBLOCK] SMBus transaction timed out. SEE ALSO
ioctl(2), smbus(4) HISTORY
The smb manual page first appeared in FreeBSD 3.0. AUTHORS
This manual page was written by Nicolas Souchu. BSD
February 6, 2009 BSD

Check Out this Related Man Page

I2CGET(8)						      System Manager's Manual							 I2CGET(8)

NAME
i2cget - read from I2C/SMBus chip registers SYNOPSIS
i2cget [-f] [-y] i2cbus chip-address [data-address [mode]] i2cget -V DESCRIPTION
i2cget is a small helper program to read registers visible through the I2C bus (or SMBus). OPTIONS
-V Display the version and exit. -f Force access to the device even if it is already busy. By default, i2cget will refuse to access a device which is already under the control of a kernel driver. Using this flag is dangerous, it can seriously confuse the kernel driver in question. It can also cause i2cget to return an invalid value. So use at your own risk and only if you know what you're doing. -y Disable interactive mode. By default, i2cget will wait for a confirmation from the user before messing with the I2C bus. When this flag is used, it will perform the operation directly. This is mainly meant to be used in scripts. Use with caution. There are two required options to i2cget. i2cbus indicates the number or name of the I2C bus to be scanned. This number should correspond to one of the busses listed by i2cdetect -l. chip-address specifies the address of the chip on that bus, and is an integer between 0x03 and 0x77. data-address specifies the address on that chip to read from, and is an integer between 0x00 and 0xFF. If omitted, the currently active register will be read (if that makes sense for the considered chip). The mode parameter, if specified, is one of the letters b, w or c, corresponding to a read byte data, a read word data or a write byte/read byte transaction, respectively. A p can also be appended to the mode parameter to enable PEC. If the mode parameter is omitted, i2cget defaults to a read byte data transaction, unless data-address is also omitted, in which case the default (and only valid) transaction is a single read byte. WARNING
i2cget can be extremely dangerous if used improperly. I2C and SMBus are designed in such a way that an SMBus read transaction can be seen as a write transaction by certain chips. This is particularly true if setting mode to cp (write byte/read byte with PEC). Be extremely careful using this program. SEE ALSO
i2cdump(8), i2cset(8) AUTHOR
Jean Delvare This manual page was strongly inspired from those written by David Z Maze for i2cset. May 2008 I2CGET(8)
Man Page