| /linux/drivers/rtc/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
16 depends on !S390
20 be allowed to plug one or more RTCs to your system. You will
26 bool "Set system time from RTC on startup and resume"
29 If you say yes here, the system time (wall clock) will be set using
34 string "RTC used to set the system time"
35 depends on RTC_HCTOSYS
38 The RTC device that will be used to (re)initialize the system
39 clock, usually rtc0. Initialization is done when the system
44 This clock should be battery-backed, so that it reads the correct
[all …]
|
| /linux/drivers/mtd/devices/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
2 menu "Self-contained MTD device drivers"
3 depends on MTD!=n
4 depends on HAS_IOMEM
8 depends on PCI
12 These devices come in memory configurations from 32M - 1G. If you
21 particularly useful on the 2.2 kernels on PPC architectures as there
26 depends on MTD_PMC551
34 depends on MTD_PMC551
37 is only really useful if you are developing on this driver or
[all …]
|
| /linux/drivers/mtd/ |
| H A D | Kconfig | 5 Memory Technology Devices are flash, RAM and similar chips, often
6 used for solid state file systems on embedded devices. This option
9 to enumerate the devices which are present and obtain a handle on
17 depends on m
40 depends on BLOCK
43 Although most flash chips have an erase size too large to be useful
45 on RAM chips in this manner. This block device is a user of MTD
49 It's possible to mount a rootfs using the MTD device on the "root="
53 on flash chips to emulate a smaller block size. Needless to say,
62 depends on MTD_BLOCK!=y && BLOCK
[all …]
|
| /linux/Documentation/driver-api/gpio/ |
| H A D | intro.rst | 9 The documents in this directory give detailed instructions on how to access
17 A "General Purpose Input/Output" (GPIO) is a flexible software-controlled
18 digital signal. They are provided from many kinds of chips, and are familiar
20 represents a bit connected to a particular pin, or "ball" on Ball Grid Array
25 System-on-Chip (SOC) processors heavily rely on GPIOs. In some cases, every
26 non-dedicated pin can be configured as a GPIO; and most chips have at least
28 provide GPIOs; multifunction chips like power managers, and audio codecs
29 often have a few such pins to help with pin scarcity on SOCs; and there are
30 also "GPIO Expander" chips that connect using the I2C or SPI serial buses.
31 Most PC southbridges have a few dozen GPIO-capable pins (with only the BIOS
[all …]
|
| /linux/Documentation/hwmon/ |
| H A D | it87.rst | 4 Supported chips:
174 - Christophe Gauthron
175 - Jean Delvare <jdelvare@suse.de>
179 -----------------
182 0 if vbat should report power on value, 1 if vbat should be updated after
183 each read. Default is 0. On some boards the battery voltage is provided
185 at power on will be the actual battery voltage (which the chip does
186 automatically). On other boards the battery voltage is always fed to
191 Force PWM polarity to active high (DANGEROUS). Some chips are
192 misconfigured by BIOS - PWM values would be inverted. This option tries
[all …]
|
| H A D | scpi-hwmon.rst | 1 Kernel driver scpi-hwmon
4 Supported chips:
6 * Chips based on ARM System Control Processor Interface
8 Addresses scanned: -
15 -----------
17 This driver supports hardware monitoring for SoC's based on the ARM
18 System Control Processor (SCP) implementing the System Control
31 -----------
33 The driver relies on device tree node to indicate the presence of SCPI
|
| H A D | userspace-tools.rst | 5 ------------
7 Most mainboards have sensor chips to monitor system health (like temperatures,
11 The kernel drivers make the data from the sensor chips available in the /sys
13 values or configure the chips in a more friendly manner.
15 Lm-sensors
16 ----------
19 setup monitoring limits etc. You can get them on their homepage
20 http://www.lm-sensors.org/ or as a package from your Linux distribution.
23 Get lm-sensors from project web site. Please note, you need only userspace
28 0) get lm-sensors userspace utils
[all …]
|
| H A D | lm85.rst | 4 Supported chips:
79 - Philip Pokorny <ppokorny@penguincomputing.com>,
80 - Frodo Looijaard <frodol@dds.nl>,
81 - Richard Barrington <rich_b_nz@clear.net.nz>,
82 - Margit Schubert-While <margitsw@t-online.de>,
83 - Justin Thiessen <jthiessen@penguincomputing.com>
86 -----------
89 compatible chips including the Analog Devices ADM1027, ADT7463, ADT7468 and
90 SMSC EMC6D10x chips family.
92 The LM85 uses the 2-wire interface compatible with the SMBUS 2.0
[all …]
|
| H A D | sysfs-interface.rst | 5 through the sysfs interface. Since lm-sensors 3.0.0, libsensors is
6 completely chip-independent. It assumes that all the kernel drivers
10 This is a major improvement compared to lm-sensors 2.
12 Note that motherboards vary widely in the connections to sensor chips.
14 temperature sensor is connected to the CPU, or that the second fan is on
15 the CPU. Also, some values reported by the chips need some computation
16 before they make full sense. For example, most chips can only measure
22 For this reason, even if we aim at a chip-independent libsensors, it will
34 find all sensor chips, it is easier to follow the device symlinks from
37 Up to lm-sensors 3.0.0, libsensors looks for hardware monitoring attributes
[all …]
|
| H A D | ucd9000.rst | 4 Supported chips:
11 Addresses scanned: -
15 - http://focus.ti.com/lit/ds/symlink/ucd90120.pdf
16 - http://focus.ti.com/lit/ds/symlink/ucd90124.pdf
17 - http://focus.ti.com/lit/ds/symlink/ucd90160.pdf
18 - http://focus.ti.com/lit/ds/symlink/ucd90320.pdf
19 - http://focus.ti.com/lit/ds/symlink/ucd9090.pdf
20 - http://focus.ti.com/lit/ds/symlink/ucd90910.pdf
22 Author: Guenter Roeck <linux@roeck-us.net>
26 -----------
[all …]
|
| /linux/drivers/mtd/maps/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
3 depends on MTD!=n
4 depends on HAS_IOMEM
7 bool "Support non-linear mappings of flash chips"
10 paged mappings of flash chips.
14 depends on MTD_CFI || MTD_JEDECPROBE || MTD_ROM || MTD_RAM || MTD_LPDDR
17 ROM driver code to communicate with chips which are mapped
19 the physical address and size of the flash chips on your
21 with config options or at run-time.
28 depends on MTD_PHYSMAP
[all …]
|
| /linux/drivers/watchdog/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
16 on-line as fast as possible after a lock-up. There's both a watchdog
21 <file:Documentation/watchdog/watchdog-api.rst> in the kernel source.
25 <https://ibiblio.org/pub/Linux/system/daemons/watchdog/>. This daemon
42 bool "Disable watchdog shutdown on close"
51 bool "Update boot-enabled watchdog until userspace takes over"
58 the watchdog on its own. Thus if your userspace does not start fast
77 bool "Enable watchdog hrtimer-based pretimeouts"
88 depends on WATCHDOG_CORE
94 depends on WATCHDOG_PRETIMEOUT_GOV
[all …]
|
| /linux/drivers/net/ethernet/wiznet/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
8 depends on HAS_IOMEM
22 depends on HAS_IOMEM
24 Support for WIZnet W5100 chips.
35 depends on HAS_IOMEM
37 Support for WIZnet W5300 chips.
48 depends on WIZNET_W5100 || WIZNET_W5300
54 In direct address mode host system can directly access all registers
55 after mapping to Memory-Mapped I/O space.
60 In indirect address mode host system indirectly accesses registers
[all …]
|
| /linux/drivers/iio/adc/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
14 depends on MFD_88PM886_PMIC
18 found on the Marvell 88PM886 PMIC. The GPADC measures various
20 system, battery and USB Vbus.
23 called 88pm886-gpadc.
26 bool "ST-Ericsson AB8500 GPADC driver"
27 depends on AB8500_CORE && REGULATOR_AB8500
44 depends on SPI
61 depends on SPI
62 depends on GPIOLIB
[all …]
|
| /linux/drivers/mtd/chips/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
3 depends on MTD!=n
6 tristate "Detect flash chips by Common Flash Interface (CFI) probe"
13 support any device that is CFI-compliant, you need to enable this
15 for more information on CFI.
18 tristate "Detect non-CFI AMD/JEDEC-compatible flash chips"
22 This option enables JEDEC-style probing of flash chips which are not
24 CFI-targeted flash drivers for any chips which are identified which
26 covers most AMD/Fujitsu-compatible chips and also non-CFI
27 Intel chips.
[all …]
|
| /linux/Documentation/devicetree/bindings/memory-controllers/ddr/ |
| H A D | jedec,lpddr-channel.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/memory-controllers/ddr/jedec,lpddr-channel.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 CK, etc.) that connect one or more LPDDR chips to a host system. The main
12 purpose of this node is to overall LPDDR topology of the system, including the
13 amount of individual LPDDR chips and the ranks per chip.
16 - Julius Werner <jwerner@chromium.org>
21 - jedec,lpddr2-channel
22 - jedec,lpddr3-channel
[all …]
|
| /linux/drivers/net/can/sja1000/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
5 depends on HAS_IOMEM
10 tristate "EMS CPC-PCI, CPC-PCIe and CPC-104P Card"
11 depends on PCI
13 This driver is for the one, two or four channel CPC-PCI,
14 CPC-PCIe and CPC-104P cards from EMS Dr. Thomas Wuensche
15 (http://www.ems-wuensche.de).
18 tristate "EMS CPC-CARD Card"
19 depends on PCMCIA
21 This driver is for the one or two channel CPC-CARD cards from
[all …]
|
| /linux/drivers/spi/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
7 depends on HAS_IOMEM
10 protocol. Chips that support SPI can have data transfer rates
11 up to several tens of Mbit/sec. Chips are addressed with a
13 dynamic device discovery; some are even write-only or read-only.
17 chips, analo
[all...] |
| /linux/drivers/i2c/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
13 I2C (pronounce: I-squared-C) is a slow serial bus protocol used in
15 or System Management Bus is a subset of the I2C protocol. More
26 will be called i2c-core.
30 depends on I2C=y && ACPI
46 Say Y here to use i2c-* device files, usually found in the /dev
47 directory on your system. They make it possible to have user-space
48 programs use the I2C bus. Information on how to do this is
49 contained in the file <file:Documentation/i2c/dev-interface.rst>.
52 will be called i2c-dev.
[all …]
|
| /linux/Documentation/driver-api/ |
| H A D | edac.rst | 5 ----------------------------------------
8 *sockets, *socket sets*, *banks*, *rows*, *chip-select rows*, *channels*,
18 The individual DRAM chips on a memory stick. These devices commonly
32 A physical connector on the motherboard that accepts a single memory
33 stick. Also called as "slot" on several datasheets.
43 It is typically the highest hierarchy on a Fully-Buffered DIMM memory
50 of correcting more errors than on single mode.
52 * Single-channel
55 only. E. g. if the data is 64 bits-wide, the data flows to the CPU using
57 memories. FB-DIMM and RAMBUS use a different concept for channel, so
[all …]
|
| /linux/drivers/video/fbdev/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
14 a well-defined interface, so the software doesn't need to know
15 anything about the low-level (hardware register) stuff.
21 On several non-X86 architectures, the frame buffer device is the
29 and the Framebuffer-HOWTO at
30 <http://www.munted.org.uk/programming/Framebuffer-HOWT
[all...] |
| /linux/Documentation/i2c/ |
| H A D | summary.rst | 6 a protocol developed by Philips. It is a two-wire protocol with variable
14 The latest official I2C specification is the `"I²C-bus specification and user
15 manual" (UM10204) <https://www.nxp.com/docs/en/user-guide/UM10204.pdf>`_
18 SMBus (System Management Bus) is based on the I2C protocol, and is mostly
19 a subset of I2C protocols and signaling. Many I2C devices will work on an
21 achieve I2C branding. Modern PC mainboards rely on SMBus. The most common
23 and hardware monitoring chips.
26 use its protocols on many I2C systems. However, there are systems that don't
34 The I2C bus connects one or more controller chips and one or more target chips.
36 .. kernel-figure:: i2c_bus.svg
[all …]
|
| /linux/Documentation/admin-guide/ |
| H A D | rtc.rst | 7 works even with system power off. Such clocks will normally not track
8 the local time zone or daylight savings time -- unless they dual boot
9 with MS-Windows -- but will instead be set to Coordinated Universal Time
12 The newest non-PC hardware tends to just count seconds, like the time(2)
13 system call reports, but RTCs also very commonly represent time using
16 Linux has two largely-compatible userspace RTC API families you may
20 so it's not very portable to non-x86 systems.
23 supported by a wide variety of RTC chips on all systems.
35 Old PC/AT-Compatible driver: /dev/rtc
36 --------------------------------------
[all …]
|
| /linux/drivers/net/ethernet/dec/tulip/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
7 bool "DEC - Tulip devices"
8 depends on (PCI || EISA || CARDBUS)
16 depends on PCI
20 cards and also works with cards based on the DECchip
21 21040 (Tulip series) chips. Some LinkSys PCI cards are
32 depends on DE2104X
38 (the descriptor is 16 bytes). This is necessary on systems that lack
44 depends on PCI
48 cards and also works with cards based on the DECchip
[all …]
|
| /linux/drivers/thermal/ti-soc-thermal/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
6 OMAP4460+ on die bandgap temperature sensor support. The register
7 set is part of system control module.
14 depends on TI_SOC_THERMAL
17 framework for the Texas Instruments on die bandgap temperature sensor.
24 depends on TI_SOC_THERMAL
25 depends on ARCH_OMAP3 || COMPILE_TEST
28 OMAP3 SoC family. The current chips supported are:
29 - OMAP3430
31 OMAP3 chips normally don't need thermal management, and sensors in
[all …]
|