99 lines
		
	
	
		
			3.1 KiB
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
			
		
		
	
	
			99 lines
		
	
	
		
			3.1 KiB
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
| #
 | |
| # I2C subsystem configuration
 | |
| #
 | |
| 
 | |
| menuconfig I2C
 | |
| 	tristate "I2C support"
 | |
| 	depends on HAS_IOMEM
 | |
| 	---help---
 | |
| 	  I2C (pronounce: I-square-C) is a slow serial bus protocol used in
 | |
| 	  many micro controller applications and developed by Philips.  SMBus,
 | |
| 	  or System Management Bus is a subset of the I2C protocol.  More
 | |
| 	  information is contained in the directory <file:Documentation/i2c/>,
 | |
| 	  especially in the file called "summary" there.
 | |
| 
 | |
| 	  Both I2C and SMBus are supported here. You will need this for
 | |
| 	  hardware sensors support, and also for Video For Linux support.
 | |
| 
 | |
| 	  If you want I2C support, you should say Y here and also to the
 | |
| 	  specific driver for your bus adapter(s) below.
 | |
| 
 | |
| 	  This I2C support can also be built as a module.  If so, the module
 | |
| 	  will be called i2c-core.
 | |
| 
 | |
| if I2C
 | |
| 
 | |
| config I2C_BOARDINFO
 | |
| 	boolean
 | |
| 	default y
 | |
| 
 | |
| config I2C_COMPAT
 | |
| 	boolean "Enable compatibility bits for old user-space"
 | |
| 	default y
 | |
| 	help
 | |
| 	  Say Y here if you intend to run lm-sensors 3.1.1 or older, or any
 | |
| 	  other user-space package which expects i2c adapters to be class
 | |
| 	  devices. If you don't know, say Y.
 | |
| 
 | |
| config I2C_CHARDEV
 | |
| 	tristate "I2C device interface"
 | |
| 	help
 | |
| 	  Say Y here to use i2c-* device files, usually found in the /dev
 | |
| 	  directory on your system.  They make it possible to have user-space
 | |
| 	  programs use the I2C bus.  Information on how to do this is
 | |
| 	  contained in the file <file:Documentation/i2c/dev-interface>.
 | |
| 
 | |
| 	  This support is also available as a module.  If so, the module 
 | |
| 	  will be called i2c-dev.
 | |
| 
 | |
| config I2C_HELPER_AUTO
 | |
| 	bool "Autoselect pertinent helper modules"
 | |
| 	default y
 | |
| 	help
 | |
| 	  Some I2C bus drivers require so-called "I2C algorithm" modules
 | |
| 	  to work. These are basically software-only abstractions of generic
 | |
| 	  I2C interfaces. This option will autoselect them so that you don't
 | |
| 	  have to care.
 | |
| 
 | |
| 	  Unselect this only if you need to enable additional helper
 | |
| 	  modules, for example for use with external I2C bus drivers.
 | |
| 
 | |
| 	  In doubt, say Y.
 | |
| 
 | |
| source drivers/i2c/algos/Kconfig
 | |
| source drivers/i2c/busses/Kconfig
 | |
| source drivers/i2c/chips/Kconfig
 | |
| 
 | |
| config I2C_DEBUG_CORE
 | |
| 	bool "I2C Core debugging messages"
 | |
| 	help
 | |
| 	  Say Y here if you want the I2C core to produce a bunch of debug
 | |
| 	  messages to the system log.  Select this if you are having a
 | |
| 	  problem with I2C support and want to see more of what is going on.
 | |
| 
 | |
| config I2C_DEBUG_ALGO
 | |
| 	bool "I2C Algorithm debugging messages"
 | |
| 	help
 | |
| 	  Say Y here if you want the I2C algorithm drivers to produce a bunch
 | |
| 	  of debug messages to the system log.  Select this if you are having
 | |
| 	  a problem with I2C support and want to see more of what is going
 | |
| 	  on.
 | |
| 
 | |
| config I2C_DEBUG_BUS
 | |
| 	bool "I2C Bus debugging messages"
 | |
| 	help
 | |
| 	  Say Y here if you want the I2C bus drivers to produce a bunch of
 | |
| 	  debug messages to the system log.  Select this if you are having
 | |
| 	  a problem with I2C support and want to see more of what is going
 | |
| 	  on.
 | |
| 
 | |
| config I2C_DEBUG_CHIP
 | |
| 	bool "I2C Chip debugging messages"
 | |
| 	help
 | |
| 	  Say Y here if you want the I2C chip drivers to produce a bunch of
 | |
| 	  debug messages to the system log.  Select this if you are having
 | |
| 	  a problem with I2C support and want to see more of what is going
 | |
| 	  on.
 | |
| 
 | |
| endif # I2C
 |