Home
last modified time | relevance | path

Searched refs:via (Results 1 – 25 of 236) sorted by relevance

12345678910

/drivers/macintosh/
Dvia-cuda.c35 static volatile unsigned char __iomem *via; variable
111 out_8(&via[B], in_8(&via[B]) | TIP); in assert_TIP()
113 out_8(&via[B], in_8(&via[B]) & ~TIP); in assert_TIP()
120 out_8(&via[B], in_8(&via[B]) | TIP | TACK); in assert_TIP_and_TACK()
122 out_8(&via[B], in_8(&via[B]) & ~(TIP | TACK)); in assert_TIP_and_TACK()
129 out_8(&via[B], in_8(&via[B]) | TACK); in assert_TACK()
131 out_8(&via[B], in_8(&via[B]) & ~TACK); in assert_TACK()
136 out_8(&via[B], in_8(&via[B]) ^ TACK); in toggle_TACK()
143 out_8(&via[B], in_8(&via[B]) & ~TACK); in negate_TACK()
145 out_8(&via[B], in_8(&via[B]) | TACK); in negate_TACK()
[all …]
Dvia-macii.c37 static volatile unsigned char *via; variable
134 via = via1; in macii_probe()
164 via[DIRB] = (via[DIRB] | ST_EVEN | ST_ODD) & ~CTLR_IRQ; in macii_init_via()
167 via[B] |= ST_IDLE; in macii_init_via()
170 via[ACR] = (via[ACR] & ~SR_CTRL) | SR_EXT; in macii_init_via()
173 x = via[SR]; in macii_init_via()
334 via[ACR] |= SR_OUT; in macii_start()
336 via[SR] = req->data[1]; in macii_start()
338 via[B] = (via[B] & ~ST_MASK) | ST_CMD; in macii_start()
375 if (via[IFR] & SR_INT) in macii_interrupt()
[all …]
DMakefile15 obj-$(CONFIG_ADB_PMU) += via-pmu.o
16 obj-$(CONFIG_ADB_PMU_EVENT) += via-pmu-event.o
17 obj-$(CONFIG_ADB_PMU_LED) += via-pmu-led.o
18 obj-$(CONFIG_PMAC_BACKLIGHT) += via-pmu-backlight.o
19 obj-$(CONFIG_ADB_CUDA) += via-cuda.o
24 obj-$(CONFIG_ADB_MACII) += via-macii.o
/drivers/iio/imu/bno055/
DKconfig9 tristate "Bosch BNO055 attached via UART"
14 Enable this to support Bosch BNO055 IMUs attached via UART.
20 tristate "Bosch BNO055 attached via I2C bus"
25 Enable this to support Bosch BNO055 IMUs attached via I2C bus.
/drivers/misc/lis3lv02d/
DKconfig12 via SPI. The accelerometer data is readable via
28 via I2C. The accelerometer data is readable via
/drivers/gpu/drm/i915/
DKconfig.profile49 This is adjustable via
64 This is adjustable via
83 This is adjustable via
102 This is adjustable via
120 This is adjustable via
132 interact with each other via userspace semaphores. Each context
136 This is adjustable via
/drivers/remoteproc/
DKconfig32 Say y here to support iMX's remote processors via the remote
43 Say y here to support iMX's DSP remote processors via the remote
62 Say y here to support Mediatek's System Companion Processor (SCP) via
75 and DSP on OMAP4) via the remote processor framework.
115 Say y here to support DA8xx/OMAP-L13x remote processors via the
124 directory. It can be specified via the module parameter
136 via the remote processor framework.
158 subsystem via the remote processor framework.
294 Say y here to support R-Car realtime processor via the
307 Say y here to support ST's adjunct processors via the remote
[all …]
/drivers/net/ethernet/via/
DMakefile6 obj-$(CONFIG_VIA_RHINE) += via-rhine.o
7 obj-$(CONFIG_VIA_VELOCITY) += via-velocity.o
/drivers/most/
DKconfig22 Say Y here if you want to connect via USB to network transceiver.
31 Say Y here if you want to commumicate via character devices.
41 Say Y here if you want to commumicate via ALSA/sound devices.
/drivers/staging/most/Documentation/
Ddriver_usage.txt19 consumer devices via optical or electrical physical layers directly to one
47 Applications, then, can access a MOST network via character devices, an
66 Host wants to communicate with hardware via MediaLB.
69 Host wants to communicate with the hardware via I2C.
72 Host wants to communicate with the hardware via USB.
105 the driver via the networking subsystem.
109 driver via the V4L subsystem.
113 used to access the driver via the ALSA subsystem.
120 The driver is to be configured via configfs. Each loaded component kernel
144 network before being transmitted via USB (this is used for USB
/drivers/staging/fieldbus/Documentation/
Dfieldbus_dev.txt15 logic controllers (PLC) via a non-time-critical communications system
23 controlled via the Fieldbus by a PLC aka "Fieldbus Controller".
25 Communication between PLC and device typically happens via process data memory,
33 exchange with a PLC aka "Fieldbus Controller" via process data memory.
/drivers/video/fbdev/via/
DMakefile10 via-core.o via-gpio.o via_modesetting.o via_clock.o \
/drivers/net/wwan/
DKconfig46 (e.g. AT commands) or via libraries/tools (e.g. libmbim, libqmi,
59 ID 0. Additional links can be created via wwan rtnetlink type.
70 MSM8916 or MSM8974. The connection can be established via QMI/AT from
81 RPMSG WWAN CTRL allows modems available via RPMSG channels to expose
84 (e.g. AT commands) or via libraries/tools (e.g. libqmi, libqcdm...).
/drivers/platform/x86/intel/ifs/
DKconfig6 CPUs. The capability allows for running low level tests via
7 a scan image distributed by Intel via Github to validate CPU
/drivers/powercap/
DKconfig25 tristate "Intel RAPL Support via MSR Interface"
30 technology via MSR interface, which allows power limits to be enforced
39 tristate "Intel RAPL Support via TPMI Interface"
45 technology via TPMI interface, which allows power limits to be enforced
/drivers/dma-buf/
DKconfig9 The Sync File Framework adds explicit synchronization via
11 userspace via Sync File fds for synchronization between drivers via
16 is attached to the buffer and is transferred via userspace, using Sync
/drivers/misc/cxl/
DKconfig20 coherently attached to a CPU via an MMU. This driver enables
21 userspace programs to access these accelerators via /dev/cxl/afuM.N
/drivers/platform/surface/
DKconfig90 Devices managed via these hubs are:
101 via the Surface Aggregator Registry) for these devices still need to be
102 selected via other options.
112 client devices that cannot be detected automatically, e.g. via ACPI.
113 Such devices are instead provided and managed via this registry.
115 Devices provided via this registry are:
127 be selected via the other options.
213 (SSAM) connected via the Surface Serial Hub (SSH / SAM-over-SSH). In
/drivers/staging/iio/frequency/
DKconfig12 AD9832 and AD9835, provides direct access via sysfs.
22 AD9833, AD9834, AD9837 and AD9838, provides direct access via sysfs.
/drivers/iio/cdc/
DKconfig12 (ad7150, ad7151, ad7156) Provides direct access via sysfs.
22 (AD7745, AD7746, AD7747) Provides direct access via sysfs.
/drivers/iio/resolver/
DKconfig12 to digital converters, ad2s90, provides direct access via sysfs.
24 via sysfs.
/drivers/mtd/nand/onenand/
DKconfig21 tristate "OneNAND Flash device via platform device driver"
23 Support for OneNAND flash via platform device driver.
32 via the GPMC memory controller.
/drivers/net/wireless/st/cw1200/
DKconfig16 Enable support for the CW1200 connected via an SDIO bus.
27 Enables support for the CW1200 connected via a SPI bus. You will
/drivers/firmware/
DKconfig38 enabled or disabled via the SCP firmware
55 BIOS tries boot from. This information is then exported via sysfs.
81 bool "Console device selection via EFI PCDP or HCDP table"
105 bool "Export DMI identification via sysfs to userspace"
119 data via sysfs. This is useful for consuming the data without
145 Boot Firmware Table (iBFT) via sysfs to userspace. If you wish to
163 configuration (fw_cfg) file entries via sysfs. Entries are
171 Allow the qemu_fw_cfg device to be initialized via the kernel
193 access through the Intel Service Layer to user space via sysfs
/drivers/thermal/mediatek/
DKconfig19 temperature via AUXADC interface.
28 thermal controllers to collect temperatures via ASIF

12345678910