| /drivers/media/i2c/ |
| D | ar0521.c | 70 #define be cpu_to_be16 macro
165 __be16 buf[2] = {be(reg), be(val)}; in ar0521_write_reg()
176 be(AR0521_REG_FRAME_LENGTH_LINES), in ar0521_set_geometry()
177 be(sensor->total_height), in ar0521_set_geometry()
178 be(sensor->total_width), in ar0521_set_geometry()
179 be(x), in ar0521_set_geometry()
180 be(y), in ar0521_set_geometry()
181 be(x + sensor->fmt.width - 1), in ar0521_set_geometry()
182 be(y + sensor->fmt.height - 1), in ar0521_set_geometry()
183 be(sensor->fmt.width), in ar0521_set_geometry()
[all …]
|
| /drivers/net/xen-netback/ |
| D | xenbus.c | 13 static int connect_data_rings(struct backend_info *be,
15 static void connect(struct backend_info *be);
16 static int read_xenbus_vif_flags(struct backend_info *be);
17 static int backend_create_xenvif(struct backend_info *be);
18 static void unregister_hotplug_status_watch(struct backend_info *be);
20 static void set_backend_state(struct backend_info *be,
206 struct backend_info *be = dev_get_drvdata(&xdev->dev); in netback_uevent() local
208 if (!be) in netback_uevent()
211 if (add_uevent_var(env, "script=%s", be->hotplug_script)) in netback_uevent()
214 if (!be->vif) in netback_uevent()
[all …]
|
| /drivers/block/xen-blkback/ |
| D | xenbus.c | 38 struct xenbus_device *xen_blkbk_xenbus(struct backend_info *be) in xen_blkbk_xenbus() argument
40 return be->dev; in xen_blkbk_xenbus()
58 struct xenbus_device *dev = blkif->be->dev; in blkback_name()
88 if (blkif->be->dev->state == XenbusStateConnected) in xen_update_blkif_status()
92 connect(blkif->be); in xen_update_blkif_status()
93 if (blkif->be->dev->state != XenbusStateConnected) in xen_update_blkif_status()
98 xenbus_dev_error(blkif->be->dev, err, "get blkback dev name"); in xen_update_blkif_status()
104 xenbus_dev_error(blkif->be->dev, err, "block flush"); in xen_update_blkif_status()
115 xenbus_dev_fatal(blkif->be->dev, err, in xen_update_blkif_status()
205 err = xenbus_map_ring_valloc(blkif->be->dev, gref, nr_grefs, in xen_blkif_map()
[all …]
|
| /drivers/hwmon/pmbus/ |
| D | Kconfig | 12 This driver can also be built as a module. If so, the module will
13 be called pmbus_core.
27 This driver can also be built as a module. If so, the module will
28 be called pmbus.
38 This driver can also be built as a module. If so, the module will
39 be called adm1266.
48 This driver can also be built as a module. If so, the module will
49 be called adm1275.
57 This driver can also be built as a module. If so, the module will
58 be called bel-pfe.
[all …]
|
| /drivers/hwmon/ |
| D | Kconfig | 23 This support can also be built as a module. If so, the module
24 will be called hwmon.
48 chip can be found on Abit uGuru featuring motherboards (most modern
53 This driver can also be built as a module. If so, the module
54 will be called abituguru.
63 uGuru chip can be found on recent Abit motherboards (since end
67 This driver can also be built as a module. If so, the module
68 will be called abituguru3.
77 This driver can also be built as a module. If so, the module
78 will be called ad7314.
[all …]
|
| /drivers/i2c/busses/ |
| D | Kconfig | 23 If you say yes to this option, support will be included for the SMB
28 This driver can also be built as a module. If so, the module
29 will be called i2c-ali1535.
35 If you say yes to this option, support will be included for the SMB
40 This driver can also be built as a module. If so, the module
41 will be called i2c-ali1563.
47 If you say yes to this option, support will be included for the
50 This driver can also be built as a module. If so, the module
51 will be called i2c-ali15x3.
57 If you say yes to this option, support will be included for the AMD
[all …]
|
| /drivers/rtc/ |
| D | Kconfig | 20 be allowed to plug one or more RTCs to your system. You will
29 If you say yes here, the system time (wall clock) will be set using
38 The RTC device that will be used to (re)initialize the system
44 This clock should be battery-backed, so that it reads the correct
49 be useful to reinitialize system time when resuming from system
57 If you say yes here, the system time (wall clock) will be stored
114 Other RTCs will not be available through that API.
129 can be accessed as /dev/rtc, which is a name
151 RTC test driver. It's a software RTC which can be
158 This driver can also be built as a module. If so, the module
[all …]
|
| /drivers/i2c/muxes/ |
| D | Kconfig | 14 If you say yes to this option, support will be included for an
19 This driver can also be built as a module. If so, the module
20 will be called i2c-arb-gpio-challenge.
26 If you say yes to this option, support will be included for a
31 This driver can also be built as a module. If so, the module
32 will be called i2c-mux-gpio.
39 If you say yes to this option, support will be included for a
44 This driver can also be built as a module. If so, the module
45 will be called i2c-mux-gpmux.
55 This driver can also be built as a module. If so, the module
[all …]
|
| /drivers/net/phy/ |
| D | mdio-boardinfo.c | 29 struct mdio_board_entry *be; in mdiobus_setup_mdiodev_from_board_info() local
35 list_for_each_entry_safe(be, tmp, &mdio_board_list, list) { in mdiobus_setup_mdiodev_from_board_info()
36 bi = &be->board_info; in mdiobus_setup_mdiodev_from_board_info()
64 struct mdio_board_entry *be; in mdiobus_register_board_info() local
67 be = kcalloc(n, sizeof(*be), GFP_KERNEL); in mdiobus_register_board_info()
68 if (!be) in mdiobus_register_board_info()
71 for (i = 0; i < n; i++, be++, info++) { in mdiobus_register_board_info()
72 memcpy(&be->board_info, info, sizeof(*info)); in mdiobus_register_board_info()
74 list_add_tail(&be->list, &mdio_board_list); in mdiobus_register_board_info()
|
| /drivers/iio/adc/ |
| D | Kconfig | 39 To compile this driver as a module, choose M here: the module will be
52 module will be called ad7192.
64 To compile this driver as a module, choose M here: the module will be
76 module will be called ad7280a
86 module will be called ad7291.
96 module will be called ad7292.
108 module will be called ad7298.
124 module will be called ad7476.
140 module will be called ad7606_parallel.
151 module will be called ad7606_spi.
[all …]
|
| /drivers/nvmem/ |
| D | Kconfig | 35 This driver can also be built as a module. If so, the module will
36 be called nvmem-apple-efuses.
47 This driver can also be built as a module. If so, the module
48 will be called nvmem-bcm-ocotp.
55 This driver provides support for Broadcom's NVRAM that can be accessed
66 This driver can also be built as a module. If so, the module
67 will be called nvmem-imx-iim.
78 This driver can also be built as a module. If so, the module
79 will be called nvmem-imx-ocotp.
99 will be called nvmem_jz4780_efuse.
[all …]
|
| /drivers/iio/temperature/ |
| D | Kconfig | 15 will be called iqs620at-temp.
26 will be called ltc2983.
41 This driver can also be built as a module. If so, the module will
42 be called maxim_thermocouple.
55 will be called hid-sensor-temperature.
64 This driver can also be built as a module. If so, the module will
65 be called mlx90614.
76 This driver can also be built as a module. If so, the module will
77 be called mlx90632.
86 This driver can also be built as a module. If so, the module will
[all …]
|
| /drivers/staging/axis-fifo/ |
| D | axis-fifo.txt | 4 be accessed from the AXI4 memory-mapped interface. This is useful for
6 a character device that can be read/written to with standard
17 - compatible: Should be "xlnx,axi-fifo-mm-s-4.1"
18 - interrupt-names: Should be "interrupt"
19 - interrupt-parent: Should be <&intc>
22 - xlnx,axi-str-rxd-protocol: Should be "XIL_AXI_STREAM_ETH_DATA"
23 - xlnx,axi-str-rxd-tdata-width: Should be <0x20>
24 - xlnx,axi-str-txc-protocol: Should be "XIL_AXI_STREAM_ETH_CTRL"
25 - xlnx,axi-str-txc-tdata-width: Should be <0x20>
26 - xlnx,axi-str-txd-protocol: Should be "XIL_AXI_STREAM_ETH_DATA"
[all …]
|
| /drivers/net/ieee802154/ |
| D | Kconfig | 11 If you say N, all options in this submenu will be skipped and
21 This driver can also be built as a module. To do so say M here.
22 The module will be called 'fakelb'.
33 This driver can also be built as a module. To do so, say M here.
34 the module will be called 'at86rf230'.
45 This driver can also be built as a module. To do so, say M here.
46 the module will be called 'mrf24j40'.
56 This driver can also be built as a module. To do so, say M here.
57 the module will be called 'cc2520'.
66 This driver can also be built as a module. To do so say M here.
[all …]
|
| /drivers/char/tpm/ |
| D | Kconfig | 15 say Yes and it will be accessible from within Linux. For
18 userspace enablement piece of the specification, can be
21 will be called tpm. If unsure, say N.
25 2) Without ACPI enabled, the BIOS event log won't be accessible,
54 specification (TPM2.0) say Yes and it will be accessible from
56 the module will be called tpm_tis.
66 specification (TPM2.0) say Yes and it will be accessible from
68 the module will be called tpm_tis_spi.
75 say Yes and it will be accessible from within Linux.
85 say Yes and it will be accessible from within Linux.
[all …]
|
| /drivers/comedi/ |
| D | Kconfig | 30 be requested by a userspace program without root privileges.
37 Enable comedi misc drivers to be built
54 To compile this driver as a module, choose M here: the module will be
61 This driver is mainly for testing purposes, but can also be used to
65 To compile this driver as a module, choose M here: the module will be
76 To compile this driver as a module, choose M here: the module will be
85 To compile this driver as a module, choose M here: the module will be
93 Enable comedi ISA and PC/104 drivers to be built
107 To compile this driver as a module, choose M here: the module will be
128 To compile this driver as a module, choose M here: the module will be
[all …]
|
| /drivers/iio/light/ |
| D | Kconfig | 21 be called acpi-als.
32 This driver can also be built as a module. If so, the module
33 will be called adjd_s311.
44 module will be called adux1020.
54 module will be called al3010.
64 module will be called al3320a.
74 module will be called apds9300.
87 module will be called apds9960
101 This driver can also be built as a module. If so, the module
102 will be called as73211.
[all …]
|
| /drivers/input/misc/ |
| D | Kconfig | 8 Say Y here, and a list of miscellaneous input drivers will be displayed.
24 will be called 88pm860x_onkey.
34 will be called 88pm80x_onkey.
44 will be called ab8500-ponkey.
54 module will be called ad714x.
64 module will be called ad714x-i2c.
74 module will be called ad714x-spi.
85 will be called ariel-pwrbutton.
95 module will be called arizona-haptics.
102 power button status. ONKEY can be used to wakeup from low power
[all …]
|
| /drivers/iio/dac/ |
| D | Kconfig | 17 module will be called ad3552r.
31 module will be called ad5064.
41 To compile this driver as module choose M here: the module will be called
54 To compile this driver as module choose M here: the module will be called
64 To compile this driver as module choose M here: the module will be called
78 module will be called ad5446.
88 module will be called ad5449.
103 module will be called ad5592r.
115 module will be called ad5593r.
125 module will be called ad5504.
[all …]
|
| /drivers/media/usb/gspca/ |
| D | Kconfig | 17 module will be called gspca_main.
28 module will be called gspca_benq.
37 module will be called gspca_conex.
48 module will be called gspca_cpia1.
58 module will be called gspca_dtcs033.
67 module will be called gspca_etoms.
76 module will be called gspca_finepix.
85 module will be called gspca_jeilinj.
95 module will be called gspca_jl2005bcd.
104 module will be called gspca_kinect.
[all …]
|
| /drivers/misc/eeprom/ |
| D | Kconfig | 21 Unless you like data loss puzzles, always be sure that any chip
32 This driver can also be built as a module. If so, the module
33 will be called at24.
46 This driver can also be built as a module. If so, the module
47 will be called at25.
55 EEPROMs could theoretically be available on other devices as well.
57 This driver is deprecated and will be removed soon, please use the
60 This driver can also be built as a module. If so, the module
61 will be called eeprom.
71 All other features of this chip should be accessed via i2c-dev.
[all …]
|
| /drivers/leds/trigger/ |
| D | Kconfig | 8 be configured via sysfs. If unsure, say Y.
15 This allows LEDs to be controlled by a programmable timer
16 via sysfs. Some LED hardware can be programmed to start
39 This allows LEDs to be controlled by disk activity.
46 This allows LEDs to be controlled by MTD activity.
52 This allows LEDs to be controlled by a CPU load average.
60 This allows LEDs to be controlled as a backlight device: they
69 This allows LEDs to be controlled by active CPUs. This shows
78 This allows LEDs to be controlled by an immediate CPU usage.
87 This allows LEDs to be controlled by gpio events. It's good
[all …]
|
| /drivers/input/touchscreen/ |
| D | Kconfig | 8 Say Y here, and a list of supported touchscreens will be displayed.
25 module will be called 88pm860x-ts.
44 module will be called ads7846.
57 module will be called ad7877.
68 module will be called ad7879.
78 module will be called ad7879-i2c.
90 module will be called ad7879-spi.
104 module will be called resistive-adc-touch.ko.
116 module will be called ar1021_i2c.
129 module will be called atmel_mxt_ts.
[all …]
|
| /drivers/staging/greybus/Documentation/firmware/ |
| D | firmware-management | 50 device interface. The character device will be present in /dev/ directory
51 and will be named gb-fw-mgmt-<N>. The number <N> is assigned at runtime.
56 There can be multiple devices present in /dev/ directory with name gb-fw-mgmt-N
61 be used by the user to identify the right character device for it. The class
64 For example this is how the class-device can be present:
69 device and so the device in this case will be:
76 The Character device (gb-fw-mgmt-0 in example) can be opened by the userspace
142 This ioctl shall be used by the user to get the version and firmware-tag of
148 This ioctl shall be used by the user to get the version of a currently
156 This ioctl shall be used by the user to load an Interface Firmware package on
[all …]
|
| /drivers/pwm/ |
| D | Kconfig | 52 will be called pwm-ab8500.
62 will be called pwm-atmel.
74 will be called pwm-atmel-hlcdc.
87 will be called pwm-atmel-tcb.
99 will be called pwm-bcm-iproc.
110 will be called pwm-bcm-kona.
120 will be called pwm-bcm2835.
130 will be called pwm-berlin.
141 will be called pwm-brcmstb.c.
147 Generic PWM framework driver for outputs that can be
[all …]
|