FROMLIST: drm/msm: restore GEM-related IOCTLs for KMS devices#757
Open
yashgupta2126 wants to merge 2 commits intoqualcomm-linux:tech/mm/drmfrom
Open
FROMLIST: drm/msm: restore GEM-related IOCTLs for KMS devices#757yashgupta2126 wants to merge 2 commits intoqualcomm-linux:tech/mm/drmfrom
yashgupta2126 wants to merge 2 commits intoqualcomm-linux:tech/mm/drmfrom
Conversation
On targets with multiple display subsystems, such as SA8775P, the GPU binds to the first display subsystem that probes. This implicit binding prevents subsequent display subsystems from probing successfully, breaking multi-display support. Enable separate_gpu_kms by default to decouple GPU and display subsystem probing. This allows each display subsystem to initialize independently, ensuring that all display subsystems are probed. Link: https://lore.kernel.org/all/[email protected]/ Signed-off-by: Mahadevan P <[email protected]> Signed-off-by: Yash Gupta <[email protected]>
The MSM GBM backend uses MSM_GEM_NEW to allocate GEM buffers from the KMS driver, imports them into the GPU driver (msm or kgsl) and then uses them for rendering / blending. Commit 98f11fd ("drm/msm: Take the ioctls away from the KMS-only driver") dropped all IOCTLs from the MSM KMS devices, pointing out the need to use dumb buffers, however dumb buffers should not be used by the GPU for rendering. Restore GEM-related IOCTLs for the KMS devices. Fixes: 98f11fd ("drm/msm: Take the ioctls away from the KMS-only driver") Signed-off-by: Dmitry Baryshkov <[email protected]> Link: https://lore.kernel.org/all/[email protected]/ Signed-off-by: Yash Gupta <[email protected]>
riteshk-quic
force-pushed
the
tech/mm/drm
branch
from
54bffff to
52fe805
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The MSM GBM backend uses MSM_GEM_NEW to allocate GEM buffers from the KMS driver, imports them into the GPU driver (msm or kgsl) and then uses them for rendering / blending. Commit 98f11fd ("drm/msm: Take the ioctls away from the KMS-only driver") dropped all IOCTLs from the MSM KMS devices, pointing out the need to use dumb buffers, however dumb buffers should not be used by the GPU for rendering. Restore GEM-related IOCTLs for the KMS devices.
Fixes: 98f11fd ("drm/msm: Take the ioctls away from the KMS-only driver")
Link: https://lore.kernel.org/all/[email protected]/