/linux-4.4.14/drivers/of/ |
D | of_mdio.c | 290 const char *managed; in of_phy_is_fixed_link() local 299 err = of_property_read_string(np, "managed", &managed); in of_phy_is_fixed_link() 300 if (err == 0 && strcmp(managed, "auto") != 0) in of_phy_is_fixed_link() 320 const char *managed; in of_phy_register_fixed_link() local 322 err = of_property_read_string(np, "managed", &managed); in of_phy_register_fixed_link() 324 if (strcmp(managed, "in-band-status") == 0) { in of_phy_register_fixed_link()
|
/linux-4.4.14/include/uapi/linux/ |
D | icmpv6.h | 48 managed:1; member 51 __u8 managed:1, member 75 #define icmp6_addrconf_managed icmp6_dataun.u_nd_ra.managed
|
/linux-4.4.14/Documentation/driver-model/ |
D | devres.txt | 14 6. List of managed interfaces : Currently implemented managed interfaces 57 using dma_alloc_coherent(). The managed version is called 59 for the DMA memory allocated using it is managed and will be 99 detached. If most resources are acquired using managed interface, a 233 6. List of managed interfaces 316 pcim_enable_device() : after success, all PCI ops become managed
|
/linux-4.4.14/Documentation/devicetree/bindings/sound/ |
D | cs35l32.txt | 19 0 = Automatically managed. Boost-converter output voltage is the higher 21 1 = Automatically managed irrespective of audio, adapting for low-power
|
/linux-4.4.14/Documentation/ABI/testing/ |
D | sysfs-class-iommu | 6 IOMMU drivers are able to link devices managed by a
|
D | sysfs-devices-power | 45 + "auto\n" to allow the device to be power managed at run time; 46 + "on\n" to prevent the device from being power managed;
|
D | sysfs-bus-coresight-devices-etm3x | 9 configured and managed automatically by the coresight framework.
|
D | sysfs-bus-coresight-devices-etm4x | 9 configured and managed automatically by the coresight framework.
|
/linux-4.4.14/Documentation/devicetree/bindings/soc/ti/ |
D | keystone-navigator-qmss.txt | 31 -- managed-queues : the actual queues managed by each queue manager 125 managed-queues = <0 0x2000>; 135 managed-queues = <0x2000 0x2000>;
|
/linux-4.4.14/drivers/virt/ |
D | Kconfig | 30 4) A kernel interface for receiving callbacks when a managed
|
/linux-4.4.14/arch/arm/boot/dts/ |
D | k2hk-netcp.dtsi | 27 managed-queues = <0 0x2000>; 39 managed-queues = <0x2000 0x2000>;
|
D | k2l-netcp.dtsi | 27 managed-queues = <0 0x2000>;
|
D | k2e-netcp.dtsi | 27 managed-queues = <0 0x2000>;
|
D | armada-370-dlink-dns327l.dts | 189 /* Ensure these are managed by hardware */
|
/linux-4.4.14/Documentation/devicetree/bindings/mfd/ |
D | axp20x.txt | 26 not used but preferred to be managed by the OS should be 121 /* unused but preferred to be managed by OS */
|
/linux-4.4.14/Documentation/devicetree/bindings/clock/ |
D | renesas,r8a7778-cpg-clocks.txt | 17 SoC devices that are part of the CPG/MSTP Clock Domain and can be power-managed
|
D | renesas,r8a7779-cpg-clocks.txt | 19 SoC devices that are part of the CPG/MSTP Clock Domain and can be power-managed
|
D | renesas,rz-cpg-clocks.txt | 21 SoC devices that are part of the CPG/MSTP Clock Domain and can be power-managed
|
D | renesas,rcar-gen2-cpg-clocks.txt | 27 SoC devices that are part of the CPG/MSTP Clock Domain and can be power-managed
|
D | renesas,cpg-mssr.txt | 36 power-managed through Module Standby should refer to the CPG device
|
/linux-4.4.14/Documentation/devicetree/bindings/mmc/ |
D | tmio_mmc.txt | 4 devices is managed by either MFD drivers or by the sh_mobile_sdhi platform
|
/linux-4.4.14/drivers/net/ethernet/sfc/ |
D | Kconfig | 29 This exposes the on-board firmware-managed sensors as a
|
/linux-4.4.14/Documentation/devicetree/bindings/net/ |
D | fixed-link.txt | 5 normal MDIO-managed PHY device. For those situations, a Device Tree
|
D | ethernet.txt | 28 - managed: string, specifies the PHY management type. Supported values are:
|
/linux-4.4.14/drivers/net/ethernet/micrel/ |
D | Kconfig | 33 ethernet switch chip (managed, VLAN, QoS) from Micrel or
|
/linux-4.4.14/Documentation/devicetree/bindings/phy/ |
D | phy-bindings.txt | 15 regulator will be managed during the PHY power on/off sequence.
|
/linux-4.4.14/Documentation/devicetree/bindings/misc/ |
D | sram.txt | 3 Simple IO memory regions to be managed by the genalloc API.
|
/linux-4.4.14/Documentation/devicetree/bindings/gpio/ |
D | gpio-mvebu.txt | 18 managed by this GPIO bank. There can be more than one interrupt
|
D | renesas,gpio-rcar.txt | 25 - gpio-ranges: Range of pins managed by the GPIO controller.
|
/linux-4.4.14/Documentation/devicetree/bindings/pinctrl/ |
D | abilis,tb10x-iomux.txt | 38 All other ports of the chip are not multiplexed and thus not managed by this
|
/linux-4.4.14/include/uapi/sound/ |
D | compress_params.h | 267 __u32 managed; member
|
/linux-4.4.14/Documentation/hwmon/ |
D | abituguru3 | 54 Louis Kruger has managed to reverse engineer the sensor part of the uGuru.
|
D | abituguru | 86 Sandberg <ollebull@gmail.com> has managed to reverse engineer the sensor part
|
D | hwmon-kernel-api.txt | 60 hwmon_device_register_with_groups. However, it is device managed, meaning the
|
D | abituguru-datasheet | 310 voltages which proprably safed my computer (after a reboot I managed to
|
/linux-4.4.14/fs/ |
D | namei.c | 1166 unsigned managed; in follow_managed() local 1173 while (managed = ACCESS_ONCE(path->dentry->d_flags), in follow_managed() 1174 managed &= DCACHE_MANAGED_DENTRY, in follow_managed() 1175 unlikely(managed != 0)) { in follow_managed() 1178 if (managed & DCACHE_MANAGE_TRANSIT) { in follow_managed() 1187 if (managed & DCACHE_MOUNTED) { in follow_managed() 1206 if (managed & DCACHE_NEED_AUTOMOUNT) { in follow_managed() 1357 unsigned managed; in follow_down() local 1360 while (managed = ACCESS_ONCE(path->dentry->d_flags), in follow_down() 1361 unlikely(managed & DCACHE_MANAGED_DENTRY)) { in follow_down() [all …]
|
/linux-4.4.14/Documentation/cgroups/ |
D | net_prio.txt | 52 can then be managed by administrators or other networking protocols such as
|
D | cpusets.txt | 257 This is useful both on tightly managed systems running a wide mix of 403 If the system is managed using cpusets to place independent jobs
|
D | cgroups.txt | 498 indexed by subsystem ID; this pointer is entirely managed by the
|
/linux-4.4.14/Documentation/ |
D | md.txt | 229 is set by user-space. This indicates that metadata is managed 265 reported if the metadata is externally managed. 306 managed metadata, the offset is from the beginning of the 329 managed by the md module. 330 'external' means that bitmap metadata is managed externally to 338 When metadata is managed externally, it should be set to true 415 providing an ongoing count for arrays with metadata managed by
|
D | media-framework.txt | 115 dynamically but is managed by the entity driver. Most drivers will embed the 178 managed by the entity driver. Drivers usually embed the array in a
|
D | unicode.txt | 102 NOTE: This range is now officially managed by the ConScript Unicode
|
D | workqueue.txt | 87 worker threads become idle. These worker threads are managed in so 185 managed by the system scheduler.
|
D | IRQ-domain.txt | 208 with the hardware managed by itself and may ask for services from its
|
D | cachetlb.txt | 100 translations for software managed TLB configurations.
|
D | bcache.txt | 76 Cache devices are managed as sets; multiple caches per set isn't supported yet
|
D | kobject.txt | 328 contain their own kobject, but that kobject is managed by the kset code and
|
D | applying-patches.txt | 352 These are daily snapshots of Linus' kernel tree (managed in a git
|
D | edac.txt | 242 Total memory managed by this csrow attribute file:
|
D | HOWTO | 290 These are daily snapshots of Linus' kernel tree which are managed in a
|
D | devices.txt | 3280 single-user mode. Starting with Linux 2.1.71, /dev/console is managed
|
D | kernel-parameters.txt | 3429 managed by CMA.
|
/linux-4.4.14/Documentation/sound/alsa/soc/ |
D | DPCM.txt | 217 that is managed externally. 219 Likewise a BE DAI can also set a dummy cpu DAI if the CPU DAI is managed by the 264 /* BE for codec Headset - DAI0 is dummy and managed by DSP FW */
|
/linux-4.4.14/Documentation/EDID/ |
D | HOWTO.txt | 2 in a file called xorg.conf, even broken hardware could be managed.
|
/linux-4.4.14/Documentation/vm/ |
D | pagemap.txt | 85 page is managed by the SLAB/SLOB/SLUB/SLQB kernel memory allocator 90 a free memory block managed by the buddy system allocator
|
D | unevictable-lru.txt | 84 indicate that the page is being managed on the unevictable list. 373 are inherently unevictable and are not managed on the LRU lists.
|
D | frontswap.txt | 264 of the memory managed by frontswap and back into kernel-addressable memory.
|
/linux-4.4.14/fs/f2fs/ |
D | Kconfig | 26 - major filesystem information managed by f2fs currently
|
/linux-4.4.14/Documentation/device-mapper/ |
D | persistent-data.txt | 5 that is managed in kernel. In late 2010 we were seeing that various
|
/linux-4.4.14/Documentation/thermal/ |
D | cpu-cooling-api.txt | 153 power managed regions that are implemented. Taking the example of an 159 then start from a set of reference values for each power managed
|
D | intel_powerclamp.txt | 32 level, and where active cooling is not preferred. Software managed
|
/linux-4.4.14/net/mac80211/ |
D | Kconfig | 148 bool "Verbose managed MLME output" 152 debugging messages for the managed-mode MLME. It
|
/linux-4.4.14/Documentation/devicetree/bindings/net/dsa/ |
D | dsa.txt | 68 managed entity. See
|
/linux-4.4.14/Documentation/scsi/ |
D | libsas.txt | 57 In general, the phys are managed by the LLDD and the ports 58 are managed by the SAS layer. So the phys are initialized 355 domain. It is completely managed by the SAS layer. A task
|
D | sym53c8xx_2.txt | 242 If your controller does not have NVRAM or if it is managed by the SDMS 257 QUEUE FULL status for a SCSI command. This behaviour is managed by the
|
D | ncr53c8xx.txt | 271 If your controller does not have NVRAM or if it is managed by the SDMS 286 QUEUE FULL status for a SCSI command. This behaviour is managed by the
|
/linux-4.4.14/Documentation/trace/ |
D | intel_th.txt | 50 [1] https://software.intel.com/sites/default/files/managed/d3/3c/intel-th-developer-manual.pdf
|
D | stm.txt | 79 [1] https://software.intel.com/sites/default/files/managed/d3/3c/intel-th-developer-manual.pdf
|
/linux-4.4.14/Documentation/s390/ |
D | DASD | 3 S/390's disk devices (DASDs) are managed by Linux via the DASD device
|
D | cds.txt | 106 interrupt lines managed by a specific interrupt controller and bus systems
|
/linux-4.4.14/Documentation/tpm/ |
D | xen-tpmfront.txt | 15 of the vTPM's secrets (Keys, NVRAM, etc) are managed by a vTPM Manager domain,
|
/linux-4.4.14/drivers/staging/lustre/ |
D | sysfs-fs-lustre | 616 Number of OSC targets managed by this LOV instance. 622 Number of OSC targets managed by this LOV instance that are 629 Number of MDC targets managed by this LMV instance. 635 Number of MDC targets managed by this LMV instance that are
|
/linux-4.4.14/Documentation/arm/ |
D | Porting | 73 area, and therefore managed dynamically on a process by process
|
D | kernel_mode_neon.txt | 29 The NEON/VFP register file is managed using lazy preserve (on UP systems) and
|
/linux-4.4.14/Documentation/scheduler/ |
D | sched-bwc.txt | 24 Quota and period are managed within the cpu subsystem via cgroupfs.
|
/linux-4.4.14/Documentation/networking/ |
D | dm9000.txt | 132 about link (carrier) availability. This is managed by several methods
|
D | spider_net.txt | 40 This filling and emptying is managed by three pointers, the "head" 41 and "tail" pointers, managed by the OS, and a hardware current
|
D | dccp.txt | 139 Several DCCP default parameters can be managed by the following sysctls
|
D | eql.txt | 471 able to data at over 48Kb/s [ISDN link -Simon]. I managed a
|
D | netdev-FAQ.txt | 14 The netdev list is managed (like many other Linux mailing lists) through
|
D | l2tp.txt | 69 pseudowire. These interfaces can be managed using standard Linux tools
|
D | bonding.txt | 1016 Bonding devices can be managed by hand, however, as follows. 2742 trunking). Most managed switches currently available have such 2751 802.3ad Dynamic Link Aggregation. Most managed and many unmanaged
|
D | can.txt | 986 removal of vcan network devices can be managed with the ip(8) tool:
|
/linux-4.4.14/Documentation/gpio/ |
D | sysfs.txt | 105 "base" ... same as N, the first GPIO managed by this chip
|
D | consumer.txt | 94 Device-managed variants of these functions are also defined: 133 The device-managed variants are, unsurprisingly:
|
D | gpio-legacy.txt | 464 While the pin allocation is totally managed by the pinctrl subsystem, 466 that different pin ranges in a SoC is managed by different gpio drivers. 508 from pins not managed as GPIOs. Code relying on such mechanisms will 725 "base" ... same as N, the first GPIO managed by this chip
|
D | driver.txt | 18 which is a unique number between 0 and n, n being the number of GPIOs managed by
|
/linux-4.4.14/Documentation/filesystems/ |
D | ceph.txt | 43 extremely large directories can be fragmented and managed by
|
D | nilfs2.txt | 157 Checkpoints and snapshots are managed by the following commands.
|
D | autofs4-mount-control.txt | 12 directory that is being managed in order to be able to issue control 256 Obtain and release a file descriptor for an autofs managed mount point
|
D | f2fs.txt | 161 - major file system information managed by f2fs currently
|
D | vfs.txt | 1031 be returned if someone else managed to make the automount first. If
|
D | coda.txt | 243 requesting detailed information about the persistent cache managed by
|
/linux-4.4.14/drivers/net/phy/ |
D | Kconfig | 262 tristate "Micrel KS8995MA 5-ports 10/100 managed Ethernet switch"
|
/linux-4.4.14/Documentation/laptops/ |
D | sonypi.txt | 125 - several users reported that this driver disables the BIOS-managed
|
/linux-4.4.14/Documentation/input/ |
D | iforce-protocol.txt | 2 This document describes what I managed to discover about the protocol used to
|
/linux-4.4.14/Documentation/networking/dsa/ |
D | dsa.txt | 309 - special, non-autonegotiated or non MDIO-managed PHY devices: SFPs, MoCA; a.k.a 320 the definition of a non-MDIO managed PHY as defined in 433 MoCA or other kinds of non-MDIO managed PHYs where out of band link
|
/linux-4.4.14/Documentation/power/ |
D | devices.txt | 170 decision, and it is managed by user space through a sysfs attribute: the 213 setting the flag and allowing the device to be runtime power-managed by its 216 device from being runtime power-managed. User space can check the current value 563 devices managed by the boot kernel need to be prepared for passing control back
|
D | runtime_pm.txt | 451 effectively allow the device to be power managed at run time) 456 effectively prevent the device from being power managed at run time) 771 power-managed on their own. (The prototype example is a USB interface. Entire
|
/linux-4.4.14/Documentation/arm/Samsung-S3C24XX/ |
D | Overview.txt | 141 ARM kernel series is managed by Russell King, and has a patch system
|
/linux-4.4.14/Documentation/prctl/ |
D | seccomp_filter.txt | 35 behavior and information flow should be managed with a combination of
|
/linux-4.4.14/drivers/staging/fsl-mc/ |
D | README.txt | 361 An Ethernet PHY is an off-chip, board specific component and is managed
|
/linux-4.4.14/Documentation/virtual/kvm/arm/ |
D | vgic-mapped-irqs.txt | 53 The state of forwarded physical interrupts is managed in the following way:
|
/linux-4.4.14/drivers/input/keyboard/ |
D | Kconfig | 231 If enabled the entire TCA6416 device will be managed through 248 If enabled the complete TCA8418 device will be managed through
|
/linux-4.4.14/Documentation/filesystems/caching/ |
D | object.txt | 96 Within FS-Cache, each active object is managed by its own individual state
|
D | backend-api.txt | 418 backend managed to reserve a backing block; -ENOBUFS or -ENOMEM if it
|
/linux-4.4.14/drivers/net/ethernet/marvell/ |
D | mvneta.c | 3259 const char *managed; in mvneta_probe() local 3312 err = of_property_read_string(dn, "managed", &managed); in mvneta_probe() 3314 strcmp(managed, "in-band-status") == 0); in mvneta_probe()
|
/linux-4.4.14/Documentation/powerpc/ |
D | cxl.txt | 38 unit which is part of the PCIe Host Bridge (PHB). This is managed
|
/linux-4.4.14/drivers/base/ |
D | Kconfig | 210 resource management for a managed device. devres.log can be
|
/linux-4.4.14/Documentation/arm64/ |
D | arm-acpi.txt | 11 it refers to are managed by the UEFI Forum. The specification is 316 -- be managed in a _PSx method which gets called on entry to power
|
/linux-4.4.14/Documentation/nfc/ |
D | nfc-hci.txt | 146 protocol. Those are isolated as modules managed by the HCI layer. There are
|
/linux-4.4.14/drivers/power/ |
D | Kconfig | 268 Say Y here to enable this dumb driver for batteries managed
|
/linux-4.4.14/arch/ |
D | Kconfig | 107 managed by the kernel and kept transparent to the probed
|
/linux-4.4.14/drivers/staging/unisys/Documentation/ |
D | overview.txt | 25 The back-end for each device is owned and managed by a small,
|
/linux-4.4.14/Documentation/video4linux/ |
D | videobuf | 316 Step (1) above is done by looking at the driver-managed list_head structure
|
/linux-4.4.14/drivers/misc/ |
D | Kconfig | 515 This driver allows you to declare a memory region to be managed by
|
/linux-4.4.14/drivers/net/usb/ |
D | Kconfig | 147 two-node links are most easily managed with Ethernet Bridging
|
/linux-4.4.14/drivers/char/ |
D | Kconfig | 482 has multiple functional units, inc several managed by
|
/linux-4.4.14/drivers/regulator/ |
D | Kconfig | 36 managed regulators and simple non-configurable regulators.
|
/linux-4.4.14/drivers/input/misc/ |
D | Kconfig | 241 an SMBus interface managed by the I2C Intel ICH (i801) driver,
|
/linux-4.4.14/Documentation/development-process/ |
D | 2.Process | 178 merged into the mainline repository managed by Linus Torvalds. More
|
/linux-4.4.14/Documentation/sysctl/ |
D | vm.txt | 363 256 means 1/256. # of protection pages becomes about "0.39%" of total managed
|
/linux-4.4.14/Documentation/sound/oss/ |
D | README.OSS | 314 PnP models of sound cards even you have managed to wake up the card properly. 468 they managed to make it a standard. MSS compatible cards are based on
|
/linux-4.4.14/drivers/i2c/busses/ |
D | Kconfig | 495 This driver enables managed host access to the PMIC I2C bus on select
|
/linux-4.4.14/arch/arm/ |
D | Kconfig | 1413 option to allow the additional clusters to be managed.
|