Home
last modified time | relevance | path

Searched full:nearly (Results 1 – 25 of 137) sorted by relevance

123456

/linux-5.10/Documentation/fb/
Dudlfb.rst23 setting is very flexible - able to set nearly arbitrary modes from any timing.
27 * Ability to add a nearly arbitrary number of displays to any USB 2.0
34 * The actual hardware functionality of DisplayLink chips matches nearly
/linux-5.10/include/linux/soc/ixp4xx/
Dqmgr.h48 u32 statne_h; /* 0x418 - queue nearly empty */
/linux-5.10/Documentation/maintainer/
Drebasing-and-merging.rst18 merges would be nearly impossible. Some problems encountered by
98 development cycle included 1,126 merge commits - nearly 9% of the total.
/linux-5.10/Documentation/devicetree/bindings/i2c/
Di2c-rk3x.yaml99 value since they are the same in nearly all cases.
/linux-5.10/drivers/mtd/ubi/
DKconfig68 in nearly constant time. Instead of scanning the whole MTD device it
/linux-5.10/Documentation/userspace-api/media/v4l/
Ddev-capture.rst11 digitized images in memory. Today nearly all devices can capture at full
/linux-5.10/arch/powerpc/sysdev/
Dipic.c550 * for nearly all cases. */ in ipic_mask_irq()
569 * for nearly all cases. */ in ipic_ack_irq()
592 * for nearly all cases. */ in ipic_mask_irq_and_ack()
/linux-5.10/arch/nios2/mm/
Dioremap.c172 * iounmap unmaps nearly everything, so be careful
/linux-5.10/drivers/net/wireless/intersil/orinoco/
DKconfig16 majority of the PCMCIA 802.11b cards (which are nearly all rebadges)
/linux-5.10/arch/s390/lib/
Dmem.S59 * because nearly all memset invocations in the kernel clear memory and
/linux-5.10/fs/ceph/
Dfile.c1931 loff_t nearly = round_up(offset, PAGE_SIZE); in ceph_zero_pagecache_range() local
1932 if (offset < nearly) { in ceph_zero_pagecache_range()
1933 loff_t size = nearly - offset; in ceph_zero_pagecache_range()
1999 u64 nearly, t; in ceph_zero_objects() local
2002 nearly = offset + object_set_size - 1; in ceph_zero_objects()
2003 t = nearly; in ceph_zero_objects()
2004 nearly -= do_div(t, object_set_size); in ceph_zero_objects()
2006 while (length && offset < nearly) { in ceph_zero_objects()
/linux-5.10/Documentation/devicetree/bindings/clock/
Dbaikal,bt1-ccu-pll.yaml50 biggest system interfaces in fact include nearly all of the rest SoC
/linux-5.10/drivers/mfd/
Dtps65090.c136 /* Nearly all registers have status bits mixed in, except a few */ in is_volatile_reg()
/linux-5.10/drivers/net/ethernet/8390/
DKconfig26 nearly NE2000 compatible but need a separate driver due to a few
/linux-5.10/Documentation/scsi/
Dscsi-changer.rst30 changers. But it allows to handle nearly all possible cases. It knows
/linux-5.10/Documentation/admin-guide/
Dldm.rst15 nearly 2000.
/linux-5.10/sound/firewire/fireworks/
Dfireworks_hwdep.c83 * All of tasks can read from the buffer nearly simultaneously, but the in hwdep_read_resp_buf()
/linux-5.10/Documentation/x86/
Dpti.rst74 entry. This consumes nearly 2MB of RAM once the kernel
/linux-5.10/drivers/scsi/
Dscsi_pm.c114 * hibernate nearly identically. In all cases the requirements in scsi_bus_suspend_common()
/linux-5.10/arch/m68k/mm/
Dkmap.c56 * __free_io_area unmaps nearly everything, so be careful
/linux-5.10/Documentation/networking/device_drivers/ethernet/toshiba/
Dspider_net.rst83 A typical example of the output, for a nearly idle system, might be::
/linux-5.10/Documentation/scheduler/
Dsched-design-CFS.rst127 - SCHED_BATCH: Does not preempt nearly as often as regular tasks
/linux-5.10/include/uapi/linux/
Ddm-ioctl.h91 * Beware that CHS geometry is nearly obsolete and only provided
/linux-5.10/tools/perf/pmu-events/arch/x86/silvermont/
Dcache.json12nearly full w condition which likely indicates back pressure from L2Q. It also counts requests th…
/linux-5.10/arch/xtensa/lib/
Dchecksum.S188 alignments work, but not nearly as efficiently.

123456