Home
last modified time | relevance | path

Searched full:understood (Results 1 – 25 of 82) sorted by relevance

1234

/linux/Documentation/devicetree/bindings/sound/
H A Drockchip,rk3576-sai.yaml78 This property's absence is to be understood as only one receiving lane
92 This property's absence is to be understood as only one transmitting lane
/linux/security/smack/
H A DKconfig29 access rule set once the behavior is well understood.
/linux/drivers/gpu/drm/nouveau/nvkm/subdev/therm/
H A Dgf100.c56 * TODO: Fermi clockgating isn't understood fully yet, so we don't specify any
/linux/rust/
H A Dbindgen_parameters33 # `seccomp`'s comment gets understood as a doctest
/linux/include/linux/device-id/
H A Dusb.h54 * a pointer to a descriptor understood by the driver, or perhaps
/linux/drivers/gpu/drm/nouveau/nvkm/subdev/mmu/
H A Dnv50.c36 * 0x01/0x02 are values understood by the VRAM allocator, in nv50_mmu_kind()
/linux/net/dccp/
H A Dfeat.h
/linux/Documentation/devicetree/bindings/hwmon/
H A Dntc-thermistor.yaml48 called "connected ground" and "connected positive" and shall be understood as
/linux/drivers/net/ethernet/intel/ice/
H A Dice_sched.h12 * This header file stores everything that is needed for broadly understood
/linux/drivers/media/radio/
H A Dradio-terratec.c92 rest = freq * 10 + 10700; /* I once had understood what is going on here */ in terratec_s_frequency()
/linux/Documentation/security/
H A Dself-protection.rst147 understood is that of the stack buffer overflow in which the return
164 A less well understood attack is using a bug that triggers the
/linux/drivers/platform/raspberrypi/vchiq-mmal/
H A Dmmal-encodings.h61 /** SAND Video (YUVUV128) format, native format understood by VideoCore.
/linux/include/linux/
H A Dhte.h90 * @line_id: The logical ID understood by the consumers and providers.
/linux/arch/m68k/include/asm/
H A Dmac_psc.h25 * not understood as there seems to be only one input and one output buffer
/linux/drivers/pci/controller/
H A Dpci-hyperv.c2248 * @hbus: Root PCI bus, as understood by this driver
2312 * @hbus: Root PCI bus, as understood by this driver
2514 * @hbus: Root PCI bus, as understood by this driver
2645 * @hbus: Root PCI bus, as understood by this driver
2824 * @hbus: Root PCI bus, as understood by this driver
2869 * @hbus: Root PCI bus, as understood by this driver
2905 * @hbus: Root PCI bus, as understood by this driver
3298 * @hbus: Root PCI bus, as understood by this driver
3323 * @hbus: Root PCI bus, as understood by this driver
3401 * @hbus: Root PCI bus, as understood by this driver
/linux/Documentation/spi/
H A Dspidev.rst71 be understood by udev or mdev (udev replacement from BusyBox; it's less
/linux/Documentation/fb/
H A Dsisfb.rst135 off Disable sisfb. This option is only understood if sisfb is
/linux/drivers/phy/intel/
H A Dphy-intel-lgm-emmc.c136 * extra long to lock for reasons that aren't understood. In some in intel_emmc_phy_power()
H A Dphy-intel-keembay-emmc.c169 * extra long to lock for reasons that aren't understood. In some in keembay_emmc_phy_power()
/linux/drivers/parport/
H A Dprobe.c96 pr_warn("%s probe: warning, class '%s' not understood\n", in parse_data()
/linux/Documentation/PCI/
H A Dacpi-info.rst36 table. _CRS allows that because it is generic and understood by the old
/linux/Documentation/dev-tools/
H A Dgcov.rst102 The actual gcov data file as understood by the gcov
/linux/Documentation/process/
H A D3.Early-stage.rst79 you have not understood. The Linux kernel is large and has a number of
/linux/Documentation/networking/device_drivers/can/
H A Dcan327.rst282 The ELM327 will reply with OK when a command is understood, and with ?
/linux/include/uapi/drm/
H A Dvmwgfx_drm.h191 * @flags: Surface flags as understood by the host.
192 * @format: Surface format as understood by the host.
483 * @format: Format of the overlay as understood by the host.

1234