tjh.dev / kernel
Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux
1
fork

Configure Feed

Select the types of activity you want to include in your feed.

Documentation: Fix driver-api typos

Corrected a few spelling mistakes

functionalty ==> functionality
in Documentation/driver-api/cxl/devices/device-types.rst

adjascent ==> adjacent
in Documentation/driver-api/cxl/platform/example-configurations/one-dev-per-hb.rst

succeessful ==> successful
in Documentation/driver-api/thermal/exynos_thermal_emulation.rst

Signed-off-by: Ranganath V N <vnranganath.20@gmail.com>
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Link: https://lore.kernel.org/r/20250814184304.20448-1-vnranganath.20@gmail.com

authored by

Ranganath V N and committed by
Jonathan Corbet 6cf5f13e 6865cb19

+9 -9
+1 -1
Documentation/driver-api/cxl/devices/device-types.rst
··· 22 22 Typically used for initialization, configuration, and I/O access for anything 23 23 other than memory (CXL.mem) or cache (CXL.cache) operations. 24 24 25 - The Linux CXL driver exposes access to .io functionalty via the various sysfs 25 + The Linux CXL driver exposes access to .io functionality via the various sysfs 26 26 interfaces and /dev/cxl/ devices (which exposes direct access to device 27 27 mailboxes). 28 28
+1 -1
Documentation/driver-api/cxl/platform/example-configurations/one-dev-per-hb.rst
··· 10 10 Things to note: 11 11 12 12 * Cross-Bridge interleave is not being used. 13 - * The expanders are in two separate but adjascent memory regions. 13 + * The expanders are in two separate but adjacent memory regions. 14 14 * This CEDT/SRAT describes one node per device 15 15 * The expanders have the same performance and will be in the same memory tier. 16 16
+7 -7
Documentation/driver-api/thermal/exynos_thermal_emulation.rst
··· 28 28 delay of changing temperature. However, this node only uses same delay 29 29 of real sensing time, 938us.) 30 30 31 - Exynos emulation mode requires synchronous of value changing and 32 - enabling. It means when you want to update the any value of delay or 33 - next temperature, then you have to enable emulation mode at the same 34 - time. (Or you have to keep the mode enabling.) If you don't, it fails to 35 - change the value to updated one and just use last succeessful value 36 - repeatedly. That's why this node gives users the right to change 37 - termerpature only. Just one interface makes it more simply to use. 31 + Exynos emulation mode requires that value changes and enabling are performed 32 + synchronously. This means that when you want to update any value, such as the 33 + delay or the next temperature, you must enable emulation mode at the same 34 + time (or keep the mode enabled). If you do not, the value will fail to update 35 + and the last successful value will continue to be used. For this reason, 36 + this node only allows users to change the temperature. Providing a single 37 + interface makes it simpler to use. 38 38 39 39 Disabling emulation mode only requires writing value 0 to sysfs node. 40 40