| /linux-4.4.14/include/uapi/linux/ |
| H A D | kexec.h | 11 /* kexec flags for different usage scenarios */
|
| H A D | shm.h | 13 * be as large possible without facilitating scenarios where userspace
|
| H A D | msg.h | 60 * scenarios where userspace causes overflows when adjusting the limits via
|
| /linux-4.4.14/drivers/staging/wilc1000/ |
| H A D | wilc_msgqueue.c | 138 /* other non-timeout scenarios */ wilc_mq_recv()
|
| /linux-4.4.14/drivers/net/wireless/ath/ath5k/ |
| H A D | gpio.c | 37 * "power" LED and LED_1 is our "network activity" LED but many scenarios
|
| H A D | base.c | 1854 * Note2: On sectored scenarios it's possible to have ath5k_beacon_setup()
|
| H A D | phy.c | 2177 * Using the above we support the following scenarios:
|
| /linux-4.4.14/drivers/net/wireless/iwlwifi/mvm/ |
| H A D | sf.c | 101 * Aging and idle timeouts for the different possible scenarios
129 * Aging and idle timeouts for the different possible scenarios
|
| H A D | phy-ctxt.c | 161 /* In scenarios where we only ever use a single-stream rates, iwl_mvm_phy_ctxt_cmd_data()
|
| H A D | fw.c | 614 * initialization, but in firmware restart scenarios they iwl_mvm_load_ucode_wait_alive()
|
| /linux-4.4.14/drivers/pinctrl/ |
| H A D | pinctrl-pistachio.c | 81 const int *scenarios; member in struct:pistachio_function
508 .scenarios = pistachio_##_name##_scenarios, \
978 if (pf->scenarios) { pistachio_pinmux_enable()
980 if (pf->scenarios[i] == group) pistachio_pinmux_enable()
|
| /linux-4.4.14/include/linux/ |
| H A D | balloon_compaction.h | 12 * performing balloon page compaction. In order to sort out these racy scenarios
|
| H A D | ide.h | 117 * 100% of all crazy scenarios here is not necessary.
|
| /linux-4.4.14/tools/testing/selftests/memfd/ |
| H A D | fuse_test.c | 292 * Note that in real scenarios, there might be a mixture of both, but main()
|
| /linux-4.4.14/drivers/net/wireless/ti/wlcore/ |
| H A D | scan.c | 368 /* we assume failure so that timeout scenarios are handled correctly */ wlcore_scan()
|
| H A D | main.c | 2584 * in some very corner case HW recovery scenarios its possible to wl1271_op_add_interface()
|
| /linux-4.4.14/arch/x86/kernel/fpu/ |
| H A D | signal.c | 31 /* Check for the first magic field and other error scenarios. */ check_for_xstate()
|
| /linux-4.4.14/include/xen/interface/io/ |
| H A D | netif.h | 96 * error. This includes scenarios where more (or fewer) queues were
|
| /linux-4.4.14/drivers/usb/musb/ |
| H A D | cppi_dma.c | 671 * Consider a 1KB bulk RX buffer in two scenarios: (a) it's fed two 300 byte
673 * (Full speed transfers have similar scenarios.)
701 * (or maybe its peripheral side counterpart) to flag (a) scenarios as errors
|
| /linux-4.4.14/drivers/crypto/nx/ |
| H A D | nx-aes-gcm.c | 265 /* For scenarios where the input message is zero length, AES CTR mode gcm_empty()
|
| /linux-4.4.14/fs/f2fs/ |
| H A D | recovery.c | 18 * Roll forward recovery scenarios.
|
| /linux-4.4.14/tools/testing/selftests/seccomp/ |
| H A D | test_harness.h | 360 * not thread-safe, but it should be fine in most sane test scenarios.
|
| /linux-4.4.14/drivers/scsi/aic7xxx/ |
| H A D | aic79xx_osm.h | 234 * scenarios that the Linux mid-layer code just doesn't know how to
|
| H A D | aic7xxx_osm.h | 246 * scenarios that the Linux mid-layer code just doesn't know how to
|
| /linux-4.4.14/drivers/net/ethernet/qlogic/qed/ |
| H A D | qed_spq.c | 813 /* This is relatively uncommon - depends on scenarios qed_spq_completion()
|
| /linux-4.4.14/arch/x86/kernel/ |
| H A D | nmi.c | 390 * There are scenarios where we may accidentally swallow default_do_nmi()
|
| /linux-4.4.14/arch/ia64/include/asm/ |
| H A D | sal.h | 790 * are for the bott rendezvous, MCAs and INIT scenarios.
|
| /linux-4.4.14/net/mac80211/ |
| H A D | tdls.c | 138 * this doesn't happen in real world scenarios. ieee80211_tdls_add_supp_channels()
959 * In some testing scenarios, we send a request and response. ieee80211_tdls_prep_mgmt_packet()
|
| H A D | ieee80211_i.h | 542 * otherwise, in scenarios where we hardly get any traffic out
|
| H A D | mlme.c | 295 * It seems possible that there are still scenarios with CSA or real ieee80211_determine_chantype()
|
| H A D | tx.c | 2440 * With the locking, such scenarios cannot happen as the check for the ieee80211_check_fast_xmit()
|
| /linux-4.4.14/drivers/mtd/ |
| H A D | mtdcore.c | 951 * In blackbox flight recorder like scenarios we want to make successful writes
|
| /linux-4.4.14/drivers/mtd/spi-nor/ |
| H A D | spi-nor.c | 658 * scenarios excluding small sectors there is config option that can be
|
| /linux-4.4.14/drivers/net/wireless/libertas/ |
| H A D | if_sdio.c | 62 * scenarios. This flag is initialized as FALSE in case the card
|
| /linux-4.4.14/drivers/net/wireless/ath/ath9k/ |
| H A D | common-spectral.c | 587 * four scenarios here: ath_cmn_process_fft()
|
| /linux-4.4.14/drivers/powercap/ |
| H A D | intel_rapl.c | 1376 * other scenarios.
|
| /linux-4.4.14/drivers/edac/ |
| H A D | edac_mc.c | 260 * on such scenarios, as grouping the multiple ranks require drivers change.
|
| /linux-4.4.14/drivers/bluetooth/ |
| H A D | btmrvl_sdio.c | 65 * scenarios. This flag is initialized as FALSE in case the card
|
| /linux-4.4.14/drivers/clk/mediatek/ |
| H A D | clk-mt8173.c | 26 * clocks may change their rate on different products or different scenarios.
|
| /linux-4.4.14/kernel/ |
| H A D | seccomp.c | 360 * This avoids scenarios where unprivileged tasks can affect the seccomp_prepare_filter()
|
| H A D | futex.c | 91 * In futex wake up scenarios where no tasks are blocked on a futex, taking
95 * checked by the waker, avoiding scenarios like the following:
|
| /linux-4.4.14/include/scsi/ |
| H A D | libfc.h | 484 * function pointer. It can be called in two scenarios: if a timeout
|
| /linux-4.4.14/sound/soc/intel/skylake/ |
| H A D | skl-topology.c | 757 * scenarios
|
| /linux-4.4.14/drivers/scsi/csiostor/ |
| H A D | csio_scsi.c | 930 * There are the following possible scenarios: csio_scsis_aborting()
946 * The first 3 scenarios are treated as succesful abort csio_scsis_aborting()
|
| /linux-4.4.14/net/sctp/ |
| H A D | sm_sideeffect.c | 1378 * multihoming stale cookie scenarios, the following sctp_cmd_interpreter()
|
| /linux-4.4.14/sound/soc/davinci/ |
| H A D | davinci-mcasp.c | 1873 * scenarios. Maximum number tdm slots is 32 and there cannot davinci_mcasp_probe()
|
| /linux-4.4.14/kernel/locking/ |
| H A D | lockdep.c | 14 * - lock inversion scenarios
1818 * any of these scenarios could lead to a deadlock.
2125 * any of these scenarios could lead to a deadlock. If validate_chain()
|
| /linux-4.4.14/drivers/usb/gadget/udc/bdc/ |
| H A D | bdc_ep.c | 578 * disconnect scenarios, continue with dconfig bdc_ep_disable()
|
| /linux-4.4.14/drivers/usb/serial/ |
| H A D | mos7720.c | 435 * that avoids two scenarios: (1) a port operation is called after usbserial
|
| /linux-4.4.14/drivers/net/wireless/mwifiex/ |
| H A D | sdio.c | 43 * scenarios. This flag is initialized as FALSE in case the card
|
| /linux-4.4.14/drivers/net/ethernet/natsemi/ |
| H A D | ns83820.c | 497 * an attempt to reduce bus traffic under heavy load scenarios.
|
| /linux-4.4.14/drivers/net/wireless/brcm80211/brcmfmac/ |
| H A D | p2p.c | 1764 /* Abort scan even for VSDB scenarios. Scan gets aborted in brcmf_p2p_send_action_frame()
|
| /linux-4.4.14/drivers/net/usb/ |
| H A D | usbnet.c | 732 // during some PM-driven resume scenarios,
|
| H A D | lan78xx.c | 1613 /* during some PM-driven resume scenarios,
|
| /linux-4.4.14/drivers/net/ |
| H A D | xen-netfront.c | 1699 * and split event channel scenarios. write_queue_xenstore_keys()
|
| /linux-4.4.14/drivers/cpufreq/ |
| H A D | cpufreq.c | 431 * double invocations are very low. Moreover, there are scenarios cpufreq_freq_transition_begin()
|
| /linux-4.4.14/drivers/base/power/ |
| H A D | domain.c | 406 * callbacks for other purposes than runtime PM. In those scenarios pm_genpd_runtime_suspend()
|
| /linux-4.4.14/crypto/ |
| H A D | drbg.c | 97 * Just mix both scenarios above.
|
| /linux-4.4.14/kernel/irq/ |
| H A D | manage.c | 68 * Do not use this for shutdown scenarios where you must be sure
|
| /linux-4.4.14/fs/ubifs/ |
| H A D | super.c | 693 * When budgeting we assume worst-case scenarios when the pages are not init_constants_sb()
|
| /linux-4.4.14/drivers/video/fbdev/omap2/dss/ |
| H A D | dsi.c | 3402 * all scenarios are satisfied.
3433 * interleaved in LP so that all scenarios are satisfied.
|
| /linux-4.4.14/include/net/ |
| H A D | mac80211.h | 2568 * 10 hardware queues to handle different scenarios:
3155 * before associated. In multi-channel scenarios, a virtual interface is
4569 * Usual scenarios are drivers that cannot continue the scheduled scan
|
| /linux-4.4.14/drivers/input/mouse/ |
| H A D | alps.c | 1480 * can not distinguish between these 2 scenarios but alps_handle_interleaved_ps2()
|
| /linux-4.4.14/drivers/net/wireless/ath/ath10k/ |
| H A D | pci.c | 2246 * able to recover the device from all possible fail scenarios. ath10k_pci_qca988x_chip_reset()
|
| /linux-4.4.14/kernel/sched/ |
| H A D | fair.c | 5430 * a few fun cases generally called infeasible weight scenarios.
6643 * In the presence of smp nice balancing, certain scenarios can have calculate_imbalance()
|
| /linux-4.4.14/drivers/scsi/ufs/ |
| H A D | ufshcd.c | 3239 * device to alert host in critical scenarios.
|
| /linux-4.4.14/net/ipv4/ |
| H A D | tcp_output.c | 445 * (but it may well be that other scenarios fail similarly).
|
| /linux-4.4.14/drivers/gpu/drm/i915/ |
| H A D | intel_dp.c | 5816 * DRRS saves power by switching to low RR based on usage scenarios.
|
| H A D | intel_display.c | 8658 * RGB<->YCbCr scenarios as well.
|
| /linux-4.4.14/net/bluetooth/ |
| H A D | mgmt.c | 7696 * NOT_POWERED. We cover both scenarios here since later in mgmt_powered()
|
| /linux-4.4.14/arch/x86/kvm/ |
| H A D | x86.c | 2410 * scenarios where it sets bit #19, itself documented as kvm_get_msr_common()
|
| /linux-4.4.14/drivers/media/dvb-frontends/drx39xyj/ |
| H A D | drxj.c | 4346 /* TODO: implement fallback scenarios */ adc_synchronization()
|
| /linux-4.4.14/drivers/net/ethernet/broadcom/bnx2x/ |
| H A D | bnx2x_main.c | 14300 /* Don't remove the netdevice, as there are scenarios which will cause bnx2x_shutdown()
|
| /linux-4.4.14/arch/m68k/ifpsp060/src/ |
| H A D | fpsp.S | 3988 # In any of the above scenarios, if a _mem_read() or _mem_write() #
|