Searched +full:0 +full:x23 (Results 1 – 17 of 17) sorted by relevance
/Documentation/devicetree/bindings/iio/light/ |
D | bh1750.yaml | 37 #size-cells = <0>; 41 reg = <0x23>;
|
/Documentation/leds/ |
D | leds-mlxcpld.rst | 28 - CPLD reg offset: 0x20 29 - Bits [3:0] 32 - CPLD reg offset: 0x20 36 - CPLD reg offset: 0x21 37 - Bits [3:0] 40 - CPLD reg offset: 0x21 44 - CPLD reg offset: 0x22 45 - Bits [3:0] 48 - CPLD reg offset: 0x22 56 - [0,0,0,0] = LED OFF [all …]
|
/Documentation/hwmon/ |
D | ltc4245.rst | 10 Addresses scanned: 0x20-0x3f 34 Example: the following will load the driver for an LTC4245 at address 0x23 38 $ echo ltc4245 0x23 > /sys/bus/i2c/devices/i2c-1/new_device
|
D | w83781d.rst | 10 Addresses scanned: I2C 0x28 - 0x2f, ISA 0x290 (8 I/O ports) 18 Addresses scanned: I2C 0x28 - 0x2f, ISA 0x290 (8 I/O ports) 26 Addresses scanned: I2C 0x2d 34 Addresses scanned: I2C 0x28 - 0x2f 52 Use 'init=0' to bypass initializing the chip. 56 (default 0) 62 a certain chip. Typical usage is `force_subclients=0,0x2d,0x4a,0x4b` 63 to force the subclients of chip 0x2d on bus 0 to i2c addresses 64 0x4a and 0x4b. This parameter is useful for certain Tyan boards. 80 | as99127f | 7 | 3 | 0 | 3 | 0x31 | 0x12c3 | yes | no | [all …]
|
D | abituguru-datasheet.rst | 34 0xE0 and 0xE4, so we don't have to scan any port-range, just check what the two 35 ports are holding for detection. We will refer to 0xE0 as CMD (command-port) 36 and 0xE4 as DATA because Abit refers to them with these names. 38 If DATA holds 0x00 or 0x08 and CMD holds 0x00 or 0xAC an uGuru could be 40 after a reboot uGuru will hold 0x00 here, but if the driver is removed and 41 later on attached again data-port will hold 0x08, more about this later. 44 turned up which will hold 0x00 instead of 0xAC at the CMD port, thus we also 46 hold 0x09 and will only hold 0x08 after reading CMD first, so CMD must be read 72 bank 0x24 for example the addressing within the bank selects a PWM output not 87 To put the uGuru in ready mode first write 0x00 to DATA and then wait for DATA [all …]
|
/Documentation/devicetree/bindings/pinctrl/ |
D | brcm,nsp-gpio.txt | 14 bit[0]: polarity (0 for active high and 1 for active low) 20 Number of gpios supported (58x25 supports 32 and 58x23 supports 24) 58 reg = <0x18000020 0x100>, 59 <0x1803f1c4 0x1c>; 63 gpio-ranges = <&pinctrl 0 0 31>; 69 pinctrl-0 = <&led>;
|
/Documentation/devicetree/bindings/media/xilinx/ |
D | xlnx,csi2rxss.yaml | 53 0x1e - YUV4228B 54 0x1f - YUV42210B 55 0x20 - RGB444 56 0x21 - RGB555 57 0x22 - RGB565 58 0x23 - RGB666 59 0x24 - RGB888 60 0x28 - RAW6 61 0x29 - RAW7 62 0x2a - RAW8 [all …]
|
/Documentation/fault-injection/ |
D | nvme-fault-injection.rst | 33 name fault_inject, interval 1, probability 100, space 0, times 1 34 CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.15.0-rc8+ #2 39 dump_stack+0x5c/0x7d 40 should_fail+0x148/0x170 41 nvme_should_fail+0x2f/0x50 [nvme_core] 42 nvme_process_cq+0xe7/0x1d0 [nvme] 43 nvme_irq+0x1e/0x40 [nvme] 44 __handle_irq_event_percpu+0x3a/0x190 45 handle_irq_event_percpu+0x30/0x70 46 handle_irq_event+0x36/0x60 [all …]
|
/Documentation/devicetree/bindings/net/wireless/ |
D | qcom,ath10k.txt | 95 - qcom,coexist-support : should contain eithr "0" or "1" to indicate coex 116 pcie@0 { 117 reg = <0 0 0 0 0>; 123 wifi@0,0 { 124 reg = <0 0 0 0 0>; 135 reg = <0xa000000 0x200000>; 154 interrupts = <0 0x20 0x1>, 155 <0 0x21 0x1>, 156 <0 0x22 0x1>, 157 <0 0x23 0x1>, [all …]
|
/Documentation/admin-guide/media/ |
D | philips.rst | 98 parameter between 0 and 3:: 100 0 = prefer uncompressed images; if the requested mode is not available 125 leds=0,0 170 dev_hint=645.0123:3,645.4567:0 The PCA645 camera with serialnumber 204 1 0x1 Module initialization; this will log messages On 207 2 0x2 probe() and disconnect() traces On 209 4 0x4 Trace open() and close() calls Off 211 8 0x8 read(), mmap() and associated ioctl() calls Off 213 16 0x10 Memory allocation of buffers, etc. Off 215 32 0x20 Showing underflow, overflow and Dumping frame On [all …]
|
D | bttv.rst | 72 00:0a.0 Multimedia video controller: Brooktree Corporation Bt878 (rev 02) 133 radio=0/1 card supports radio 134 pll=0/1/2 pll settings 136 0: don't use PLL 140 triton1=0/1 for Triton1 (+others) compatibility 141 vsfx=0/1 yet another chipset bug compatibility bit 146 fieldnr=0/1 Count fields. Some TV descrambling software 148 50 useless IRQs/sec. default is 0 (off). 149 autoload=0/1 autoload helper modules (tuner, audio). 151 bttv_verbose=0/1/2 verbose level (at insmod time, while [all …]
|
/Documentation/input/devices/ |
D | alps.rst | 32 E8-E6-E6-E6-E9. An ALPS touchpad should respond with either 00-00-0A or 33 00-00-64 if no buttons are pressed. The bits 0-2 of the first byte will be 1s 45 The new ALPS touchpads have an E7 signature of 73-03-50 or 73-03-0A but 94 byte 0: 0 0 YSGN XSGN 1 M R L 109 byte 0: 1 0 0 0 1 x9 x8 x7 110 byte 1: 0 x6 x5 x4 x3 x2 x1 x0 111 byte 2: 0 ? ? l r ? fin ges 112 byte 3: 0 ? ? ? ? y9 y8 y7 113 byte 4: 0 y6 y5 y4 y3 y2 y1 y0 114 byte 5: 0 z6 z5 z4 z3 z2 z1 z0 [all …]
|
/Documentation/admin-guide/ |
D | bug-hunting.rst | 7 WARNING: CPU: 1 PID: 28102 at kernel/module.c:1108 module_put+0x57/0x70 15 [<c12ba080>] ? dump_stack+0x44/0x64 16 [<c103ed6a>] ? __warn+0xfa/0x120 17 [<c109e8a7>] ? module_put+0x57/0x70 18 [<c109e8a7>] ? module_put+0x57/0x70 19 [<c103ee33>] ? warn_slowpath_null+0x23/0x30 20 [<c109e8a7>] ? module_put+0x57/0x70 21 [<f80ca4d0>] ? gp8psk_fe_set_frontend+0x460/0x460 [dvb_usb_gp8psk] 22 [<c109f617>] ? symbol_put_addr+0x27/0x50 23 [<f80bc9ca>] ? dvb_usb_adapter_frontend_exit+0x3a/0x70 [dvb_usb] [all …]
|
/Documentation/scsi/ |
D | arcmsr_spec.rst | 9 1. Message 0 37 offset 0xf00 for RS232 out (request buffer) 38 offset 0xe00 for RS232 in (scratch buffer) 39 offset 0xa00 for inbound message code message_rwbuffer 41 offset 0xa00 for outbound message code message_rwbuffer 70 0 256 bytes frame 74 0 normal request 91 bit31 must be 0 (for this type of reply) 95 0 no error, ignore AdapStatus/DevStatus/SenseData 111 offset: 0x78 Request Frame (bit30 == 1) [all …]
|
/Documentation/core-api/ |
D | dma-api.rst | 103 crossing restrictions, pass 0 for alloc; passing 4096 says memory allocated 161 Returns: 0 if successful and a negative error if not. 171 Returns: 0 if successful and a negative error if not. 181 Returns: 0 if successful and a negative error if not. 221 segments, the function returns 0. 374 does, 0 is returned and a driver must take appropriate action. It is 394 mapped them to. On failure 0, is returned. 484 If dma_attrs are 0, the semantics of each of these functions 645 check_unmap+0x203/0x490() 648 function [device address=0x00000000640444be] [size=66 bytes] [mapped as [all …]
|
/Documentation/trace/ |
D | histogram.rst | 216 field:unsigned short common_type; offset:0; size:2; signed:0; 217 field:unsigned char common_flags; offset:2; size:1; signed:0; 218 field:unsigned char common_preempt_count; offset:3; size:1; signed:0; 221 field:unsigned long call_site; offset:8; size:8; signed:0; 222 field:const void * ptr; offset:16; size:8; signed:0; 223 field:size_t bytes_req; offset:24; size:8; signed:0; 224 field:size_t bytes_alloc; offset:32; size:8; signed:0; 225 field:gfp_t gfp_flags; offset:40; size:4; signed:0; 278 Dropped: 0 295 allowed for the table (normally 0, but if not a hint that you may [all …]
|
/Documentation/x86/ |
D | boot.rst | 28 Protocol 2.02 (Kernel 2.4.0-test3-pre3) New command line protocol. 99 0A0000 +------------------------+ 121 0x100000 ("high memory"), and the kernel real-mode block (boot sector, 123 0x10000 and end of low memory. Unfortunately, in protocols 2.00 and 124 2.01 the 0x90000+ memory range is still used internally by the kernel; 139 0x90000 segment, the boot loader should make sure not to use memory 140 above the 0x9A000 point; too many BIOSes will break above that point. 149 0A0000 +------------------------+ 180 following header at offset 0x01f1. The real-mode code can total up to 195 01FE/2 ALL boot_flag 0xAA55 magic number [all …]
|