Searched full:inside (Results 1 – 25 of 313) sorted by relevance
12345678910>>...13
/Documentation/devicetree/bindings/crypto/ |
D | inside-secure-safexcel.txt | 1 Inside Secure SafeXcel cryptographic engine 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";
|
/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
|
/Documentation/devicetree/bindings/rng/ |
D | omap_rng.txt | 1 OMAP SoC and Inside-Secure HWRNG Module 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";
|
/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.
|
/Documentation/hwmon/ |
D | abx500.rst | 24 There are some GPADCs inside ABx500 which are designed for connecting to 25 thermal sensors, and there is also a thermal sensor inside ABx500 too, which
|
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
|
/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().
|
/Documentation/userspace-api/media/v4l/ |
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
|
D | v4l2-selection-targets.rst | 40 - Bounds of the crop rectangle. All valid crop rectangles fit inside 63 inside the compose bounds rectangle.
|
D | ext-ctrls-rf-tuner.rst | 17 inside a metal box, while newer ones are highly integrated chips 76 located inside mixer block, where RF signal is down-converted by the
|
/Documentation/devicetree/bindings/gpio/ |
D | mediatek,mt7621-gpio.txt | 3 The IP core used inside these SoCs has 3 banks of 32 GPIOs each. 4 The registers of all the banks are interwoven inside one single IO range.
|
/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
|
/Documentation/devicetree/bindings/interconnect/ |
D | qcom,bcm-voter.yaml | 47 # Example 1: apps bcm_voter on SDM845 SoC should be defined inside &apps_rsc node 55 # Example 2: disp bcm_voter on SDM845 should be defined inside &disp_rsc node
|
/Documentation/arm/ |
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
|
D | memory.rst | 43 DTCM mounted inside the CPU. 46 ITCM mounted inside the CPU. 96 must not access any memory which is not mapped inside their 0x0001000
|
/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,
|
/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.
|
/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.
|
/Documentation/devicetree/bindings/sound/ |
D | inno-rk3036.txt | 3 Inno audio codec is integrated inside RK3036 SoC.
|
/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
|
/Documentation/filesystems/ |
D | splice.rst | 8 splice is a method for moving blocks of data around inside the kernel,
|
/Documentation/devicetree/bindings/net/ |
D | lantiq,xrx200-net.txt | 8 - reg : memory range of the PMAC core inside of the GSWIP core
|
/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.
|
/Documentation/devicetree/bindings/interrupt-controller/ |
D | marvell,gicp.txt | 6 located in the Marvell CP110 to turn wired interrupts inside the CP
|
/Documentation/doc-guide/ |
D | kernel-doc.rst | 198 Inside a struct or union description, you can use the ``private:`` and 199 ``public:`` comment tags. Structure fields that are inside a ``private:`` 237 * @bar.st1: struct st1 inside @bar 238 * @bar.st2: struct st2 inside @bar 271 is named, the member ``bar`` inside it should be documented as 304 /** @bar2: Description for struct @bar2 inside @foo */ 307 * @bar2.barbar: Description for @barbar inside @foo.bar2 364 This is particularly useful if you need to use things like ``%ph`` inside
|
12345678910>>...13