diff options
| author | Philip Chen <philipchen@chromium.org> | 2021-10-30 20:08:50 +0300 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2021-12-17 12:30:14 +0300 |
| commit | dc6c1eddfc7424233d4f365db4e8ba8d4e807f09 (patch) | |
| tree | de3abb06edd4218ec170bfae76ef92216620b41d /arch | |
| parent | d2db21103d84fd7655699e07d027e2061981388d (diff) | |
| download | linux-dc6c1eddfc7424233d4f365db4e8ba8d4e807f09.tar.xz | |
drm/msm/dsi: set default num_data_lanes
[ Upstream commit cd92cc187c053ab010a1570e2d61d68394a5c725 ]
If "data_lanes" property of the dsi output endpoint is missing in
the DT, num_data_lanes would be 0 by default, which could cause
dsi_host_attach() to fail if dsi->lanes is set to a non-zero value
by the bridge driver.
According to the binding document of msm dsi controller, the
input/output endpoint of the controller is expected to have 4 lanes.
So let's set num_data_lanes to 4 by default.
Signed-off-by: Philip Chen <philipchen@chromium.org>
Reviewed-by: Douglas Anderson <dianders@chromium.org>
Reviewed-by: Stephen Boyd <swboyd@chromium.org>
Link: https://lore.kernel.org/r/20211030100812.1.I6cd9af36b723fed277d34539d3b2ba4ca233ad2d@changeid
Signed-off-by: Rob Clark <robdclark@chromium.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions