Home
last modified time | relevance | path

Searched refs:EC (Results 1 – 44 of 44) sorted by relevance

/linux-4.1.27/Documentation/devicetree/bindings/i2c/
Di2c-cros-ec-tunnel.txt1 I2C bus that tunnels through the ChromeOS EC (cros-ec)
3 On some ChromeOS board designs we've got a connection to the EC (embedded
5 the EC (like a battery and PMIC). To get access to those devices we need
6 to tunnel our i2c commands through the EC.
14 - google,remote-bus: The EC bus we'd like to talk to.
/linux-4.1.27/Documentation/devicetree/bindings/mfd/
Dcros-ec.txt3 Google's ChromeOS EC is a Cortex-M device which talks to the AP and
6 The EC can be connect through various means (I2C, SPI, LPC) and the
8 its own driver which connects to the top level interface-agnostic EC driver.
21 - google,cros-ec-spi-msg-delay: Some implementations of the EC require some
23 between transactions is not long enough the EC may not be able to respond
26 for the time required by the EC to get back into a state in which new data
/linux-4.1.27/Documentation/devicetree/bindings/input/
Dcros-ec-keyb.txt1 ChromeOS EC Keyboard
3 Google's ChromeOS EC Keyboard is a simple matrix keyboard implemented on
4 a separate EC (Embedded Controller) device. It provides a message for reading
5 key scans from the EC. These are then converted into keycodes for processing
15 keyboard. This is recommended if the EC does not have its own logic or
/linux-4.1.27/drivers/staging/nvec/
DREADME4 embedded controller (EC) via I2C bus. The EC is an I2C master while the host
5 processor is the I2C slave. Requests from the host processor to the EC are
DKconfig13 tristate "Keyboard on nVidia compliant EC"
23 tristate "PS2 on nVidia EC"
/linux-4.1.27/Documentation/ABI/testing/
Ddebugfs-ec6 General information like which GPE is assigned to the EC and whether
8 Knowing the EC GPE one can watch the amount of HW events related to
9 the EC here (XY -> GPE number from /sys/kernel/debug/ec/*/gpe):
/linux-4.1.27/Documentation/hwmon/
Dnct668331 Limit register locations on Intel boards with EC firmware version 1.0
55 Intel DH87RL NCT6683D EC firmware version 1.0 build 04/03/13
56 Intel DH87MC NCT6683D EC firmware version 1.0 build 04/03/13
57 Intel DB85FL NCT6683D EC firmware version 1.0 build 04/03/13
/linux-4.1.27/drivers/edac/
Dmce_amd.c294 u16 ec = EC(m->status); in decode_mc0_mce()
404 u16 ec = EC(m->status); in decode_mc1_mce()
550 u16 ec = EC(m->status); in decode_mc2_mce()
561 u16 ec = EC(m->status); in decode_mc3_mce()
592 u16 ec = EC(m->status); in decode_mc4_mce()
649 u16 ec = EC(m->status); in decode_mc5_mce()
Dmce_amd.h8 #define EC(x) ((x) & 0xffff) macro
Damd64_edac.c2184 u16 ec = EC(m->status); in decode_bus_error()
/linux-4.1.27/drivers/platform/chrome/
DKconfig45 This driver adds support to talk with the ChromeOS EC from userspace.
54 If you say Y here, you get support for talking to the ChromeOS EC
/linux-4.1.27/Documentation/input/
Dalps.txt45 seem to be better differentiated by the EC Command Mode response.
52 EC-EC-EC-E9 places the device in command mode, and the device will respond
59 specific command, either EC for v3 devices or F5 for v4 devices. Then the
70 For the new ALPS touchpads, the EC command is used to enter command
76 of the EC response.
/linux-4.1.27/arch/ia64/kernel/
Dparavirt.c181 CASE_GET_AR(EC); in ia64_native_getreg_func()
261 CASE_SET_AR(EC); in ia64_native_setreg_func()
441 __DEFINE_GET_AR(EC, ec)
524 __DEFINE_SET_AR(EC, ec)
834 IA64_NATIVE_PATCH_BUNDLE_ELEM_AR(ec, EC),
/linux-4.1.27/sound/pci/ali5451/
Dali5451.c1001 unsigned int EC) in snd_ali_write_voice_regs() argument
1014 (EC & 0x00000fff); in snd_ali_write_voice_regs()
1226 unsigned int EC; in snd_ali_playback_prepare() local
1266 EC = 0; in snd_ali_playback_prepare()
1282 EC); in snd_ali_playback_prepare()
1298 EC); in snd_ali_playback_prepare()
1317 unsigned int EC; in snd_ali_prepare() local
1372 EC = 0; in snd_ali_prepare()
1385 EC); in snd_ali_prepare()
/linux-4.1.27/Documentation/x86/
Dzero-page.txt37 D00/1EC ALL eddbuf EDD data (array of struct edd_info)
/linux-4.1.27/Documentation/i2c/busses/
Di2c-nforce248 the driver to work with direct I/O access, which is different to the EC
/linux-4.1.27/sound/pci/trident/
Dtrident_main.c464 (voice->EC & 0x00000fff); in snd_trident_write_voice_regs()
472 (voice->EC & 0x00000fff); in snd_trident_write_voice_regs()
480 (voice->EC & 0x00000fff); in snd_trident_write_voice_regs()
972 voice->EC = 0; in snd_trident_playback_prepare()
998 evoice->EC = 0; in snd_trident_playback_prepare()
1119 voice->EC = 0; in snd_trident_capture_prepare()
1213 voice->EC = 0; in snd_trident_si7018_capture_prepare()
1233 evoice->EC = 0; in snd_trident_si7018_capture_prepare()
1291 voice->EC = 0; in snd_trident_foldback_prepare()
1310 evoice->EC = 0; in snd_trident_foldback_prepare()
[all …]
Dtrident.h292 unsigned short EC; /* 12 bits */ member
/linux-4.1.27/Documentation/laptops/
Dthinkpad-acpi.txt13 through the ACPI and ACPI EC framework, but not otherwise fully
914 Instead the EC can be accessed through /sys/kernel/debug/ec with
922 - use above mentioned tool to read out the EC
956 brightness control, EC and UCMS (or CMOS). To select which one should be
958 EC mode, brightness_mode=2 selects UCMS mode, brightness_mode=3 selects EC
1121 selects EC mode, and volume_mode=3 selects EC mode with NVRAM backing
1160 Level "auto" means the EC changes the fan level according to some
1164 In this level, the EC disables the speed-locked closed-loop fan control,
1169 it is normal for the EC to take several seconds to react to fan
1172 while the EC is transitioning to the full-speed level.
[all …]
/linux-4.1.27/drivers/acpi/
DKconfig81 tristate "EC read/write access through /sys/kernel/debug/ec"
92 The kernel accesses the EC through ACPI parsed code provided by BIOS
93 tables. This option allows to access the EC directly without ACPI
96 and can be used to identify ACPI code or EC firmware bugs.
/linux-4.1.27/Documentation/devicetree/bindings/regulator/
Dtps65090.txt27 "overcurrent wait" field and we'll leave it to the BIOS/EC to deal with.
/linux-4.1.27/drivers/net/ethernet/
Dfealnx.c277 EC = 0x00000800, /* excessive collision */ enumerator
1509 if (tx_status & (CSL | LC | EC | UDF | HF)) { in intr_handler()
1511 if (tx_status & EC) in intr_handler()
/linux-4.1.27/drivers/mfd/
DKconfig99 Controller (EC) providing keyboard, battery and power services.
101 protocol for talking to the EC is defined by the bus driver.
109 EC through an I2C bus. This uses a simple byte-level protocol with
118 If you say Y here, you get support for talking to the ChromeOS EC
119 through a SPI bus, using a byte-level protocol. Since the EC's
/linux-4.1.27/firmware/radeon/
DR600_me.bin.ihex1158 :1048500000000000000000000020480400000000EC
DRV670_me.bin.ihex1125 :1046400000000000000000050020481100000000EC
/linux-4.1.27/Documentation/arm/pxa/
Dmfp.txt160 | RESERVED |PS|PU|PD| DRIVE |SS|SD|SO|EC|EF|ER|--| AF_SEL |
/linux-4.1.27/drivers/input/keyboard/
DKconfig678 tristate "ChromeOS EC keyboard"
683 and implemented on the ChromeOS EC. You must enable one bus option
/linux-4.1.27/drivers/i2c/busses/
DKconfig1105 tristate "ChromeOS EC tunnel I2C bus"
1109 through to the other side of the ChromeOS EC to the i2c bus
1111 talk to the EC (SPI, I2C or LPC).
/linux-4.1.27/Documentation/ioctl/
Dioctl-number.txt324 0xEC 00-01 drivers/platform/chrome/cros_ec_dev.h ChromeOS EC driver
/linux-4.1.27/drivers/net/ethernet/apm/xgene/
Dxgene_enet_main.c219 SET_VAL(EC, csum_enable) | in xgene_enet_work_msg()
/linux-4.1.27/drivers/eisa/
Deisa.ids1203 STL0400 "Stallion Technologies - EC 8/64-EI"
1204 STL0410 "Stallion Technologies - EC 8/32-AT"
1205 STL0420 "Stallion Technologies - EC 8/64-AT"
/linux-4.1.27/firmware/bnx2x/
Dbnx2x-e1-6.2.9.0.fw.ihex1029 :1040400005250555000000000000000000000000EC
4097 :020000021000EC
9287 :1044400080000000000000000000000000000000EC
Dbnx2x-e2-6.2.9.0.fw.ihex906 :1038900002164240000000000216424800000000EC
4097 :020000021000EC
Dbnx2x-e1h-6.2.9.0.fw.ihex4097 :020000021000EC
/linux-4.1.27/
DCREDITS237 P: 1024/FA6F16D1 96 D1 1A CF 5F CA 69 EC F9 4F 36 1F 6D 60 7B DA
531 P: 4096R/566281B9 1BC6 29EB D390 D870 7B5F 497A 39EC 9EDD 5662 81B9
1733 P: 1024/4536A8DD 2A EC 88 08 40 64 CE D8 DD F8 12 2B 61 43 83 15
3605 P: 1024/E7A417AD E2 FE A4 20 34 EC ED FC 7D 7E 67 8D E0 31 D1 69
/linux-4.1.27/firmware/acenic/
Dtg1.bin.ihex4097 :020000021000EC
Dtg2.bin.ihex4097 :020000021000EC
/linux-4.1.27/firmware/emi26/
Dbitstream.HEX4166 :1084800000000000000000000000000000000000EC
/linux-4.1.27/firmware/myricom/
Dlanai.bin.ihex4097 :020000021000EC
/linux-4.1.27/firmware/bnx2/
Dbnx2-mips-06-6.2.1.fw.ihex4877 :1030300000001821308200011040000200042042EC
Dbnx2-mips-09-6.2.1a.fw.ihex5514 :1058100010800007000000003082000110400002EC
/linux-4.1.27/arch/x86/
DKconfig2407 - EC-driven system wakeups
2420 - EC-driven system wakeups
/linux-4.1.27/Documentation/
Dkernel-parameters.txt2548 olpc_ec_timeout= [OLPC] ms delay when issuing EC commands
2549 Rather than timing out after 20 ms if an EC
/linux-4.1.27/Documentation/s390/
DDebugging390.txt1522 CCWA 000FFDF8 DEV STS 0C SCH STS 00 CNT 00EC