| /Linux-v5.15/Documentation/devicetree/bindings/ |
| D | .yamllint | 10 min-spaces-inside: 0
11 max-spaces-inside: 1
12 min-spaces-inside-empty: 0
13 max-spaces-inside-empty: 0
15 min-spaces-inside: 0
16 max-spaces-inside: 1
17 min-spaces-inside-empty: 0
18 max-spaces-inside-empty: 0
|
| /Linux-v5.15/Documentation/devicetree/bindings/crypto/ |
| D | inside-secure-safexcel.txt | 4 - compatible: Should be "inside-secure,safexcel-eip197b",
5 "inside-secure,safexcel-eip197d" or
6 "inside-secure,safexcel-eip97ies".
21 - "inside-secure,safexcel-eip197" is equivalent to
22 "inside-secure,safexcel-eip197b".
23 - "inside-secure,safexcel-eip97" is equivalent to
24 "inside-secure,safexcel-eip97ies".
29 compatible = "inside-secure,safexcel-eip197b";
|
| /Linux-v5.15/Documentation/devicetree/bindings/rng/ |
| D | omap_rng.txt | 9 - "inside-secure,safexcel-eip76" for SoCs with EIP76 IP block
14 Used for "ti,omap4-rng" and "inside-secure,safexcel-eip76"
16 "inside-secure,safexcel-eip76" compatible, the second clock is
34 compatible = "inside-secure,safexcel-eip76";
|
| /Linux-v5.15/net/netfilter/ |
| D | nf_nat_proto.c | 567 } *inside; in nf_nat_icmp_reply_translation() local
576 if (skb_ensure_writable(skb, hdrlen + sizeof(*inside))) in nf_nat_icmp_reply_translation()
581 inside = (void *)skb->data + hdrlen; in nf_nat_icmp_reply_translation()
582 if (inside->icmp.type == ICMP_REDIRECT) { in nf_nat_icmp_reply_translation()
601 if (!nf_nat_ipv4_manip_pkt(skb, hdrlen + sizeof(inside->icmp), in nf_nat_icmp_reply_translation()
607 inside = (void *)skb->data + hdrlen; in nf_nat_icmp_reply_translation()
608 inside->icmp.checksum = 0; in nf_nat_icmp_reply_translation()
609 inside->icmp.checksum = in nf_nat_icmp_reply_translation()
845 } *inside; in nf_nat_icmpv6_reply_translation() local
853 if (skb_ensure_writable(skb, hdrlen + sizeof(*inside))) in nf_nat_icmpv6_reply_translation()
[all …]
|
| /Linux-v5.15/fs/affs/ |
| D | dir.c | 86 goto inside; in affs_readdir()
102 goto inside; in affs_readdir()
110 inside: in affs_readdir()
|
| /Linux-v5.15/Documentation/devicetree/bindings/input/ |
| D | dlink,dir685-touchkeys.txt | 5 board inside the router is named E119921.
7 The touchkey device node should be placed inside an I2C bus node.
|
| /Linux-v5.15/Documentation/devicetree/bindings/mips/ |
| D | cpu_irq.txt | 9 Below is an example of a platform describing the cascade inside the devicetree
10 and the code used to load it inside arch_init_irq().
|
| /Linux-v5.15/Documentation/userspace-api/media/v4l/ |
| D | v4l2-selection-targets.rst | 46 - Bounds of the crop rectangle. All valid crop rectangles fit inside
69 inside the compose bounds rectangle.
|
| D | selection-api-configuration.rst | 39 active cropping area must lie completely inside the capture boundaries.
58 bounds rectangle. The composing rectangle must lie completely inside
73 be changed by the hardware. The content of pixels that lie inside the
99 must lie completely inside the crop boundaries and the driver may
110 composing rectangle must lie completely inside the bounds rectangle. The
|
| /Linux-v5.15/Documentation/devicetree/bindings/mmc/ |
| D | sdhci-st.txt | 10 subsystem (mmcss) inside the FlashSS (available in STiH407 SoC
27 to configure DLL inside the flashSS, if so reg-names must also be
32 for eMMC on stih407 family silicon to configure DLL inside FlashSS.
|
| /Linux-v5.15/Documentation/devicetree/bindings/clock/ |
| D | ux500.txt | 20 cell indicates which clock inside the PRCC block it wants,
26 cell indicates which clock inside the PRCC block it wants,
|
| /Linux-v5.15/Documentation/arm/ |
| D | memory.rst | 43 DTCM mounted inside the CPU.
46 ITCM mounted inside the CPU.
101 must not access any memory which is not mapped inside their 0x0001000
|
| D | tcm.rst | 8 This is usually just a few (4-64) KiB of RAM inside the ARM
11 Due to being embedded inside the CPU, the TCM has a
57 the CPU and then we hang inside ITCM waiting for an
86 to have functions called locally inside the TCM without
|
| /Linux-v5.15/Documentation/hwmon/ |
| D | k8temp.rst | 21 This driver permits reading temperature sensor(s) embedded inside AMD K8
29 There can be up to four temperature sensors inside single CPU. The driver
|
| D | coretemp.rst | 30 inside Intel CPUs. This driver can read both the per-core and per-package
33 show the temperature of all cores inside a package under a single device
34 directory inside hwmon.
|
| /Linux-v5.15/Documentation/filesystems/ext4/ |
| D | inlinedata.rst | 7 data is so tiny that it readily fits inside the inode, which
10 ``inode.i_block``. If the rest of the file would fit inside the extended
|
| /Linux-v5.15/Documentation/devicetree/bindings/phy/ |
| D | phy-miphy365x.txt | 12 register offset inside the sysconfig group.
16 'reg' and 'reg-names' properties are used inside these
|
| /Linux-v5.15/arch/um/ |
| D | Kconfig | 93 use in a chroot jail. So, if you intend to run UML inside a chroot,
136 where /tmp/fromhost is an empty directory inside UML and
200 This driver allows a host file to be used as emulated IO memory inside
215 Enable this option to support time travel inside the UML instance.
|
| /Linux-v5.15/Documentation/devicetree/bindings/sound/ |
| D | inno-rk3036.txt | 3 Inno audio codec is integrated inside RK3036 SoC.
|
| /Linux-v5.15/Documentation/devicetree/bindings/net/dsa/ |
| D | vitesse,vsc73xx.txt | 17 reside inside a SPI bus device tree node, see spi/spi-bus.txt
21 must reside inside a platform bus device tree node.
|
| /Linux-v5.15/Documentation/filesystems/ |
| D | splice.rst | 8 splice is a method for moving blocks of data around inside the kernel,
|
| /Linux-v5.15/drivers/phy/ralink/ |
| D | Kconfig | 20 This option enables support for the Ralink USB PHY found inside
|
| /Linux-v5.15/Documentation/devicetree/bindings/net/ |
| D | lantiq,xrx200-net.txt | 8 - reg : memory range of the PMAC core inside of the GSWIP core
|
| /Linux-v5.15/drivers/media/dvb-core/ |
| D | Kconfig | 63 inside the Kernel.
75 handling DVB network ULE packet loss inside the Kernel.
|
| /Linux-v5.15/Documentation/powerpc/ |
| D | bootwrapper.rst | 29 tree). This image embeds a device tree blob inside
31 are all embedded inside the U-Boot uImage file format
48 inside the image instead of provided by firmware. The
75 tree blob inside the image.
|
