| /linux-6.15/arch/arm/boot/dts/ti/omap/ |
| H A D | am335x-osd335x-common.dtsi | 26 * Therefore, from a DEVICE_ID revision point of view, the silicon looks
28 * the HW OPP table, the silicon looks like it is Revision 1.0 (ie the
|
| /linux-6.15/Documentation/iio/ |
| H A D | bno055.rst | 31 the driver looks for at probe time. If found, then the IMU is initialized
36 The driver looks for calibration data file using two different names: first
|
| H A D | ad4030.rst | 158 internal buffered reference voltage via the ``REFIN`` input. The driver looks
167 Both hardware and software reset are supported. The driver looks first at the
|
| /linux-6.15/Documentation/ABI/stable/ |
| H A D | sysfs-driver-qla2xxx | 4 Description: qla2xxx-udev.sh currently looks for uevent CHANGE events to
|
| H A D | o2cb | 5 Description: Ocfs2-tools looks at 'interface-revision' for versioning
|
| /linux-6.15/Documentation/maintainer/ |
| H A D | messy-diffstat.rst | 12 great deal of unrelated work. The result looks ugly and obscures what the
21 manner, mainline kernel development looks like this::
36 result in the simplest case is a history that looks like::
|
| /linux-6.15/Documentation/ABI/obsolete/ |
| H A D | o2cb | 5 Description: Ocfs2-tools looks at 'interface-revision' for versioning
|
| /linux-6.15/tools/testing/selftests/bpf/ |
| H A D | README.rst | 127 The symptom looks like
169 The symptom for ``bpf_iter/ipv6_route`` looks like
181 The symptom for ``bpf_iter/netlink`` looks like
206 The verifier output looks like
275 Without it, the error from compiling bpf selftests looks like:
|
| /linux-6.15/Documentation/ABI/testing/ |
| H A D | procfs-smaps_rollup | 17 Typical output looks like this::
|
| /linux-6.15/Documentation/driver-api/iio/ |
| H A D | hw-consumer.rst | 22 A typical IIO HW consumer setup looks like this::
|
| H A D | triggered-buffers.rst | 15 A typical triggered buffer setup looks like this::
|
| /linux-6.15/Documentation/driver-api/firmware/ |
| H A D | direct-fs-lookup.rst | 6 by the kernel. The kernel looks for the firmware directly on the root
|
| /linux-6.15/scripts/coccinelle/null/ |
| H A D | kmerr.cocci | 2 /// This semantic patch looks for kmalloc etc that are not followed by a
|
| /linux-6.15/Documentation/networking/ |
| H A D | phy-link-topology.rst | 17 when designing these configuration APIs were that the link looks something like ::
35 The link topology then looks like this (when an SFP module is inserted) ::
|
| /linux-6.15/drivers/staging/sm750fb/ |
| H A D | readme | 27 ahead of parameters,so,it looks like:
|
| /linux-6.15/Documentation/core-api/ |
| H A D | entry.rst | 64 invoked from low-level assembly code looks like this:
144 The architecture-specific part looks similar to syscall handling:
229 Architecture-specific code looks like this:
|
| /linux-6.15/Documentation/fb/ |
| H A D | cmap_xfbdev.rst | 54 that the app wants to match to. The above code is doing what looks like a least
|
| /linux-6.15/Documentation/devicetree/bindings/display/panel/ |
| H A D | panel-edp.yaml | 38 looks the exactly the same as every other panel. Each panel datasheet
81 The above looks fairly complex but, as per above, each panel only cares
|
| /linux-6.15/Documentation/firmware-guide/acpi/ |
| H A D | non-d0-probe.rst | 59 System the device should remain powered off during probe looks like this. Some
|
| /linux-6.15/arch/arm64/boot/dts/ti/ |
| H A D | k3-am62-lp-sk-nand.dtso | 96 reg = <0x00400000 0x00200000>; /* BootROM looks at 4M */
|
| /linux-6.15/Documentation/driver-api/ |
| H A D | zorro.rst | 29 for the board with Zorro ID ``ZORRO_PROD_xxx`` looks like::
|
| /linux-6.15/Documentation/admin-guide/ |
| H A D | cpu-load.rst | 26 signalled the kernel looks what kind of task was running at this
|
| /linux-6.15/Documentation/netlink/specs/ |
| H A D | team.yaml | 29 The team nested layout of get/set msg looks like
|
| /linux-6.15/Documentation/filesystems/ |
| H A D | sharedsubtree.rst | 722 the new tree now looks like this::
742 the new tree now looks like this::
804 the new tree now looks like this::
820 the new tree now looks like this::
836 the new tree now looks like this::
896 A example propagation tree looks as shown in the figure below.
897 [ NOTE: Though it looks like a forest, if we consider all the shared
|
| /linux-6.15/Documentation/arch/s390/ |
| H A D | zfcpdump.rst | 32 The s390 zipl tool looks for the zfcpdump kernel and optional initrd/initramfs
|