Searched full:suggests (Results 1 – 25 of 147) sorted by relevance
123456
| /linux-6.14.4/Documentation/devicetree/bindings/mfd/ |
| D | aspeed-gfx.txt | 3 The Aspeed SoC Display Controller primarily does as its name suggests, but also
|
| /linux-6.14.4/Documentation/ABI/testing/ |
| D | sysfs-bus-platform-devices-occ-hwmon | 8 completely read by a user. As the name suggests, only the data
|
| D | sysfs-platform-at91 | 15 The workaround in the errata suggests not to use the
|
| /linux-6.14.4/arch/csky/include/asm/ |
| D | vdso.h | 13 * addresses even when the code model suggests those low addresses would not
|
| /linux-6.14.4/Documentation/driver-api/iio/ |
| D | intro.rst | 13 or temperature measurement. :doc:`Input <../input>` is, as its name suggests,
|
| /linux-6.14.4/Documentation/hwmon/ |
| D | nsa320.rst | 57 of one unit but suggests that the Zyxel provided delay values include a
|
| /linux-6.14.4/Documentation/iio/ |
| D | opt4060.rst | 52 The data sheet suggests using the scaled values to normalize the scaled R, G
|
| /linux-6.14.4/drivers/net/wireless/zydas/zd1211rw/ |
| D | zd_rf.h | 46 * flag is set in the POD. The vendor driver suggests that this should
|
| /linux-6.14.4/sound/pci/cs5535audio/ |
| D | cs5535audio_pm.c | 22 AC97 codec to shutdown. the amd spec suggests in snd_cs5535audio_stop_hardware()
|
| /linux-6.14.4/samples/kprobes/ |
| D | kretprobe_example.c | 100 /* nmissed > 0 suggests that maxactive was set too low. */ in kretprobe_exit()
|
| /linux-6.14.4/arch/mips/mm/ |
| D | dma-noncoherent.c | 39 * Presence of MAARs suggests that the CPU supports in cpu_needs_post_dma_flush()
|
| /linux-6.14.4/Documentation/devicetree/bindings/serial/ |
| D | nvidia,tegra20-hsuart.yaml | 73 received data will have corruption/invalid framing errors. Parker errata suggests adjusting
|
| /linux-6.14.4/Documentation/devicetree/bindings/power/avs/ |
| D | qcom,cpr.yaml | 17 temperature, etc. and suggests adjustments to the voltage to save power
|
| /linux-6.14.4/Documentation/locking/ |
| D | lockstat.rst | 8 As the name suggests, it provides statistics on locks.
185 (subclass starts from 0), since in this case, as line 50 suggests,
|
| D | lockdep-design.rst | 22 dependency can be understood as lock order, where L1 -> L2 suggests that
107 The character '-' suggests irq is disabled because if otherwise the
240 As the name suggests, lockdep_assert_held* family of macros assert that a
|
| /linux-6.14.4/drivers/char/agp/ |
| D | Kconfig | 37 For the ALi-chipset question, ALi suggests you refer to
|
| /linux-6.14.4/drivers/comedi/drivers/ |
| D | ni_labpc_isadma.c | 23 /* utility function that suggests a dma transfer size in bytes */
|
| /linux-6.14.4/sound/pci/ |
| D | azt3328.h | 13 /* the driver initialisation suggests a layout of 4 areas
169 * thus it suggests influence on PCM only!!
|
| /linux-6.14.4/net/core/ |
| D | secure_seq.c | 43 * suggests using a 250 kHz clock. in seq_scale()
|
| /linux-6.14.4/drivers/gpu/drm/amd/display/dc/hubp/dcn32/ |
| D | dcn32_hubp.c | 73 /* Programming guide suggests CURSOR_REQ_MODE = 1 for SubVP: in hubp32_prepare_subvp_buffering()
|
| /linux-6.14.4/tools/memory-model/Documentation/ |
| D | glossary.txt | 70 name suggests. And in a great many cases, a pair of CPUs is all
|
| /linux-6.14.4/arch/x86/kernel/cpu/ |
| D | topology_amd.c | 51 * suggests it's the topmost bit(s) of the CPU cores area, but in store_node()
|
| /linux-6.14.4/Documentation/livepatch/ |
| D | shadow-vars.rst | 211 suggests how to handle the parent object.
|
| /linux-6.14.4/sound/isa/wavefront/ |
| D | wavefront_fx.c | 121 report "never idle", which suggests that this test should in snd_wavefront_fx_detect()
|
| /linux-6.14.4/drivers/power/supply/ |
| D | generic-adc-battery.c | 34 * gab_chan_name suggests the standard channel names for commonly used
|
123456