| /linux/Documentation/fb/ |
| H A D | viafb.modes | 16 # 12 chars 2 lines
18 # 2 chars 10 lines
20 # 6 chars 33 lines
22 # 80 chars 480 lines
24 # 20 chars 45 lines
41 # 8 chars 3 lines
43 # 2 chars 1 lines
45 # 15 chars 16 lines
47 # 80 chars 480 lines
49 # 25 chars 20 lines
[all …]
|
| /linux/tools/net/ynl/pyynl/lib/ |
| H A D | doc_generator.py | 57 # This is useful for some fields that are spread across multiple lines
117 lines = []
119 lines.append(self.rst_paragraph(".. SPDX-License-Identifier: GPL-2.0"))
120 lines.append(self.rst_paragraph(".. NOTE: This document was auto-generated.\n\n"))
122 return "\n".join(lines)
127 lines = []
129 lines.append(".. toctree::")
130 lines.append(f" :maxdepth: {maxdepth}\n\n")
132 return "\n".join(lines)
151 lines = []
[all …]
|
| /linux/tools/gpio/ |
| H A D | gpio-utils.c | 27 * ioctl, including request and release for lines of gpio, read/write
29 * lines of gpio, user should use this type of api.
32 * following api will request gpio lines, do the operation and then
33 * release these lines.
37 * gpiotools_request_line() - request gpio lines in a gpiochip
40 * @lines: An array desired lines, specified by offset
42 * @num_lines: The number of lines to request.
49 * Request gpio lines through the ioctl provided by chardev. User
52 * gpiotools_release_line() to release these lines after that.
57 int gpiotools_request_line(const char *device_name, unsigned int *lines, in gpiotools_request_line() argument
[all …]
|
| H A D | gpio-hammer.c | 3 * gpio-hammer - example swiss army knife to shake GPIO lines on a system
25 int hammer_device(const char *device_name, unsigned int *lines, int num_lines, in hammer_device() argument
39 ret = gpiotools_request_line(device_name, lines, num_lines, in hammer_device()
55 fprintf(stdout, "Hammer lines ["); in hammer_device()
57 fprintf(stdout, "%u", lines[i]); in hammer_device()
72 /* Invert all lines so we blink */ in hammer_device()
92 fprintf(stdout, "%u: %d", lines[i], in hammer_device()
116 "Hammer GPIO lines, 0->1->0->1...\n" in print_usage()
130 unsigned int lines[GPIOHANDLES_MAX]; in main() local
152 lines[i] = strtoul(optarg, NULL, 10); in main()
[all …]
|
| /linux/tools/testing/kunit/ |
| H A D | kunit_parser.py | 34 log : List[str] - log of KTAP lines that correspond to the test
148 A class to represent the lines of kernel output.
157 def __init__(self, lines: Iterator[Tuple[int, str]]):
159 self._lines = lines
192 """Returns True if stream has more lines."""
198 """Empties all lines stored in LineStream object into
218 """Extracts KTAP lines from the kernel output."""
227 # start extracting KTAP lines and set prefix
234 # start extracting KTAP lines and set prefix
240 # stop extracting KTAP lines
[all...] |
| /linux/include/uapi/linux/ |
| H A D | gpio.h | 30 * @lines: number of GPIO lines on this chip
35 __u32 lines; member
39 * Maximum number of requested lines.
89 * struct gpio_v2_line_values - Values of GPIO lines
90 * @bits: a bitmap containing the value of the lines, set to 1 for active
92 * @mask: a bitmap identifying the lines to get or set, with each bit
124 * containing the values to which the lines will be set, with each bit
142 * associated with one or more of the requested lines.
144 * @mask: a bitmap identifying the lines to which the attribute applies,
154 * struct gpio_v2_line_config - Configuration for GPIO lines
[all …]
|
| /linux/Documentation/userspace-api/gpio/ |
| H A D | chardev.rst | 21 Similarly, for multi-function lines there may be other subsystems, such as
39 Each chip supports a number of GPIO lines,
40 :c:type:`chip.lines<gpiochip_info>`. Lines on the chip are identified by an
41 ``offset`` in the range from 0 to ``chip.lines - 1``, i.e. `[0,chip.lines)`.
43 Lines are requested from the chip using gpio-v2-get-line-ioctl.rst
44 and the resulting line request is used to access the GPIO chip's lines or
45 monitor the lines for edge events.
71 access to a set of requested lines. The line request is exposed to userspace
89 Reconfigure Lines <gpio-v2-line-set-config-ioctl>
|
| H A D | gpio-v2-line-set-config-ioctl.rst | 12 GPIO_V2_LINE_SET_CONFIG_IOCTL - Update the configuration of previously requested lines.
30 requested lines.
35 Update the configuration of previously requested lines, without releasing the
38 The new configuration must specify a configuration for all requested lines.
41 :ref:`gpio-v2-get-line-config-support` that apply when requesting the lines
48 bi-directional lines between input and output, but it may also be used to
49 dynamically control edge detection, or more generally move lines seamlessly
52 To only change the value of output lines, use
|
| H A D | gpio-handle-set-config-ioctl.rst | 16 GPIOHANDLE_SET_CONFIG_IOCTL - Update the configuration of previously requested lines.
34 requested lines.
39 Update the configuration of previously requested lines, without releasing the
42 The configuration applies to all requested lines.
46 lines also apply when updating the line configuration, with the additional
52 bi-directional lines between input and output, but it may be used more
53 generally to move lines seamlessly from one configuration state to another.
55 To only change the value of output lines, use
|
| H A D | chardev_v1.rst | 34 Each chip supports a number of GPIO lines,
35 :c:type:`chip.lines<gpiochip_info>`. Lines on the chip are identified by an
36 ``offset`` in the range from 0 to ``chip.lines - 1``, i.e. `[0,chip.lines)`.
38 Lines are requested from the chip using either gpio-get-linehandle-ioctl.rst
39 and the resulting line handle is used to access the GPIO chip's lines, or
68 access to a set of requested lines. The line handle is exposed to userspace
85 Reconfigure Lines <gpio-handle-set-config-ioctl>
|
| /linux/tools/mm/ |
| H A D | slabinfo-gnuplot.sh | 56 local lines=2000000
64 lines=$((xmax-xmin))
69 wc_lines=$lines
72 if [ "$wc_lines" -lt "$lines" ]; then
73 lines=$wc_lines
76 if [ $((width / lines)) -gt $min_slab_name_size ]; then
118 '$i Memory usage' with lines,"
120 '$i Loss' with lines,"
144 local lines
150 let lines=3
[all …]
|
| /linux/Documentation/driver-api/gpio/ |
| H A D | drivers-on-gpio.rst | 11 lines, giving you the LED sysfs interface
26 mouse cable and connect the wires to GPIO lines or solder a mouse connector
27 to the lines for a more permanent solution of this type.
54 (two wires, SDA and SCL lines) by hammering (bitbang) two GPIO lines. It will
59 of wires, at least SCK and optionally MISO, MOSI and chip select lines) using
84 to a set of simple GPIO lines: RDY, NCE, ALE, CLE, NWP. It interacts with the
89 bus, data and clock line, by bit banging two GPIO lines. It will appear as
100 nothing but GPIO lines, this driver provides that and also a clearly defined
105 n GPIO lines such that you can mux in 2^n different devices by activating
106 different GPIO lines. Often the GPIOs are on a SoC and the devices are
[all …]
|
| H A D | using-gpio.rst | 2 Using GPIO Lines in Linux
5 The Linux kernel exists to abstract and present hardware to users. GPIO lines
7 and preferred way to use GPIO lines is to let kernel hardware drivers deal
20 In Linux GPIO lines also have a userspace ABI.
23 factory lines, maker community projects, workshop specimen, production tools,
33 from userspace will likely be a good fit for using GPIO lines from userspace as
|
| /linux/tools/perf/util/ |
| H A D | srccode.c | 3 * Manage printing of source lines
29 char **lines; member
58 static void fill_lines(char **lines, int maxline, char *map, int maplen) in fill_lines() argument
67 lines[l++] = map; in fill_lines()
71 lines[l++] = ++p; in fill_lines()
74 lines[l] = p; in fill_lines()
83 zfree(&sf->lines); in free_srcfile()
136 h->lines = calloc(h->numlines, sizeof(char *)); in find_srcfile()
137 if (!h->lines) in find_srcfile()
139 fill_lines(h->lines, h->numlines, h->map, h->maplen); in find_srcfile()
[all …]
|
| /linux/drivers/staging/greybus/ |
| H A D | gpio.c | 38 struct gb_gpio_line *lines; member
80 ggc->lines[which].active = true; in gb_gpio_activate_operation()
101 ggc->lines[which].active = false; in gb_gpio_deactivate_operation()
128 ggc->lines[which].direction = direction ? 1 : 0; in gb_gpio_get_direction_operation()
142 ggc->lines[which].direction = 1; in gb_gpio_direction_in_operation()
157 ggc->lines[which].direction = 0; in gb_gpio_direction_out_operation()
184 ggc->lines[which].value = value ? 1 : 0; in gb_gpio_get_value_operation()
204 ggc->lines[which].value = request.value; in gb_gpio_set_value_operation()
220 ggc->lines[which].debounce_usec = debounce_usec; in gb_gpio_set_debounce_operation()
273 struct gb_gpio_line *line = &ggc->lines[d->hwirq]; in gb_gpio_irq_mask()
[all …]
|
| /linux/arch/hexagon/mm/ |
| H A D | cache.c | 17 unsigned long lines = spanlines(start, end-1); in flush_dcache_range() local
24 for (i = 0; i < lines; i++) { in flush_dcache_range()
37 unsigned long lines = spanlines(start, end-1); in flush_icache_range() local
44 for (i = 0; i < lines; i++) { in flush_icache_range()
62 unsigned long lines = spanlines(start, end-1); in hexagon_clean_dcache_range() local
69 for (i = 0; i < lines; i++) { in hexagon_clean_dcache_range()
82 unsigned long lines = spanlines(start, end-1); in hexagon_inv_dcache_range() local
89 for (i = 0; i < lines; i++) { in hexagon_inv_dcache_range()
|
| /linux/Documentation/devicetree/bindings/gpio/ |
| H A D | nxp,pcf8575.yaml | 13 The PCF857x-compatible chips have "quasi-bidirectional" I/O lines that can be
55 lines-initial-states:
63 If the property is not specified all lines will be initialized to the
85 Performing a reset makes all lines initialized to their input (pulled-up)
103 # lines-initial-states XOR reset-gpios
104 # Performing a reset reinitializes all lines to a known state which
105 # may not match passed lines-initial-states
108 - lines-initial-states
|
| H A D | gpio-mmio.yaml | 43 the ngpios property further restricts the number of used lines.
46 Register to READ the value of the GPIO lines. If GPIO line is high,
51 Register to SET the value of the GPIO lines. Setting a bit in this
54 Register to CLEAR the value of the GPIO lines. Setting a bit in this
56 the SET register will be used to clear the GPIO lines as well, by
84 If this property is present the number of usable GPIO lines are restricted
85 to the first 0 .. ngpios lines. This is useful when the GPIO MMIO register
92 If this property is present, the controller cannot drive the GPIO lines.
|
| /linux/tools/perf/pmu-events/arch/x86/ivybridge/ |
| H A D | cache.json | 7 "PublicDescription": "Counts the number of lines brought into the L1 data cache.",
51 "BriefDescription": "Not rejected writebacks from L1D to L2 cache lines in any state.",
59 "BriefDescription": "Not rejected writebacks from L1D to L2 cache lines in E state",
63 "PublicDescription": "Not rejected writebacks from L1D to L2 cache lines in E state.",
68 "BriefDescription": "Not rejected writebacks from L1D to L2 cache lines in M state",
72 "PublicDescription": "Not rejected writebacks from L1D to L2 cache lines in M state.",
77 …"BriefDescription": "Count the number of modified Lines evicted from L1 and missed L2. (Non-reject…
86 "BriefDescription": "L2 cache lines filling L2",
90 "PublicDescription": "L2 cache lines filling L2.",
95 "BriefDescription": "L2 cache lines in E state filling L2",
[all …]
|
| /linux/Documentation/sphinx/ |
| H A D | kernel_abi.py | 134 lines = [
139 lines.append(" " + m)
141 lines = msg_list
143 for line in lines:
144 # sphinx counts lines from 0
163 logger.verbose("%s ABI: %i symbols (%i ReST lines)" % (abi_type, n_sym, n))
165 logger.verbose("%s ABI: %i files (%i ReST lines)" % (abi_type, n_sym, n))
167 logger.verbose("%s ABI: %i data (%i ReST lines)" % (abi_type, n_sym, n))
|
| H A D | kernel_feat.py | 98 lines = feat.output_arch_table(arch)
100 lines = feat.output_matrix()
106 for line in lines.split("\n"):
119 def nestedParse(self, lines, fname): argument
125 for l in lines.split("\n"):
127 lines = code_block + "\n\n"
129 for c, l in enumerate(lines.split("\n")):
|
| /linux/Documentation/devicetree/bindings/display/ |
| H A D | arm,malidp.yaml | 65 arm,malidp-output-port-lines:
68 Number of output lines/bits for each colour channel.
70 - description: number of output lines for the red channel (R)
71 - description: number of output lines for the green channel (G)
72 - description: number of output lines for the blue channel (B)
98 - arm,malidp-output-port-lines
110 arm,malidp-output-port-lines = /bits/ 8 <8 8 8>;
|
| /linux/drivers/gpio/ |
| H A D | gpio-mockup.c | 32 * of GPIO lines.
55 struct gpio_mockup_line_status *lines; member
89 return chip->lines[offset].value; in __gpio_mockup_get()
122 chip->lines[offset].value = !!value; in __gpio_mockup_set()
154 struct gpio_mockup_line_status *line = &chip->lines[offset]; in gpio_mockup_apply_pull()
191 chip->lines[offset].pull = value; in gpio_mockup_apply_pull()
217 chip->lines[offset].dir = GPIO_LINE_DIRECTION_OUT; in gpio_mockup_dirout()
229 chip->lines[offset].dir = GPIO_LINE_DIRECTION_IN; in gpio_mockup_dirin()
240 direction = chip->lines[offset].dir; in gpio_mockup_get_direction()
257 chip->lines[offset].requested = true; in gpio_mockup_request()
[all …]
|
| /linux/tools/testing/selftests/gpio/ |
| H A D | gpio-sim.sh | 30 LINES=`ls $CONFIGFS_DIR/$CHIP/$BANK/ | grep -E ^line`
32 for LINE in $LINES; do
76 fail "Unable to set the number of lines"
128 $BASE_DIR/gpio-chip-info /dev/`configfs_chip_name $CHIP $BANK` num-lines || \
129 fail "unable to read the number of lines from the character device"
205 echo "2.1. Default number of lines is 1"
209 test "`get_chip_num_lines chip bank`" = "1" || fail "default number of lines is not 1"
213 echo "2.2. Number of lines can be specified"
218 test "`get_chip_num_lines chip bank`" = "16" || fail "number of lines is not 16"
251 echo "2.6. Line config can remain unused if offset is greater than number of lines"
[all …]
|
| /linux/arch/um/drivers/ |
| H A D | Kconfig | 15 lines on the UML that are usually made to show up on the host as
27 lines to a device similar to /dev/null. Data written to it disappears
34 lines to host portals. They may be accessed with 'telnet <host>
35 <port number>'. Any number of consoles and serial lines may be
44 lines to host pseudo-terminals. Access to both traditional
54 lines to host terminals. Access to both virtual consoles
63 lines to xterms. Each UML device so assigned will be brought up in
104 This is the string describing the channel to which the serial lines
|