Home
last modified time | relevance | path

Searched full:believed (Results 1 – 25 of 30) sorted by relevance

12

/Linux-v5.15/Documentation/devicetree/bindings/iio/humidity/
Ddht11.yaml14 interface. It is believed the part is made by aosong but don't have
/Linux-v5.15/tools/arch/sparc/include/asm/
Dbarrier_64.h12 * It used to be believed that the memory barrier had to be right in the
/Linux-v5.15/arch/sparc/include/asm/
Dbarrier_64.h10 * It used to be believed that the memory barrier had to be right in the
/Linux-v5.15/arch/arm/crypto/
DKconfig114 believed to be invulnerable to cache timing attacks.
/Linux-v5.15/arch/powerpc/include/asm/
Dpmac_feature.h56 #define PMAC_TYPE_COMET 0x20 /* Believed to be PowerBook 2400 */
57 #define PMAC_TYPE_HOOPER 0x21 /* Believed to be PowerBook 3400 */
/Linux-v5.15/Documentation/admin-guide/nfs/
Dnfs-client.rst45 anything that is believed to be unique across all NFS clients. An
/Linux-v5.15/Documentation/usb/
Dgadget_multi.rst124 believed that it should (read: "I have no idea whether it will") work
Dehci.rst52 It's believed to do all the right PCI magic so that I/O works even on
/Linux-v5.15/Documentation/power/
Dpower_supply_class.rst15 the attributes provided are believed to be universally applicable to any
/Linux-v5.15/arch/alpha/lib/
Dev6-clear_user.S27 * The believed purpose of only updating $0 after a store is that a signal
/Linux-v5.15/LICENSES/preferred/
DGPL-2.0245 This section is intended to make thoroughly clear what is believed to
DLGPL-2.0387 This section is intended to make thoroughly clear what is believed to
DLGPL-2.1405 This section is intended to make thoroughly clear what is believed to
/Linux-v5.15/tools/usb/usbip/
DCOPYING226 This section is intended to make thoroughly clear what is believed to
/Linux-v5.15/drivers/net/ethernet/sfc/falcon/
Dtxc43128_phy.c282 * (PHY<->MAC) as this is believed less likely to upset Falcon in txc_apply_defaults()
/Linux-v5.15/drivers/net/ethernet/natsemi/
Dmacsonic.c274 documentation is to be believed) */ in mac_onboard_sonic_probe()
/Linux-v5.15/drivers/staging/olpc_dcon/
Dolpc_dcon.c109 * The smbus doesn't always come back due to what is believed to be
/Linux-v5.15/include/linux/regulator/
Ddriver.h98 * still believed to not be damaged but that a board sepcific
/Linux-v5.15/Documentation/filesystems/
Dlocking.rst6 It is (believed to be) up-to-date. *Please*, if you change anything in
/Linux-v5.15/drivers/char/
Drandom.c83 * exposing the internal state of the entropy pool. It is believed to
97 * not believed to be feasible, but there is a remote possibility.
/Linux-v5.15/Documentation/RCU/Design/Requirements/
DRequirements.rst1031 counter, which is currently believed to be an acceptably long time.
1730 sometimes by a large factor. If RCU naively believed the firmware, as it
2683 sockets or cores. Such spreading and alignment is currently believed to
/Linux-v5.15/drivers/media/usb/cx231xx/
Dcx231xx-cards.c670 /* This board is believed to have a hardware encoding chip
/Linux-v5.15/arch/mips/
DKconfig1154 # Attribute bits. It is believed that the uncached access through
/Linux-v5.15/drivers/usb/serial/
Dcp210x.c1657 * are made unavailable by configuring the use of GPIO. This is believed to be
/Linux-v5.15/drivers/vme/bridges/
Dvme_tsi148.c1331 * that reading the data we have just written is safe. It is believed in tsi148_master_write()

12