-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'msm-next' of git://people.freedesktop.org/~robclark/lin…
…ux into drm-next The big things this time around are: 1) support for hw cursor on newer mdp5 devices (snapdragon 820+, tested on db820c) 2) dsi encoder cleanup 3) gpu dt bindings cleanup so we can get the gpu nodes merged upstream * 'msm-next' of git://people.freedesktop.org/~robclark/linux: (32 commits) drm/msm: return -EFAULT if copy_from_user() fails drm/msm/dsi: Add PHY/PLL for 8x96 drm/msm/dsi: Add new method to calculate 14nm PHY timings drm/msm/dsi: Move PHY operations out of host drm/msm/dsi: Reset both PHYs before clock operation for dual DSI drm/msm/dsi: Pass down use case to PHY drm/msm/dsi: Return more timings from PHY to host drm/msm/dsi: Add a PHY op that initializes version specific stuff drm/msm/dsi: Add 8x96 info in dsi_cfg drm/msm/dsi: Don't error if a DSI host doesn't have a device connected drm/msm/mdp5: Add support for legacy cursor updates drm/msm/mdp5: Refactor mdp5_plane_atomic_check drm/msm/mdp5: Add cursor planes drm/msm/mdp5: Misc cursor plane bits drm/msm/mdp5: Configure COLOR3_OUT propagation drm/msm/mdp5: Use plane helpers to configure src/dst rectangles drm/msm/mdp5: Prepare CRTC/LM for empty stages drm/msm/mdp5: Create only as many CRTCs as we need drm/msm/mdp5: cfg: Change count to unsigned int drm/msm/mdp5: Create single encoder per interface (INTF) ...
- Loading branch information
Showing
45 changed files
with
2,712 additions
and
556 deletions.
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,52 +1,38 @@ | ||
Qualcomm adreno/snapdragon GPU | ||
|
||
Required properties: | ||
- compatible: "qcom,adreno-3xx" | ||
- compatible: "qcom,adreno-XYZ.W", "qcom,adreno" | ||
for example: "qcom,adreno-306.0", "qcom,adreno" | ||
Note that you need to list the less specific "qcom,adreno" (since this | ||
is what the device is matched on), in addition to the more specific | ||
with the chip-id. | ||
- reg: Physical base address and length of the controller's registers. | ||
- interrupts: The interrupt signal from the gpu. | ||
- clocks: device clocks | ||
See ../clocks/clock-bindings.txt for details. | ||
- clock-names: the following clocks are required: | ||
* "core_clk" | ||
* "iface_clk" | ||
* "mem_iface_clk" | ||
- qcom,chipid: gpu chip-id. Note this may become optional for future | ||
devices if we can reliably read the chipid from hw | ||
- qcom,gpu-pwrlevels: list of operating points | ||
- compatible: "qcom,gpu-pwrlevels" | ||
- for each qcom,gpu-pwrlevel: | ||
- qcom,gpu-freq: requested gpu clock speed | ||
- NOTE: downstream android driver defines additional parameters to | ||
configure memory bandwidth scaling per OPP. | ||
* "core" | ||
* "iface" | ||
* "mem_iface" | ||
|
||
Example: | ||
|
||
/ { | ||
... | ||
|
||
gpu: qcom,kgsl-3d0@4300000 { | ||
compatible = "qcom,adreno-3xx"; | ||
compatible = "qcom,adreno-320.2", "qcom,adreno"; | ||
reg = <0x04300000 0x20000>; | ||
reg-names = "kgsl_3d0_reg_memory"; | ||
interrupts = <GIC_SPI 80 0>; | ||
interrupt-names = "kgsl_3d0_irq"; | ||
clock-names = | ||
"core_clk", | ||
"iface_clk", | ||
"mem_iface_clk"; | ||
"core", | ||
"iface", | ||
"mem_iface"; | ||
clocks = | ||
<&mmcc GFX3D_CLK>, | ||
<&mmcc GFX3D_AHB_CLK>, | ||
<&mmcc MMSS_IMEM_AHB_CLK>; | ||
qcom,chipid = <0x03020100>; | ||
qcom,gpu-pwrlevels { | ||
compatible = "qcom,gpu-pwrlevels"; | ||
qcom,gpu-pwrlevel@0 { | ||
qcom,gpu-freq = <450000000>; | ||
}; | ||
qcom,gpu-pwrlevel@1 { | ||
qcom,gpu-freq = <27000000>; | ||
}; | ||
}; | ||
}; | ||
}; |
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.