Searched full:strings (Results 1 – 25 of 279) sorted by relevance
12345678910>>...12
| /Documentation/usb/ |
| D | gadget_configfs.rst | 81 A gadget also needs its serial number, manufacturer and product strings.
82 In order to have a place to store them, a strings subdirectory must be created
85 $ mkdir strings/0x409
87 Then the strings can be specified::
89 $ echo <serial number> > strings/0x409/serialnumber
90 $ echo <manufacturer> > strings/0x409/manufacturer
91 $ echo <product> > strings/0x409/product
97 $ mkdir strings/0x409/xu.0
98 $ echo <string text> > strings/0x409/xu.0/s
101 string descriptors to associate those strings with class descriptors.
[all …]
|
| D | functionfs.rst | 11 strings (the user space program has to provide the same information
20 write descriptors and strings to that file. It does not need
21 to worry about endpoints, interfaces or strings numbers but
23 only one (endpoints and strings numbers starting from one and
30 When descriptors and strings are written "ep#" files appear
|
| D | gadget_uvc.rst | 306 Custom Strings Support
312 assign those strings as descriptors:
322 mkdir -p $GADGET/strings/0x409/iad_desc
323 echo -n "Interface Associaton Descriptor" > $GADGET/strings/0x409/iad_desc/s
324 ln -s $GADGET/strings/0x409/iad_desc $FUNCTION/iad_desc
330 mkdir -p $GADGET/strings/0x409/xu.0
331 echo -n "A Very Useful Extension Unit" > $GADGET/strings/0x409/xu.0/s
332 ln -s $GADGET/strings/0x409/xu.0 $FUNCTION/control/extensions/xu.0
|
| /Documentation/firmware-guide/acpi/apei/ |
| D | output_format.rst | 15 <section flags strings>
23 <section flags strings># :=
38 <proc error type strings>]
41 <proc flags strings>]
54 <processor error type strings># :=
60 <proc flags strings># :=
139 All <field strings> description with # has the following format::
142 <field strings>
144 Where each string in <fields strings> corresponding to one set bit of
146 strings> description.
|
| /Documentation/devicetree/bindings/leds/backlight/ |
| D | qcom-wled.yaml | 104 qcom,num-strings:
106 number of led strings attached.
109 qcom,enabled-strings:
111 Array of the WLED strings numbered from 0 to 3. Each
113 list of strings used by the device. Any combination of
114 led strings can be used.
186 qcom,num-strings:
207 qcom,num-strings:
261 qcom,num-strings = <2>;
262 qcom,enabled-strings = <0 1>;
|
| /Documentation/pcmcia/ |
| D | devicetable.rst | 10 - product ID strings _and_ hashes of these strings
17 If you want to match product ID strings, you also need to pass the crc32
26 You can determine the hash of the product ID strings by catting the file
|
| /Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-fm-rx.rst | 36 name strings. Also from RDS specification, PS is usually a single
38 which can scroll strings sized as 8 x N characters. So, this control
47 ``V4L2_CID_RDS_RX_PS_NAME``. The encoding for Radio Text strings is
49 Radio Text strings depends on which RDS Block is being used to
51 also possible to find receivers which can scroll strings sized as 32
|
| D | ext-ctrls-fm-tx.rst | 42 name strings. Also from RDS specification, PS is usually a single
44 which can scroll strings sized as 8 x N characters. So, this control
54 The encoding for Radio Text strings is also fully described in Annex
55 E of :ref:`iec62106`. The length of Radio Text strings depends on
58 which can scroll strings sized as 32 x N or 64 x N characters. So,
|
| /Documentation/devicetree/bindings/sifive/ |
| D | sifive-blocks-ip-versioning.txt | 4 strings for open-source SiFive IP blocks. HDL for these IP blocks
9 IP block-specific DT compatible strings are contained within the HDL,
26 match on these IP block-specific compatible strings.
|
| /Documentation/ABI/testing/ |
| D | sysfs-platform-phy-rcar-gen3-usb2 | 9 Write the following strings to change the mode:
14 Read the file, then it shows the following strings:
|
| D | configfs-usb-gadget | 51 What: /config/usb-gadget/gadget/configs/config/strings
56 strings for this configuration.
58 What: /config/usb-gadget/gadget/configs/config/strings/language
109 - 7: multiple unicode strings
114 What: /config/usb-gadget/gadget/strings
119 strings for this gadget.
121 What: /config/usb-gadget/gadget/strings/language
|
| D | sysfs-class-devlink | 19 This will be one of the following strings:
50 This will be one of the following strings:
71 This will be one of the following strings:
117 This will be one of the following strings:
|
| D | sysfs-class-regulator | 10 This will be one of the following strings:
36 This will be one of the following strings:
75 This will be one of the following strings:
130 The opmode value can be one of the following strings:
324 This will be one of the same strings reported by
337 This will be one of the same strings reported by
350 This will be one of the same strings reported by
361 This will be one of the following strings:
|
| /Documentation/devicetree/bindings/leds/ |
| D | leds-lm36274.txt | 4 The backlight boost provides the power to bias four parallel LED strings with
20 - led-sources : Indicates which LED strings will be enabled.
21 Values from 0-3, sources is 0 based so strings will be
|
| D | ti.lm36922.yaml | 17 LED strings it supports. The LM36922 supports two strings while the LM36923
18 supports three strings.
|
| D | leds-lm3532.txt | 55 - ti,led-mode : Defines if the LED strings are manually controlled or
56 if the LED strings are controlled by the ALS.
57 0x00 - LED strings are I2C controlled via full scale
59 0x01 - LED strings are ALS controlled
|
| /Documentation/devicetree/bindings/usb/ |
| D | atmel-usb.txt | 11 - clock-names: Should contain three strings
38 - clock-names: Should contain two strings
65 - clock-names: Should contain two strings
96 - clock-names: Should contain two strings
|
| /Documentation/devicetree/bindings/ |
| D | .yamllint | 4 quoted-strings:
43 check-multi-line-strings: false
|
| /Documentation/devicetree/bindings/sound/ |
| D | audio-graph.yaml | 26 Each entry is a pair of strings, the first being the
32 Each entry is a pair of strings, the first being the type of
|
| D | omap-mcbsp.txt | 11 - reg-names: Array of strings associated with the address space
17 - interrupt-names: Array of strings associated with the interrupt numbers
|
| /Documentation/devicetree/bindings/hsi/ |
| D | nokia-modem.txt | 12 - hsi-channel-names: Should contain the following strings
19 - gpio-names: Should contain the following strings
|
| /Documentation/admin-guide/pm/ |
| D | sleep-states.rst | 163 This file contains a list of strings representing sleep states supported
164 by the kernel. Writing one of these strings into it causes the kernel
168 In particular, the "disk", "freeze" and "standby" strings represent the
178 This file contains a list of strings representing supported system
182 The strings that may be present in this file are "s2idle", "shallow"
188 Writing one of the listed strings into this file causes the system
235 Writing one of the strings listed above into this file causes the option
279 into the :ref:`standby <standby>` state (the strings to write to the control
|
| /Documentation/devicetree/bindings/iio/multiplexer/ |
| D | io-channel-mux.yaml | 18 of strings in the channels property, and also matches the mux controller
40 List of strings, labeling the mux controller states. An empty
|
| /Documentation/devicetree/bindings/memory-controllers/ddr/ |
| D | jedec,lpddr-props.yaml | 21 Compatible strings can be either explicit vendor names and part numbers
22 (e.g. elpida,ECB240ABACN), or generated strings of the form
|
| /Documentation/devicetree/bindings/mux/ |
| D | mux-consumer.yaml | 25 strings to label each of the mux controllers listed in the "mux-controls"
30 "mux-state-names" can be used to provide a list of strings, to label
|
12345678910>>...12