[PATCH 139/159] drm/amdgpu: Fix the comment in amdgpu_gmc.h

Alex Deucher alexander.deucher at amd.com
Wed Feb 24 22:18:39 UTC 2021


From: Oak Zeng <Oak.Zeng at amd.com>

More accurate words are used to address a
code review feedback

Signed-off-by: Oak Zeng <Oak.Zeng at amd.com>
Reviewed-by: Felix Kuehling <Felix.Kuehling at amd.com>
Signed-off-by: Alex Deucher <alexander.deucher at amd.com>
---
 drivers/gpu/drm/amd/amdgpu/amdgpu_gmc.h | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_gmc.h b/drivers/gpu/drm/amd/amdgpu/amdgpu_gmc.h
index cd4592ff70ae..e57daa262150 100644
--- a/drivers/gpu/drm/amd/amdgpu/amdgpu_gmc.h
+++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_gmc.h
@@ -190,13 +190,13 @@ struct amdgpu_gmc {
 	u64			gart_end;
 	/* Frame buffer aperture of this GPU device. Different from
 	 * fb_start (see below), this only covers the local GPU device.
-	 * If use FB aperture to access FB, driver get fb_start from
+	 * If driver uses FB aperture to access FB, driver get fb_start from
 	 * MC_VM_FB_LOCATION_BASE (set by vbios) and calculate vram_start
 	 * of this local device by adding an offset inside the XGMI hive.
-	 * If use GART table for VMID0 FB access, driver finds a hole in
+	 * If driver uses GART table for VMID0 FB access, driver finds a hole in
 	 * VMID0's virtual address space to place the SYSVM aperture inside
 	 * which the first part is vram and the second part is gart (covering
-	 * sram)
+	 * system ram).
 	 */
 	u64			vram_start;
 	u64			vram_end;
-- 
2.29.2



More information about the amd-gfx mailing list