BMC/Intel-BMC/linux.git/drivers/gpu/drm/msm/dsi, branch dev-4.7

drm/msm: Centralize connector registration/unregistration

2016-05-08T14:22:19+00:00

Move the drm_connector registration from the encoder(HDMI/DSI etc) drivers to the msm platform driver. This will simplify the task of ensuring that the connectors are registered only after the drm_device itself is registered. The connectors' destroy ops are made to use kzalloc instead of devm_kzalloc to ensure that that the connectors can be successfully unregistered when the msm driver module is removed. The memory for the connectors is unallocated when drm_mode_config_cleanup() is called during either during an error or during driver remove. Signed-off-by: Archit Taneja Signed-off-by: Rob Clark

drm/msm/dsi: Fix regulator API abuse

2016-05-08T14:22:17+00:00

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: update generated headers

2016-03-03T16:55:27+00:00

Pull in additional regs needed for a430, etc. Signed-off-by: Rob Clark

drm/msm/dsi: fix definition of msm_dsi_pll_28nm_8960_init()

2016-03-03T16:55:26+00:00

This fixes the following build failure: drivers/gpu/drm/msm/dsi/pll/dsi_pll_28nm.o: In function `msm_dsi_pll_28nm_8960_init': dsi_pll_28nm.c:(.text+0x1198): multiple definition of `msm_dsi_pll_28nm_8960_init' drivers/gpu/drm/msm/dsi/pll/dsi_pll.o:dsi_pll.c:(.text+0x0): first defined here Signed-off-by: Luis Henriques Acked-by: Archit Taneja Signed-off-by: Rob Clark

drm/msm/dsi: Parse DSI lanes via DT

2016-03-03T16:55:20+00:00

The DSI driver is currently unaware of how the DSI physical data lanes are mapped to the logical lanes provided by the DSI controller. Create a DT binding "qcom,data-lane-map" that provides this information on a given platform. The MSM DSI controller is restricted in terms of what all mappings it can support. The lane polarity is fixed for all the lanes, the clock lanes are fixed, and the data lanes can be swapped among each other only for a few combinations. Apply these restrictions when we parse the DT data. Cc: devicetree@vger.kernel.org Cc: Rob Herring Cc: Tomi Valkeinen Signed-off-by: Archit Taneja Signed-off-by: Rob Clark Acked-by: Rob Herring

drm/msm/dsi: Drop VDD regulator for MSM8916

2016-03-02T21:19:47+00:00

VDD regulator input was specified for MSM8916. It turns our that this regulator is used for the display panels used on MSM8916 platforms, but not the DSI controller itself. Drop this regulator from the list. Reported-by: Vinay Simha Signed-off-by: Archit Taneja Signed-off-by: Rob Clark

drm/msm/dsi: Remove incorrect warning on host attach

2016-03-02T21:19:46+00:00

With the implementation of of_graph parsing, it isn't any longer necessary for msm_host->device node to be same as dsi->dev.of_node. This only holds true when the connected device is also a child of the dsi_host. In the case of external bridge chips belonging to a different control bus, these are guaranteed to be different. Signed-off-by: Archit Taneja Signed-off-by: Rob Clark

drm/msm/dsi: Added missing mutex_unlock

2015-12-14T16:50:57+00:00

in case of failed to get iova, function was returning without releasing the mutex. Added it. Signed-off-by: Saurabh Sengar Signed-off-by: Rob Clark

drm/msm/dsi: Enable MMSS SPFB port via syscon

2015-12-14T15:40:50+00:00

For DSIv2 to work, we need to enable MMSS_AHB_ARB_MASTER_PORT in MMSS_SFPB. We enable the required bitfield by retrieving MMSS_SFPB regmap pointer via syscon. Signed-off-by: Archit Taneja Signed-off-by: Rob Clark

drm/msm/dsi: Don't use iommu for command TX buffer for DSIv2

2015-12-14T15:40:45+00:00

We currently use iommu allocated DMA buffers for sending DSI commands. DSIv2 doesn't have a port connected to the MDP iommu. Therefore, it can't use iommu allocated buffers to fetch DSI commands. Use a regular contiguous DMA buffer if we are DSIv2. Signed-off-by: Archit Taneja Signed-off-by: Rob Clark