Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   26626 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

I2C_REGISTER_BOARD_I(9)	    I2C and SMBus Subsystem    I2C_REGISTER_BOARD_I(9)

NAME
       i2c_register_board_info - statically declare I2C devices

SYNOPSIS
       int i2c_register_board_info(int busnum,
				   struct i2c_board_info const * info,
				   unsigned len);

ARGUMENTS
       busnum
	   identifies the bus to which these devices belong

       info
	   vector of i2c device descriptors

       len
	   how many descriptors in the vector; may be zero to reserve the
	   specified bus number.

DESCRIPTION
       Systems using the Linux I2C driver stack can declare tables of board
       info while they initialize. This should be done in board-specific init
       code near arch_initcall time, or equivalent, before any I2C adapter
       driver is registered. For example, mainboard init code could define
       several devices, as could the init code for each daughtercard in a
       board stack.

       The I2C devices will be created later, after the adapter for the
       relevant bus has been registered. After that moment, standard driver
       model tools are used to bind “new style” I2C drivers to the devices.
       The bus number for any device declared using this routine is not
       available for dynamic allocation.

       The board info passed can safely be __initdata, but be careful of
       embedded pointers (for platform_data, functions, etc) since that won´t
       be copied.

COPYRIGHT
Kernel Hackers Manual 2.6.	 November 2013	       I2C_REGISTER_BOARD_I(9)

Vote for polarhome