kernel.git/drivers/gpu/drm/msm/dsi/phy, branch linux-4.9.y

drm/msm/dsi: Correct io_start for MSM8994 (20nm PHY)

2021-03-03T16:44:39Z

[ Upstream commit 33a7808ce1aea6e2edc1af25db25928137940c02 ] The previous registers were *almost* correct, but instead of PHYs, they were pointing at DSI PLLs, resulting in the PHY id autodetection failing miserably. Fixes: dcefc117cc19 ("drm/msm/dsi: Add support for msm8x94") Signed-off-by: Konrad Dybcio Signed-off-by: Rob Clark Signed-off-by: Sasha Levin

drm/msm/dsi: Don't get DSI index from DT

2016-07-16T14:09:02Z

The DSI host and PHY driver currently expects the DT bindings to provide custom properties "qcom,dsi-host-index" and "qcom,dsi-phy-index" so that the driver can identify which DSI instance it is. The binding isn't acceptable, but the driver still needs to figure out what its instance id. This is now done by storing the mmio starting addresses for each DSI instance in every SoC version in the driver. The driver then identifies the index number by trying to match the stored address with comparing the resource start address we get from DT. We don't have compatible strings for DSI PHY on each SoC, but only the DSI PHY type. We only support one SoC version for each PHY type, so we get away doing the same thing above for the PHY driver. We can revisit this when we support two SoCs with the same DSI PHY. Signed-off-by: Archit Taneja Signed-off-by: Rob Clark

drm/msm/dsi: Fix regulator API abuse

2016-05-08T14:22:17Z

The voltage changing code in this driver is broken and should be removed. The driver sets a single, exact voltage on probe. Unless there is a very good reason for this (which should be documented in comments) constraints like this need to be set via the machine constraints, voltage setting in a driver is expected to be used in cases where the voltage varies at runtime. In addition client drivers should almost never be calling regulator_can_set_voltage(), if the device needs to set a voltage it needs to set the voltage and the regulator core will handle the case where the regulator is fixed voltage. If the driver simply skips setting the voltage if it doesn't have permission then it should just not bother in the first place. Originally authored by Mark Brown Remove the min/max voltage data entries per SoC managed by the driver. These aren't needed as we don't try to set voltages any more. Mention in comments the voltages that each regulator expects. Signed-off-by: Archit Taneja Signed-off-by: Rob Clark

drm/msm/dsi: Add support for 28nm PHY on 8960

2015-12-14T15:40:06Z

DSI PHY on MSM8960 and APQ8064 is a 28nm PHY that's different from the supported 28nm LP PHY found in newer chips. Add support for the new PHY. Signed-off-by: Archit Taneja Signed-off-by: Rob Clark

drm/msm/dsi: Updata LNn_CFG4 register settings for 28nm PHY

2015-10-22T19:39:54Z

The current settings for 28nm PHY data lane CFG4 registers do not work with certain panels. This change is to modify them to hw recommended values. Signed-off-by: Hai Li Signed-off-by: Rob Clark

drm: msm: dsi: Don't attempt changing voltage of switches

2015-10-22T19:39:53Z

In some configurations the supplies are voltage switches and not LDOs, making the set voltage call to fail. Check with the regulator framework if the supply can change voltage before attempting. Signed-off-by: Bjorn Andersson Reviewed-by: Archit Taneja Signed-off-by: Rob Clark

drm/msm/dsi: Make each PHY type compilation independent

2015-08-15T22:27:29Z

On a certain platform, only one type of DSI PHY is used. This change allows the user to only compile the PHY type which is being used. Signed-off-by: Hai Li Signed-off-by: Rob Clark

drm/msm/dsi: Split PHY drivers to separate files

2015-08-15T22:27:28Z

This change moves each PHY type specific code into separate files. Signed-off-by: Hai Li Signed-off-by: Rob Clark