Home
last modified time | relevance | path

Searched full:properly (Results 1 – 25 of 2022) sorted by relevance

12345678910>>...81

/linux-6.15/arch/arm64/boot/dts/rockchip/
Drk3588-jaguar-pre-ict-tester.dtso75 * GPIO3_A3 requires two power rails to be properly
78 * incorrect value if VCC_1V8_S0_1 isn't properly routed,
80 * If VCC_IN_2 is properly routed, GPIO3_A3 should be
82 * GPIO3_A3 isn't properly routed due to soldering
89 * rail. It should be HIGH if all is properly soldered.
97 * GPIO3_B2 requires two power rails to be properly
100 * incorrect value if VCC_1V8_S0_1 isn't properly routed,
102 * If VCC_IN_1 is properly routed, GPIO3_B2 should be
103 * LOW. This is an issue if GPIO3_B2 isn't properly
114 * rail. It should be HIGH if all is properly soldered.
[all …]
/linux-6.15/drivers/platform/arm64/
DKconfig33 laptop where this information is not properly exposed via the
52 laptop where this information is not properly exposed via the
68 laptop where this information is not properly exposed via the
/linux-6.15/mm/
Dballoon_compaction.c36 * Driver must call this function to properly enqueue balloon pages before
66 * Driver must call this function to properly de-allocate a previous enlisted
120 * Driver must call this function to properly allocate a new balloon page.
141 * Drivers must call this function to properly enqueue a new allocated balloon
164 * Driver must call this function to properly dequeue a previously enqueued page
/linux-6.15/tools/testing/selftests/sync/
Dsync_wait.c64 "Fence did not signal properly!\n"); in test_fence_multi_timeline_wait()
70 "Fence did not signal properly!\n"); in test_fence_multi_timeline_wait()
76 "Fence did not signal properly!\n"); in test_fence_multi_timeline_wait()
/linux-6.15/arch/s390/lib/
Dtest_modules.c9 * Test that modules with many relocations are loaded properly.
32 MODULE_DESCRIPTION("KUnit test that modules with many relocations are loaded properly");
/linux-6.15/drivers/base/
Dfaux.c98 * Create a new faux device and register it in the driver core properly.
105 * everything to be properly initialized before that point in time. If the
177 * Create a new faux device and register it in the driver core properly.
184 * everything to be properly initialized before that point in time.
/linux-6.15/drivers/misc/lkdtm/
Dstackleak.c3 * This code tests that the current task stack is properly erased (filled
117 pr_err("FAIL: the thread stack is NOT properly erased!\n"); in check_stackleak_irqoff()
119 pr_info("OK: the rest of the thread stack is properly erased\n"); in check_stackleak_irqoff()
/linux-6.15/lib/
Dkobject.c326 * This function will properly initialize a kobject such that it can then
331 * the memory is cleaned up properly.
342 err_str = "must have a ktype to be initialized properly!\n"; in kobject_init()
370 pr_err("can not set name properly!\n"); in kobject_add_varg()
395 * userspace is properly notified of this kobject's creation.
398 * called to properly clean up the memory associated with the
404 * in order to properly clean up the memory associated with the object.
407 * when the use of the object is finished in order to properly free
444 * properly clean up the memory associated with the object. This is the
865 pr_err("must have a ktype to be initialized properly!\n"); in kset_register()
[all …]
/linux-6.15/Documentation/process/
Dvolatile-considered-harmful.rst23 unwanted optimization. If they are being used properly, there will be no
25 almost certainly a bug in the code somewhere. In properly-written kernel
106 been properly thought through.
/linux-6.15/Documentation/networking/dsa/
Dbcm_sf2.rst71 in order to properly configure them. By default, the SF2 pseudo-PHY address, and
86 firmware gets reloaded. The SF2 driver relies on such events to properly set its
87 MoCA interface carrier state and properly report this to the networking stack.
/linux-6.15/Documentation/hwmon/
Df71882fg.rst145 properly.
162 RPM mode, it will also set fan#_full_speed properly, if it does not then
163 fan control will not work properly, unless you set a sane fan#_full_speed
Dadm1025.rst52 properly, you'll have a wrong +12V reading or a wrong VID reading. The way
54 process, assuming that the BIOS set it up properly beforehand. If it turns
/linux-6.15/arch/powerpc/kernel/
Drethook.c49 * When going back through (1), we need regs->nip to be setup properly in arch_rethook_fixup_return()
52 * the link register properly so that the subsequent 'blr' in in arch_rethook_fixup_return()
/linux-6.15/Documentation/arch/x86/i386/
DIO-APIC.rst81 between the PIRQ lines. (distributing IRQ sources properly is not a
107 permute all IRQ numbers properly ... it will take some time though. An
109 won't function properly (e.g. if it's inserted as a module).
/linux-6.15/tools/testing/selftests/arm64/signal/testcases/
Dfake_sigreturn_bad_size.c47 /* and terminate properly */ in fake_sigreturn_bad_size_run()
63 /* and terminate properly */ in fake_sigreturn_bad_size_run()
/linux-6.15/Documentation/scheduler/
Dsched-debug.rst23 detect if pages are properly placed or if the data should be migrated to a
31 behaviour. If pages are properly placed then the scan delay increases,
/linux-6.15/drivers/base/firmware_loader/
Dsysfs.h38 /* These getters are vetted to use int properly */
44 /* These setters are vetted to use int properly */
/linux-6.15/Documentation/core-api/
Dkobject.rst123 The ktype is required for a kobject to be created properly, as every kobject
131 properly. If the kobject is to be associated with a specific kset,
151 To properly access the name of the kobject, use the function
177 have been initialized properly, as userspace will instantly start to look
413 any other sysfs housekeeping will be handled for the caller properly.
432 For a more complete example of using ksets and kobjects properly, see the
/linux-6.15/arch/m68k/ifpsp060/
DREADME58 was connected properly; hex image
62 connected properly; hex image
/linux-6.15/tools/power/cpupower/debug/kernel/
Dcpufreq-test_tsc.c4 * to work properly after cpufreq transitions. Needs ACPI to work
5 * properly.
/linux-6.15/Documentation/livepatch/
Dcumulative-patches.rst81 that are necessary to properly replace any older patch.
102 callback. It is called only when the livepatch is properly disabled.
/linux-6.15/include/uapi/mtd/
Dubi-user.h32 * control device. The caller has to properly fill and pass
47 * device. A &struct ubi_mkvol_req object has to be properly filled and a
61 * device should be used. A &struct ubi_rsvol_req object has to be properly
69 * has to be properly filled and a pointer to it has to be passed to the ioctl.
338 * shortened in order to make it properly aligned. The alignment has to be
346 * BLOBs, without caring about how to properly align them.
/linux-6.15/tools/testing/selftests/mqueue/
Dmq_open_tests.c358 * properly follows the default settings in main()
380 printf("Kernel properly honors default setting " in main()
397 printf("Kernel properly limits default values " in main()
400 printf("Kernel does not properly set default " in main()
416 printf("Kernel properly fails to create queue when " in main()
/linux-6.15/Documentation/scsi/
Dqlogicfas.rst59 Make sure it works properly under DOS. You should also do an initial FDISK
72 that the file copied properly. (Turn off all caching when doing these
/linux-6.15/fs/smb/server/
Dunicode.c149 * string is always properly null terminated and fits in the destination
155 * deal with those characters properly. In the event that we get some of
156 * those characters, they won't be translated properly.
217 /* properly null-terminate string */ in smb_from_utf16()

12345678910>>...81