Searched refs:Lines (Results 1 – 25 of 34) sorted by relevance
12
/linux-6.12.1/tools/perf/tests/shell/lib/ |
D | perf_json_output_lint.py | 25 Lines = args.file.readlines() variable 67 input = '[\n' + ','.join(Lines) + '\n]' 100 print('Test failed for input:\n' + '\n'.join(Lines))
|
/linux-6.12.1/Documentation/userspace-api/gpio/ |
D | chardev.rst | 40 :c:type:`chip.lines<gpiochip_info>`. Lines on the chip are identified by an 43 Lines are requested from the chip using gpio-v2-get-line-ioctl.rst 89 Reconfigure Lines <gpio-v2-line-set-config-ioctl>
|
D | chardev_v1.rst | 35 :c:type:`chip.lines<gpiochip_info>`. Lines on the chip are identified by an 38 Lines are requested from the chip using either gpio-get-linehandle-ioctl.rst 85 Reconfigure Lines <gpio-handle-set-config-ioctl>
|
/linux-6.12.1/Documentation/networking/pse-pd/ |
D | introduction.rst | 21 PoDL PSE, or Power over Data Lines PSE, specifically denotes PSEs operating 64 Summary of Clause 104: Power over Data Lines (PoDL) of Single Balanced Twisted-Pair Ethernet
|
/linux-6.12.1/Documentation/admin-guide/ |
D | lcd-panel-cgram.rst | 10 illuminated pixel with LSB on the right. Lines are numbered from the
|
/linux-6.12.1/Documentation/locking/ |
D | lockstat.rst | 141 show the header with column descriptions. Lines 05-18 and 20-31 show the actual 145 Lines 09-12 show the first 4 recorded contention points (the code
|
/linux-6.12.1/Documentation/driver-api/gpio/ |
D | using-gpio.rst | 2 Using GPIO Lines in Linux
|
/linux-6.12.1/arch/riscv/boot/dts/allwinner/ |
D | sun20i-d1-nezha.dts | 12 * Lines which are routed to the 40-pin header are named as follows:
|
/linux-6.12.1/Documentation/userspace-api/media/v4l/ |
D | vidioc-g-sliced-vbi-cap.rst | 137 - Lines, usually
|
/linux-6.12.1/arch/arm/boot/dts/nxp/imx/ |
D | imx53-smd.dts | 338 data-shift = <12>; /* Lines 19:12 used */
|
D | imx6qdl-ds.dtsi | 52 data-shift = <12>; /* Lines 19:12 used */
|
D | imx6qdl-sabrelite.dtsi | 232 data-shift = <12>; /* Lines 19:12 used */
|
D | imx6qdl-sabresd.dtsi | 153 data-shift = <12>; /* Lines 19:12 used */
|
/linux-6.12.1/tools/perf/pmu-events/ |
D | README | 117 Lines in which the first character is either '\n' or '#'
|
/linux-6.12.1/Documentation/RCU/ |
D | rcubarrier.rst | 155 Lines 7-50 stop all the kernel tasks associated with the rcutorture 246 Lines 3 and 4 locate RCU's internal per-CPU rcu_data structure,
|
/linux-6.12.1/arch/arm64/boot/dts/xilinx/ |
D | zynqmp-zcu106-revA.dts | 258 * Lines: 276 * Lines:
|
D | zynqmp-zcu104-revC.dts | 158 * Lines:
|
D | zynqmp-zcu104-revA.dts | 204 * Lines:
|
D | zynqmp-zcu111-revA.dts | 218 * Lines:
|
/linux-6.12.1/Documentation/filesystems/nfs/ |
D | knfsd-stats.rst | 17 separated by newline '\n' characters. Lines beginning with a hash
|
/linux-6.12.1/tools/memory-model/Documentation/ |
D | litmus-tests.txt | 111 Lines 5-9 show the first process and lines 11-18 the second process. Each 279 Lines 3-6 now initialize both "x" and "y" to the value 42. This also 715 sets the value of "y" to the *address* of "z". Lines 4 and 5 therefore 857 Lines 4-6 initialize a linked list headed by "y" that initially contains
|
/linux-6.12.1/arch/arm/boot/dts/ti/omap/ |
D | omap3-gta04.dtsi | 884 data-shift = <2>; /* Lines 9:2 are used */
|
/linux-6.12.1/Documentation/RCU/Design/Data-Structures/ |
D | Data-Structures.rst | 641 Lines 11-19 perform this computation. 643 Lines 21-24 compute the maximum number of CPUs supported by a 662 lines 37, 46-47, and 56-58. Lines 31-33, 40-42, 50-52, and 62-63 create
|
/linux-6.12.1/arch/arm64/boot/dts/qcom/ |
D | sdm845-db845c.dts | 710 /* QUAT I2S Uses 4 I2S SD Lines for audio on LT9611 HDMI Bridge */
|
/linux-6.12.1/Documentation/admin-guide/device-mapper/ |
D | dm-raid.rst | 236 # (Lines separated for easy reading)
|
12