Home
last modified time | relevance | path

Searched refs:reasons (Results 1 – 148 of 148) sorted by relevance

/linux-4.1.27/drivers/net/wireless/iwlwifi/mvm/
Dd3.c1209 u32 reasons = status->wakeup_reasons; in iwl_mvm_report_wakeup_reasons() local
1211 if (reasons == IWL_WOWLAN_WAKEUP_BY_NON_WIRELESS) { in iwl_mvm_report_wakeup_reasons()
1216 if (reasons & IWL_WOWLAN_WAKEUP_BY_MAGIC_PACKET) in iwl_mvm_report_wakeup_reasons()
1219 if (reasons & IWL_WOWLAN_WAKEUP_BY_PATTERN) in iwl_mvm_report_wakeup_reasons()
1223 if (reasons & (IWL_WOWLAN_WAKEUP_BY_DISCONNECTION_ON_MISSED_BEACON | in iwl_mvm_report_wakeup_reasons()
1227 if (reasons & IWL_WOWLAN_WAKEUP_BY_GTK_REKEY_FAILURE) in iwl_mvm_report_wakeup_reasons()
1230 if (reasons & IWL_WOWLAN_WAKEUP_BY_RFKILL_DEASSERTED) in iwl_mvm_report_wakeup_reasons()
1233 if (reasons & IWL_WOWLAN_WAKEUP_BY_EAPOL_REQUEST) in iwl_mvm_report_wakeup_reasons()
1236 if (reasons & IWL_WOWLAN_WAKEUP_BY_FOUR_WAY_HANDSHAKE) in iwl_mvm_report_wakeup_reasons()
1239 if (reasons & IWL_WOWLAN_WAKEUP_BY_REM_WAKE_LINK_LOSS) in iwl_mvm_report_wakeup_reasons()
[all …]
/linux-4.1.27/Documentation/ABI/testing/
Dsysfs-class-net-statistics154 See the driver for the exact reasons as to why the packets were
163 a network device. See the driver for the exact reasons as to
172 FIFO error. See the driver for the exact reasons as to why the
182 reasons as to why the packets were dropped.
Dsysfs-bus-rbd30 available will fail for backwards compatibility reasons.
41 available will fail for backwards compatibility reasons.
Dsysfs-firmware-gsmi9 historical reasons this different entry-point has been
Dsysfs-class-mic.txt74 OS can shutdown because of various reasons. When read, this
/linux-4.1.27/drivers/net/wireless/iwlwifi/dvm/
Dmac80211.c523 u32 reasons = le32_to_cpu(status_data.wakeup_reason); in iwlagn_mac_resume() local
526 IWL_INFO(priv, "WoWLAN wakeup reason(s): 0x%.8x\n", reasons); in iwlagn_mac_resume()
528 if (reasons) { in iwlagn_mac_resume()
529 if (reasons & IWLAGN_WOWLAN_WAKEUP_MAGIC_PACKET) in iwlagn_mac_resume()
531 if (reasons & IWLAGN_WOWLAN_WAKEUP_PATTERN_MATCH) in iwlagn_mac_resume()
533 if (reasons & (IWLAGN_WOWLAN_WAKEUP_BEACON_MISS | in iwlagn_mac_resume()
536 if (reasons & IWLAGN_WOWLAN_WAKEUP_GTK_REKEY_FAIL) in iwlagn_mac_resume()
538 if (reasons & IWLAGN_WOWLAN_WAKEUP_EAP_IDENT_REQ) in iwlagn_mac_resume()
540 if (reasons & IWLAGN_WOWLAN_WAKEUP_4WAY_HANDSHAKE) in iwlagn_mac_resume()
/linux-4.1.27/Documentation/arm/
Dmem_alignment4 bad idea to configure it out, but Russell King has some good reasons for
18 mode isn't recommended for performance reasons (just think about the
Dkernel_mode_neon.txt19 code that runs in kernel mode. However, for performance reasons, the NEON/VFP
24 non-preemptible section for reasons outlined below.
50 For reasons of performance and simplicity, it was decided that there shall be no
DIXP4xx94 By default, the direct method is used for performance reasons. If
/linux-4.1.27/Documentation/devicetree/bindings/mmc/
Dmmc-spi-slot.txt15 binding from mmc.txt, for historical reasons.
/linux-4.1.27/Documentation/x86/x86_64/
Dcpu-hotplug-spec4 Linux/x86-64 supports CPU hotplug now. For various reasons Linux wants to
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/
Dccf.txt19 is retained for compatibility reasons, as it was already
/linux-4.1.27/Documentation/sh/
Dregister-banks.txt19 reasons. Userspace is also not able to poke at the bank1 values, so these can
/linux-4.1.27/fs/jffs2/
DLICENCE28 This exception does not invalidate any other reasons why a work based on
/linux-4.1.27/drivers/isdn/capi/
DKconfig42 If you say Y here, the capidrv interface will give verbose reasons
/linux-4.1.27/drivers/pnp/pnpbios/
DKconfig40 Unless you are debugging or have other specific reasons, it is
/linux-4.1.27/Documentation/ia64/
Defirtc.txt35 The Epoch is January 1st 1998. For backward compatibility reasons we don't
38 One of the reasons for doing it this way is to allow for EFI to still evolve
DIRQ-redir.txt19 compatibility reasons with i386.
Dfsys.txt285 __kernel_syscall_via_epc() function for historical reasons (it was
/linux-4.1.27/fs/pstore/
DKconfig59 Note that for historical reasons, the module will be named
/linux-4.1.27/Documentation/
Dsgi-ioc4.txt36 simply for historical reasons (it used to be the only IOC4 driver
Dinit.txt6 Some high-level reasons for failure (listed roughly in order of execution)
Dhw_random.txt66 NOTE: request_mem_region was removed, for three reasons:
Dthis_cpu_ops.txt116 Per cpu variables are used for performance reasons. Bouncing cache
215 so is expensive. If there are other reasons why the scheduler cannot
Dpi-futex.txt4 We are calling them lightweight for 3 reasons:
Dbinfmt_misc.txt24 reasons.
DManagementStyle82 reasons:
94 Happily, both of these reasons can be mitigated effectively by just
Dunshare.txt184 directly by unshare because of the following two reasons.
Doops-tracing.txt53 for historical reasons, and because some of the information in it still
DHOWTO23 explain some of the reasons why the community works like it does.
517 The reasons for breaking things up are the following:
Dcpu-hotplug.txt31 provisioning reasons, or for RAS purposes to keep an offending CPU off
Ddma-buf-sharing.txt404 Exporters that shoot down mappings (for any reasons) shall not do any
Dapplying-patches.txt108 a change in the middle of the file but for some reasons a few lines have
Dmd.txt89 reasons - it is the original superblock format.
DDMA-API.txt548 For reasons of efficiency, most platforms choose to track the declared
DCodingStyle93 braces. Unlike the indent size, there are few technical reasons to
DSubmittingPatches653 For these reasons, the "summary" must be no more than 70-75
Ddevices.txt3294 respectively; for historical reasons, /dev/ttyS# and /dev/ttyC#
/linux-4.1.27/Documentation/vm/
Dbalance6 There are two reasons to be requesting non __GFP_WAIT allocations:
9 whatever reasons.
Dzswap.txt68 of pages stored, and various counters for the reasons pages are rejected.
Dtranshuge.txt215 pages. This can happen for a variety of reasons but a common
270 needed special handling in futex code for similar reasons).
Dunevictable-lru.txt91 LRU list for a few reasons:
/linux-4.1.27/Documentation/input/
Dcs461x.txt19 reasons are performed: the same hardware cannot work under Win95 (blue
Drotary-encoder.txt82 signals (because of an inverting buffer or other reasons). The encoder
Dgamepad.txt69 for backwards-compatibility reasons, you need to provide fixup mappings in
/linux-4.1.27/Documentation/video4linux/
Dcafe_ccic16 The "xawtv" utility also works; gqcam does not, for unknown reasons.
Dv4l2-framework.txt1143 while a subdevice driver is holding a reference to the clock. For these reasons
/linux-4.1.27/Documentation/misc-devices/
Dc2port.txt71 However, for security reasons, the in-system flash access in not
/linux-4.1.27/fs/btrfs/
DKconfig19 expected to change unless there are strong reasons to do so. If there
/linux-4.1.27/Documentation/mmc/
Dmmc-dev-attrs.txt43 be desirable to do it in smaller chunks for three reasons:
/linux-4.1.27/Documentation/devicetree/bindings/arm/
Dfsl.txt82 which is the VF5xx and VF6xx series. Out of historical reasons, in most
/linux-4.1.27/Documentation/timers/
Dtimers-howto.txt86 that may have happened for other reasons, or at the
Dhrtimers.txt16 several reasons why such integration is hard/impossible:
/linux-4.1.27/Documentation/hwmon/
Dk10temp56 Due to technical reasons, the driver can detect only the mainboard's
Dw83627hf74 module parameter is gone for technical reasons. If you need this feature,
Dpc87360121 channels). For technical reasons, these channels are held by the VLM
Dsysfs-interface667 for compatibility reasons:
/linux-4.1.27/Documentation/s390/
DDASD61 partition. For reasons of sanity you should build your filesystem on
/linux-4.1.27/Documentation/devicetree/bindings/gpio/
Dgpio.txt18 for compatibility reasons (resolving to the "gpios" property), it is not allowed
206 compatibility reasons, and would still be required even in new device
/linux-4.1.27/Documentation/cpu-freq/
Dboost.txt81 For compatibility reasons this file and its behavior is still supported
/linux-4.1.27/Documentation/PCI/
DMSI-HOWTO.txt34 There are three reasons why using MSIs can give an advantage over
122 there are many reasons why the platform may not be able to provide the
278 there are many reasons why the platform may not be able to provide the
574 From the above three sections, you can see that there are many reasons
Dpci.txt399 There are (at least) two really good reasons for using MSI:
/linux-4.1.27/Documentation/scsi/
Dhpsa.txt11 complexity and eliminating that complexity is one of the reasons
Dscsi_eh.txt300 performance reasons and as sense information could get out of
Dscsi_fc_transport.txt270 other reasons
Dst.txt171 used). Direct i/o can be impossible because of several reasons, e.g.:
DChangeLog.1992-1997139 performance reasons.
DChangeLog.lpfc122 semantics - ELS completions worked for the wrong reasons. Also
/linux-4.1.27/Documentation/device-mapper/
Dswitch.txt58 failover reasons.
Dcache.txt200 back cache block contents later for performance reasons,
/linux-4.1.27/Documentation/gpio/
Dgpio.txt14 usable for compatibility reasons) is documented in gpio-legacy.txt.
/linux-4.1.27/arch/ia64/
DKconfig416 or have huge holes in the physical address space for other reasons.
452 # VIRTUAL_MEM_MAP has been retained for historical reasons.
/linux-4.1.27/Documentation/locking/
Drt-mutex-design.txt10 It doesn't describe the reasons why rtmutex.c exists. For that please see
16 inheritance (PI) algorithm that is used, as well as reasons for the
24 priority process wants to run. This happens for several reasons, and
689 The schedule can then wake up for a few reasons.
699 Note: For various reasons, because of timeout and signals, the steal mutex
Dspinlocks.txt112 The reasons you mustn't use these versions if you have interrupts that
Dww-mutex-design.txt212 mutexes are a natural fit for such a case for two reasons:
/linux-4.1.27/Documentation/networking/
Dxfrm_sync.txt167 to be reached. This is done for simplicity and efficiency reasons.
Dpktgen.txt41 ring-buffers for various performance reasons, and packets stalling
Dtimestamping.txt61 Timestamps may also be generated for reasons other than being
297 reasons, SCM_TSTAMP_SND is equal to zero and can be set for both
DREADME.ipw210048 For these reasons Intel cannot permit any manipulation by third parties
Darcnet.txt329 reasons yet to be determined. (Probably it's the smaller
385 RFC1201 protocol, for reasons listed above), and one XT that can't run
DREADME.ipw220061 For these reasons Intel cannot permit any manipulation by third parties
Dz8530drv.txt393 TxErrors - number of discarded Tx frames (due to various reasons)
Dppp_generic.txt50 flow-control reasons. In this case, start_xmit() should return 0
Dip-sysctl.txt296 connection but that are invalid due to any of these reasons:
1646 allowing the ADD-IP extension. For reasons of interoperability,
Dfilter.txt707 For practical reasons all eBPF programs have only one argument 'ctx' which is
Dcan.txt116 solution for a couple of reasons:
Dbonding.txt1738 For reasons of simplicity, and to support the use of adapters
/linux-4.1.27/Documentation/filesystems/nfs/
Dknfsd-stats.txt130 a strong indication, for a couple of reasons:
Dnfs-rdma.txt67 version with support for NFS/RDMA mounts, but for various reasons we
Dnfsroot.txt88 compatibility reasons.
/linux-4.1.27/sound/pci/hda/
DKconfig52 for compatibility reasons.
/linux-4.1.27/drivers/block/paride/
DTransition-notes92 For similar reasons, (3) can become not true only when ps_spinlock is released
/linux-4.1.27/Documentation/power/
Dsuspend-and-interrupts.txt115 There are very few valid reasons to use both enable_irq_wake() and the
Dbasic-pm-debugging.txt175 information about the reasons of the suspend (resume) failure. Alternatively,
Dfreezing-of-tasks.txt97 Generally speaking, there is a couple of reasons to use the freezing of tasks:
Ddevices.txt53 For these reasons not only the device driver itself, but also the
Druntime_pm.txt611 are several reasons for this, including:
/linux-4.1.27/Documentation/i2c/
Dslave-interface151 to NACK them. For those reasons, this API does not support NACK in the address
Dwriting-clients221 operation by another chip. For these reasons, explicit device
/linux-4.1.27/Documentation/spi/
Dspidev11 Some reasons you might want to use this programming interface include:
Dspi-summary85 controller; the reasons to use SPI focus on low cost and simple operation,
/linux-4.1.27/Documentation/development-process/
D1.Intro17 encounter there. There are a great many reasons why kernel code should be
97 intimidating to new developers, but there are good reasons and solid
D7.AdvancedTopics93 of the reasons why development should be done in private branches (which
D4.Coding48 on it for other reasons, but coding style changes should not be made for
/linux-4.1.27/drivers/cpufreq/
DKconfig.x8658 entry in addition to the new boost ones, for compatibility reasons.
/linux-4.1.27/Documentation/cgroups/
Dmemcg_test.txt5 Because VM is getting complex (one of reasons is memcg...), memcg's behavior
Dunified-hierarchy.txt440 general kernel APIs for good reasons. It may end up leaking internal
Dcpusets.txt769 Note that for legacy reasons, the "cpuset" filesystem exists as a
/linux-4.1.27/Documentation/isdn/
DREADME.hysdn138 Additional info about error reasons may be fetched from the log output.
DREADME.gigaset257 automatically. However, for the reasons above, the mode chosen when
DREADME22 reasons, the mailing-list's primary language is german. However mails
/linux-4.1.27/Documentation/powerpc/
Dtransactional_memory.txt173 These are defined in <asm/reg.h>, and distinguish different reasons why the
/linux-4.1.27/Documentation/sound/oss/
DOpti110 This is left for historical reasons. If you enable the
DREADME.OSS292 few other reasons to the DMA timeout message but using the SB mode seems
1426 to the driver. There are three main reasons: First I don't want to break
/linux-4.1.27/Documentation/crypto/
Dasync-tx-api.txt180 performing these operations cannot, for many platform specific reasons,
/linux-4.1.27/fs/reiserfs/
DREADME101 that start on a node aligned boundary (there are reasons to want to node
/linux-4.1.27/arch/cris/arch-v10/
DREADME.mm157 Linux/CRIS, a page is 8192 bytes (for technical reasons not equal to 4096 as in
/linux-4.1.27/drivers/thermal/
DKconfig273 CPU/SOC, for thermal safety reasons.
/linux-4.1.27/Documentation/filesystems/
Dlogfs.txt77 reasons is stored in the journal instead. Instead of data blocks, the
Doverlayfs.txt13 filesystem for various technical reasons. The expectation is that
Dgfs2-glocks.txt169 So why gather these statistics? There are several reasons
Dhpfs.txt166 reasons. If you extremely wish to update them, let me know, I'll write it (but
DLocking486 components. And there are other reasons why the current interface is a mess...
Dvfs.txt606 This may happen for data integrity reasons (i.e. 'sync'), or
/linux-4.1.27/kernel/power/
DKconfig45 of the reasons to use software suspend is that the firmware hooks
/linux-4.1.27/Documentation/frv/
Dfeatures.txt99 The reasons for doing this are: (1) the page at address 0 should be
/linux-4.1.27/Documentation/fb/
Dapi.txt300 For forward compatibility reasons applications must zero those fields, and
/linux-4.1.27/drivers/mtd/
DKconfig317 For historical reasons, by default, either a master is present or
/linux-4.1.27/Documentation/RCU/
Dtrace.txt51 Displays counts of the reasons rcu_pending() decided that RCU had
534 reasons, e.g., the grace period ended first.
/linux-4.1.27/Documentation/sysctl/
Dkernel.txt572 A small number of systems do generate NMI's for bizarre random reasons
860 the hardware, or for other reasons.
/linux-4.1.27/Documentation/usb/
Dusbmon.txt227 only returns first 48 bytes for compatibility reasons.
Dproc_usb_info.txt135 For reasons lost in the mists of time, the Port number is always
/linux-4.1.27/arch/x86/kernel/
Dentry_32.S969 # We get here for two reasons:
/linux-4.1.27/Documentation/laptops/
Dthinkpad-acpi.txt337 due to unknown reasons.
630 CAP_SYS_ADMIN capability for safety reasons, as it can interact badly
1141 safety reasons. To enable them, the module parameter "fan_control=1"
/linux-4.1.27/arch/alpha/
DKconfig585 or have huge holes in the physical address space for other reasons.
/linux-4.1.27/init/
DKconfig607 scheduling-clock interrupts for energy-efficiency reasons will
777 or energy-efficiency reasons, but the real reason it exists
792 or energy-efficiency reasons.
/linux-4.1.27/drivers/block/
DKconfig374 for historical reasons.
/linux-4.1.27/Documentation/mtd/
Dnand_ecc.txt97 And I could not reuse the ST picture anyway for copyright reasons.
/linux-4.1.27/Documentation/arm64/
Darm-acpi.txt209 Tree description for the same device. This is also one of the reasons that
/linux-4.1.27/Documentation/cdrom/
Dcdrom-standard.tex35 the widest variety of hardware devices. The reasons for this are
426 are several reasons for changing the speed of a \cdrom\ drive. Badly
/linux-4.1.27/Documentation/netlabel/
Ddraft-ietf-cipso-ipsecurity-01.txt441 datagram for reasons that the information contained can not be adequately
/linux-4.1.27/Documentation/block/
Dbiodoc.txt105 generic functionality is essential for performance or correctness reasons.
393 latency reasons)
/linux-4.1.27/Documentation/virtual/kvm/
Dtimekeeping.txt386 multiple socket systems for these reasons.
Dapi.txt3036 reasons. Further architecture-specific information is available in
3045 to unknown reasons. Further architecture-specific information is
/linux-4.1.27/net/wireless/
Dnl80211.c12647 struct nlattr *reasons; in cfg80211_report_wowlan_wakeup() local
12649 reasons = nla_nest_start(msg, NL80211_ATTR_WOWLAN_TRIGGERS); in cfg80211_report_wowlan_wakeup()
12650 if (!reasons) in cfg80211_report_wowlan_wakeup()
12714 nla_nest_end(msg, reasons); in cfg80211_report_wowlan_wakeup()
/linux-4.1.27/Documentation/security/
Dkeys.txt1383 included for two reasons:
/linux-4.1.27/arch/mips/
DKconfig2404 or have huge holes in the physical address space for other reasons.
/linux-4.1.27/drivers/staging/speakup/
Dspkguide.txt153 reasons. This has nothing to do with Speakup, it's a Linux security