Searched full:strings (Results 1 – 25 of 278) 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
110 Each configuration also needs its strings, so a subdirectory must be created
113 $ mkdir configs/c.1/strings/0x409
117 $ echo <configuration> > configs/c.1/strings/0x409/configuration
[all …]
|
| D | functionfs.rst | 8 strings (the user space program has to provide the same information
17 write descriptors and strings to that file. It does not need
18 to worry about endpoints, interfaces or strings numbers but
20 only one (endpoints and strings numbers starting from one and
25 When descriptors and strings are written "ep#" files appear
|
| /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/ABI/testing/ |
| D | configfs-usb-gadget | 43 What: /config/usb-gadget/gadget/configs/config/strings
48 strings for this configuration.
50 What: /config/usb-gadget/gadget/configs/config/strings/language
95 7: multiple unicode strings
99 What: /config/usb-gadget/gadget/strings
104 strings for this gadget.
106 What: /config/usb-gadget/gadget/strings/language
|
| D | sysfs-platform-phy-rcar-gen3-usb2 | 9 Write the following strings to change the mode:
13 Read the file, then it shows 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/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/media/uapi/v4l/ |
| D | ext-ctrls-fm-rx.rst | 43 name strings. Also from RDS specification, PS is usually a single
45 which can scroll strings sized as 8 x N characters. So, this control
54 ``V4L2_CID_RDS_RX_PS_NAME``. The encoding for Radio Text strings is
56 Radio Text strings depends on which RDS Block is being used to
58 also possible to find receivers which can scroll strings sized as 32
|
| D | ext-ctrls-fm-tx.rst | 49 name strings. Also from RDS specification, PS is usually a single
51 which can scroll strings sized as 8 x N characters. So, this control
61 The encoding for Radio Text strings is also fully described in Annex
62 E of :ref:`iec62106`. The length of Radio Text strings depends on
65 which can scroll strings sized as 32 x N or 64 x N characters. So,
|
| /Documentation/devicetree/bindings/leds/backlight/ |
| D | pm8941-wled.txt | 26 - qcom,num-strings: #; number of led strings attached; value from 1 to 3
41 qcom,num-strings = <2>;
|
| /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/devicetree/bindings/leds/ |
| D | leds-lm3692x.txt | 7 LED strings it supports. The LM36922 supports two strings while the LM36923
8 supports three strings.
|
| 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 | 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/clock/ |
| D | brcm,iproc-clocks.txt | 29 An ordered list of strings defining the names of the clocks
69 An ordered list of strings defining the names of the ASIU clocks
89 PLL and leaf clock compatible strings for Cygnus are:
142 PLL and leaf clock compatible strings for Hurricane 2 are:
156 PLL and leaf clock compatible strings for Northstar and Northstar Plus are:
186 PLL and leaf clock compatible strings for Northstar 2 are:
234 PLL and leaf clock compatible strings for BCM63138 are:
239 PLL and leaf clock compatible strings for Stingray are:
|
| /Documentation/devicetree/bindings/regulator/ |
| D | cirrus,lochnagar.txt | 26 - compatible : One of the following strings:
33 - compatible : One of the following strings:
39 - compatible : One of the following strings:
|
| /Documentation/admin-guide/pm/ |
| D | sleep-states.rst | 160 This file contains a list of strings representing sleep states supported
161 by the kernel. Writing one of these strings into it causes the kernel
165 In particular, the strings "disk", "freeze" and "standby" represent the
175 This file contains a list of strings representing supported system
179 The strings that may be present in this file are "s2idle", "shallow"
185 Writing one of the listed strings into this file causes the system
194 This file contains a list of strings representing different operations
223 Writing one of the listed strings into this file causes the option
238 into the :ref:`standby <standby>` state (the strings to write to the control
|
| /Documentation/devicetree/bindings/iio/multiplexer/ |
| D | io-channel-mux.txt | 14 - channels : List of strings, labeling the mux controller states.
18 the list of strings in the channels property, and also matches the mux
|
| /Documentation/devicetree/bindings/arm/socionext/ |
| D | uniphier.txt | 5 - compatible: should contain board and SoC compatible strings
7 SoC and board compatible strings:
|
| /Documentation/devicetree/bindings/sound/ |
| 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/devicetree/bindings/usb/ |
| D | atmel-usb.txt | 11 - clock-names: Should contain three strings
38 - clock-names: Should contain two strings
61 - clock-names: Should contain two strings
88 - clock-names: Should contain two strings
|
| D | usb-device.txt | 23 with leading zeroes suppressed. The other compatible strings from the above
40 strings from the above standard binding could also be used, but a device
52 with leading zeroes suppressed. The other compatible strings from the above
|
| /Documentation/devicetree/bindings/iio/ |
| D | st-sensors.txt | 8 - compatible: see the list of valid compatible strings below
27 Valid compatible strings:
|
| /Documentation/devicetree/bindings/mailbox/ |
| D | nvidia,tegra186-hsp.txt | 15 Array of strings.
21 Array of strings.
|
12345678910>>...12