Home
last modified time | relevance | path

Searched full:fundamental (Results 1 – 25 of 105) sorted by relevance

12345

/linux/Documentation/PCI/
H A Dpci-error-recovery.rst258 soft reset(default) and fundamental(optional) reset.
266 Powerpc fundamental reset is supported by PCI Express cards only
271 Optional fundamental reset is provided to support a limited number
316 Drivers for PCI Express cards that require a fundamental reset must
321 + /* Set EEH reset type to fundamental if required by hba */
/linux/Documentation/devicetree/bindings/iio/frequency/
H A Dadi,adf4350.yaml137 adi,aux-output-fundamental-enable:
140 Selects fundamental VCO output on the auxiliary RF output.
/linux/Documentation/driver-api/surface_aggregator/
H A Dinternal.rst81 ``RQID``). This layer basically provides a fundamental interface to the SAM
106 Packets are the fundamental transmission unit of the SSH protocol. They are
155 The packet queue is the first of the two fundamental collections in the
168 The pending set is the second of the two fundamental collections in the
359 The request queue is the first of the two fundamental collections in the
374 The pending set is the second of the two fundamental collections in the
/linux/drivers/misc/genwqe/
H A Dcard_base.c792 * genwqe_pci_fundamental_reset() - trigger a PCIe fundamental reset on the slot
806 * save state and issue PCIe fundamental reset in genwqe_pci_fundamental_reset()
839 /* Try recoverying the card with fundamental reset */ in genwqe_platform_recovery()
862 * Set the appropriate register and call fundamental reset to reaload the card
880 * partition on PCIe hot or fundamental reset in genwqe_reload_bistream()
888 * A fundamental reset failure can be caused in genwqe_reload_bistream()
1026 * If it's supported by the platform, we try a fundamental reset in genwqe_health_thread()
1122 /* EEH recovery requires PCIe fundamental reset */ in genwqe_pci_setup()
/linux/Documentation/userspace-api/media/v4l/
H A Dselections-common.rst10 similar, there's one fundamental difference between the two. On
/linux/drivers/cxl/
H A DMakefile4 # - 'core' first for fundamental init
/linux/tools/include/linux/
H A Dbits.h46 * such as long and unsigned long. The fundamental problem is
/linux/include/linux/
H A Dbits.h46 * such as long and unsigned long. The fundamental problem is
/linux/Documentation/devicetree/bindings/pci/
H A Dpci.txt29 GPIO and apply fundamental reset to endpoints.
/linux/fs/f2fs/
H A DKconfig22 addressing the fundamental issues in LFS, which are snowball effect
/linux/Documentation/process/
H A D1.Intro.rst141 internal interface is a deliberate design decision; it allows fundamental
179 - Contribution of code is the fundamental action which makes the whole
/linux/Documentation/driver-api/thermal/
H A Dcpu-cooling-api.rst103 running time dynamic power coefficient in fundamental units of
/linux/Documentation/filesystems/xfs/
H A Dxfs-delayed-logging-design.rst344 Hence it can be seen that the relogging operation is fundamental to the correct
390 is the fundamental goal of delayed logging.
401 the relogging concept fundamental to the XFS journalling subsystem, this is
431 The fundamental requirements for delayed logging in XFS are simple:
583 transaction, nor does the log replay code. The only fundamental limit is that
902 A fundamental requirement for the CIL is that accesses through transaction
/linux/drivers/gpu/drm/i915/gt/uc/
H A Dintel_uc.h66 * the HW and use them is a fundamental issue (e.g. no memory for our
/linux/Documentation/admin-guide/cgroup-v1/
H A Dpids.rst12 place, PIDs are a fundamental resource. As such, PID exhaustion must be
/linux/include/uapi/linux/netfilter/
H A Dx_tables.h89 * containing all the fundamental data types that are used in ipt_entry,
/linux/Documentation/scheduler/
H A Dsched-nice-design.rst53 But the fundamental HZ-sensitive property for nice+19 still remained,
/linux/Documentation/RCU/
H A DUP.rst47 its arguments would cause it to fail to make the fundamental guarantee
/linux/Documentation/arch/arm/omap/
H A Domap_pm.rst19 - specify PM parameters in terms of fundamental units, such as
/linux/arch/powerpc/kernel/
H A Deeh.c786 * Each device might have its preferred reset type: fundamental or
825 * the appropriate flags, performing a fundamental or hot reset, and then
840 * Determine the type of reset to perform - hot or fundamental. in eeh_pe_reset_full()
842 * PE requires a fundamental reset. in eeh_pe_reset_full()
1452 * indicated type, either fundamental reset or hot reset.
/linux/Documentation/driver-api/cxl/
H A Dmaturity-map.rst48 All of the fundamental enumeration an object model of the subsystem is
/linux/arch/powerpc/platforms/powernv/
H A Deeh-powernv.c772 * for fundamental or hot reset during deassert phase. in pnv_eeh_root_reset()
1043 * (usually bus#1), we apply hot or fundamental reset on the root port. in pnv_eeh_reset()
1097 * Fundamental resets need to be handled internally to EEH since the in pnv_eeh_reset()
1098 * PCI core doesn't really have a concept of a fundamental reset, in pnv_eeh_reset()
/linux/Documentation/dev-tools/kunit/
H A Darchitecture.rst26 The test case is the fundamental unit in KUnit. KUnit test cases are organised
/linux/Documentation/timers/
H A Dhrtimers.rst32 timing inaccuracies. Cascading is a fundamental property of the timer
/linux/Documentation/firmware-guide/acpi/
H A Dosi.rst82 But _OS had fundamental problems. First, the BIOS needed to know the name

12345