Home
last modified time | relevance | path

Searched refs:managed (Results 1 – 125 of 125) sorted by relevance

/linux-4.4.14/drivers/of/
Dof_mdio.c290 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/
Dicmpv6.h48 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/
Ddevres.txt14 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/
Dcs35l32.txt19 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/
Dsysfs-class-iommu6 IOMMU drivers are able to link devices managed by a
Dsysfs-devices-power45 + "auto\n" to allow the device to be power managed at run time;
46 + "on\n" to prevent the device from being power managed;
Dsysfs-bus-coresight-devices-etm3x9 configured and managed automatically by the coresight framework.
Dsysfs-bus-coresight-devices-etm4x9 configured and managed automatically by the coresight framework.
/linux-4.4.14/Documentation/devicetree/bindings/soc/ti/
Dkeystone-navigator-qmss.txt31 -- 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/
DKconfig30 4) A kernel interface for receiving callbacks when a managed
/linux-4.4.14/arch/arm/boot/dts/
Dk2hk-netcp.dtsi27 managed-queues = <0 0x2000>;
39 managed-queues = <0x2000 0x2000>;
Dk2l-netcp.dtsi27 managed-queues = <0 0x2000>;
Dk2e-netcp.dtsi27 managed-queues = <0 0x2000>;
Darmada-370-dlink-dns327l.dts189 /* Ensure these are managed by hardware */
/linux-4.4.14/Documentation/devicetree/bindings/mfd/
Daxp20x.txt26 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/
Drenesas,r8a7778-cpg-clocks.txt17 SoC devices that are part of the CPG/MSTP Clock Domain and can be power-managed
Drenesas,r8a7779-cpg-clocks.txt19 SoC devices that are part of the CPG/MSTP Clock Domain and can be power-managed
Drenesas,rz-cpg-clocks.txt21 SoC devices that are part of the CPG/MSTP Clock Domain and can be power-managed
Drenesas,rcar-gen2-cpg-clocks.txt27 SoC devices that are part of the CPG/MSTP Clock Domain and can be power-managed
Drenesas,cpg-mssr.txt36 power-managed through Module Standby should refer to the CPG device
/linux-4.4.14/Documentation/devicetree/bindings/mmc/
Dtmio_mmc.txt4 devices is managed by either MFD drivers or by the sh_mobile_sdhi platform
/linux-4.4.14/drivers/net/ethernet/sfc/
DKconfig29 This exposes the on-board firmware-managed sensors as a
/linux-4.4.14/Documentation/devicetree/bindings/net/
Dfixed-link.txt5 normal MDIO-managed PHY device. For those situations, a Device Tree
Dethernet.txt28 - managed: string, specifies the PHY management type. Supported values are:
/linux-4.4.14/drivers/net/ethernet/micrel/
DKconfig33 ethernet switch chip (managed, VLAN, QoS) from Micrel or
/linux-4.4.14/Documentation/devicetree/bindings/phy/
Dphy-bindings.txt15 regulator will be managed during the PHY power on/off sequence.
/linux-4.4.14/Documentation/devicetree/bindings/misc/
Dsram.txt3 Simple IO memory regions to be managed by the genalloc API.
/linux-4.4.14/Documentation/devicetree/bindings/gpio/
Dgpio-mvebu.txt18 managed by this GPIO bank. There can be more than one interrupt
Drenesas,gpio-rcar.txt25 - gpio-ranges: Range of pins managed by the GPIO controller.
/linux-4.4.14/Documentation/devicetree/bindings/pinctrl/
Dabilis,tb10x-iomux.txt38 All other ports of the chip are not multiplexed and thus not managed by this
/linux-4.4.14/include/uapi/sound/
Dcompress_params.h267 __u32 managed; member
/linux-4.4.14/Documentation/hwmon/
Dabituguru354 Louis Kruger has managed to reverse engineer the sensor part of the uGuru.
Dabituguru86 Sandberg <ollebull@gmail.com> has managed to reverse engineer the sensor part
Dhwmon-kernel-api.txt60 hwmon_device_register_with_groups. However, it is device managed, meaning the
Dabituguru-datasheet310 voltages which proprably safed my computer (after a reboot I managed to
/linux-4.4.14/fs/
Dnamei.c1166 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/
Dnet_prio.txt52 can then be managed by administrators or other networking protocols such as
Dcpusets.txt257 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
Dcgroups.txt498 indexed by subsystem ID; this pointer is entirely managed by the
/linux-4.4.14/Documentation/
Dmd.txt229 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
Dmedia-framework.txt115 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
Dunicode.txt102 NOTE: This range is now officially managed by the ConScript Unicode
Dworkqueue.txt87 worker threads become idle. These worker threads are managed in so
185 managed by the system scheduler.
DIRQ-domain.txt208 with the hardware managed by itself and may ask for services from its
Dcachetlb.txt100 translations for software managed TLB configurations.
Dbcache.txt76 Cache devices are managed as sets; multiple caches per set isn't supported yet
Dkobject.txt328 contain their own kobject, but that kobject is managed by the kset code and
Dapplying-patches.txt352 These are daily snapshots of Linus' kernel tree (managed in a git
Dedac.txt242 Total memory managed by this csrow attribute file:
DHOWTO290 These are daily snapshots of Linus' kernel tree which are managed in a
Ddevices.txt3280 single-user mode. Starting with Linux 2.1.71, /dev/console is managed
Dkernel-parameters.txt3429 managed by CMA.
/linux-4.4.14/Documentation/sound/alsa/soc/
DDPCM.txt217 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/
DHOWTO.txt2 in a file called xorg.conf, even broken hardware could be managed.
/linux-4.4.14/Documentation/vm/
Dpagemap.txt85 page is managed by the SLAB/SLOB/SLUB/SLQB kernel memory allocator
90 a free memory block managed by the buddy system allocator
Dunevictable-lru.txt84 indicate that the page is being managed on the unevictable list.
373 are inherently unevictable and are not managed on the LRU lists.
Dfrontswap.txt264 of the memory managed by frontswap and back into kernel-addressable memory.
/linux-4.4.14/fs/f2fs/
DKconfig26 - major filesystem information managed by f2fs currently
/linux-4.4.14/Documentation/device-mapper/
Dpersistent-data.txt5 that is managed in kernel. In late 2010 we were seeing that various
/linux-4.4.14/Documentation/thermal/
Dcpu-cooling-api.txt153 power managed regions that are implemented. Taking the example of an
159 then start from a set of reference values for each power managed
Dintel_powerclamp.txt32 level, and where active cooling is not preferred. Software managed
/linux-4.4.14/net/mac80211/
DKconfig148 bool "Verbose managed MLME output"
152 debugging messages for the managed-mode MLME. It
/linux-4.4.14/Documentation/devicetree/bindings/net/dsa/
Ddsa.txt68 managed entity. See
/linux-4.4.14/Documentation/scsi/
Dlibsas.txt57 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
Dsym53c8xx_2.txt242 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
Dncr53c8xx.txt271 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/
Dintel_th.txt50 [1] https://software.intel.com/sites/default/files/managed/d3/3c/intel-th-developer-manual.pdf
Dstm.txt79 [1] https://software.intel.com/sites/default/files/managed/d3/3c/intel-th-developer-manual.pdf
/linux-4.4.14/Documentation/s390/
DDASD3 S/390's disk devices (DASDs) are managed by Linux via the DASD device
Dcds.txt106 interrupt lines managed by a specific interrupt controller and bus systems
/linux-4.4.14/Documentation/tpm/
Dxen-tpmfront.txt15 of the vTPM's secrets (Keys, NVRAM, etc) are managed by a vTPM Manager domain,
/linux-4.4.14/drivers/staging/lustre/
Dsysfs-fs-lustre616 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/
DPorting73 area, and therefore managed dynamically on a process by process
Dkernel_mode_neon.txt29 The NEON/VFP register file is managed using lazy preserve (on UP systems) and
/linux-4.4.14/Documentation/scheduler/
Dsched-bwc.txt24 Quota and period are managed within the cpu subsystem via cgroupfs.
/linux-4.4.14/Documentation/networking/
Ddm9000.txt132 about link (carrier) availability. This is managed by several methods
Dspider_net.txt40 This filling and emptying is managed by three pointers, the "head"
41 and "tail" pointers, managed by the OS, and a hardware current
Ddccp.txt139 Several DCCP default parameters can be managed by the following sysctls
Deql.txt471 able to data at over 48Kb/s [ISDN link -Simon]. I managed a
Dnetdev-FAQ.txt14 The netdev list is managed (like many other Linux mailing lists) through
Dl2tp.txt69 pseudowire. These interfaces can be managed using standard Linux tools
Dbonding.txt1016 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
Dcan.txt986 removal of vcan network devices can be managed with the ip(8) tool:
/linux-4.4.14/Documentation/gpio/
Dsysfs.txt105 "base" ... same as N, the first GPIO managed by this chip
Dconsumer.txt94 Device-managed variants of these functions are also defined:
133 The device-managed variants are, unsurprisingly:
Dgpio-legacy.txt464 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
Ddriver.txt18 which is a unique number between 0 and n, n being the number of GPIOs managed by
/linux-4.4.14/Documentation/filesystems/
Dceph.txt43 extremely large directories can be fragmented and managed by
Dnilfs2.txt157 Checkpoints and snapshots are managed by the following commands.
Dautofs4-mount-control.txt12 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
Df2fs.txt161 - major file system information managed by f2fs currently
Dvfs.txt1031 be returned if someone else managed to make the automount first. If
Dcoda.txt243 requesting detailed information about the persistent cache managed by
/linux-4.4.14/drivers/net/phy/
DKconfig262 tristate "Micrel KS8995MA 5-ports 10/100 managed Ethernet switch"
/linux-4.4.14/Documentation/laptops/
Dsonypi.txt125 - several users reported that this driver disables the BIOS-managed
/linux-4.4.14/Documentation/input/
Diforce-protocol.txt2 This document describes what I managed to discover about the protocol used to
/linux-4.4.14/Documentation/networking/dsa/
Ddsa.txt309 - 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/
Ddevices.txt170 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
Druntime_pm.txt451 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/
DOverview.txt141 ARM kernel series is managed by Russell King, and has a patch system
/linux-4.4.14/Documentation/prctl/
Dseccomp_filter.txt35 behavior and information flow should be managed with a combination of
/linux-4.4.14/drivers/staging/fsl-mc/
DREADME.txt361 An Ethernet PHY is an off-chip, board specific component and is managed
/linux-4.4.14/Documentation/virtual/kvm/arm/
Dvgic-mapped-irqs.txt53 The state of forwarded physical interrupts is managed in the following way:
/linux-4.4.14/drivers/input/keyboard/
DKconfig231 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/
Dobject.txt96 Within FS-Cache, each active object is managed by its own individual state
Dbackend-api.txt418 backend managed to reserve a backing block; -ENOBUFS or -ENOMEM if it
/linux-4.4.14/drivers/net/ethernet/marvell/
Dmvneta.c3259 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/
Dcxl.txt38 unit which is part of the PCIe Host Bridge (PHB). This is managed
/linux-4.4.14/drivers/base/
DKconfig210 resource management for a managed device. devres.log can be
/linux-4.4.14/Documentation/arm64/
Darm-acpi.txt11 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/
Dnfc-hci.txt146 protocol. Those are isolated as modules managed by the HCI layer. There are
/linux-4.4.14/drivers/power/
DKconfig268 Say Y here to enable this dumb driver for batteries managed
/linux-4.4.14/arch/
DKconfig107 managed by the kernel and kept transparent to the probed
/linux-4.4.14/drivers/staging/unisys/Documentation/
Doverview.txt25 The back-end for each device is owned and managed by a small,
/linux-4.4.14/Documentation/video4linux/
Dvideobuf316 Step (1) above is done by looking at the driver-managed list_head structure
/linux-4.4.14/drivers/misc/
DKconfig515 This driver allows you to declare a memory region to be managed by
/linux-4.4.14/drivers/net/usb/
DKconfig147 two-node links are most easily managed with Ethernet Bridging
/linux-4.4.14/drivers/char/
DKconfig482 has multiple functional units, inc several managed by
/linux-4.4.14/drivers/regulator/
DKconfig36 managed regulators and simple non-configurable regulators.
/linux-4.4.14/drivers/input/misc/
DKconfig241 an SMBus interface managed by the I2C Intel ICH (i801) driver,
/linux-4.4.14/Documentation/development-process/
D2.Process178 merged into the mainline repository managed by Linus Torvalds. More
/linux-4.4.14/Documentation/sysctl/
Dvm.txt363 256 means 1/256. # of protection pages becomes about "0.39%" of total managed
/linux-4.4.14/Documentation/sound/oss/
DREADME.OSS314 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/
DKconfig495 This driver enables managed host access to the PMIC I2C bus on select
/linux-4.4.14/arch/arm/
DKconfig1413 option to allow the additional clusters to be managed.