aboutsummaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/flamegraph.py
diff options
context:
space:
mode:
authorPhilip Chen <philipchen@chromium.org>2021-10-29 15:27:41 -0700
committerBjorn Andersson <bjorn.andersson@linaro.org>2021-11-20 16:19:58 -0600
commit0417a86b200b4da1dff73e9f4bd7743346e5565b (patch)
treeaba2a2ceb0d7ee0c9f3863f9d4606b3ffb27c189 /tools/perf/scripts/python/flamegraph.py
parentarm64: dts: qcom: sc7180: Include gpio.h in edp bridge dts (diff)
downloadlinux-0417a86b200b4da1dff73e9f4bd7743346e5565b.tar.gz
linux-0417a86b200b4da1dff73e9f4bd7743346e5565b.zip
arm64: dts: qcom: sc7180: Specify "data-lanes" for DSI host output
MSM DSI host driver actually parses "data-lanes" in DT and compare it with the number of DSI lanes the bridge driver sets for mipi_dsi_device. So we need to always specify "data-lanes" for the DSI host output. As of now, "data-lanes" is added to ti-sn65dsi86 dts fragment, but missing in parade-ps8640 dts fragment, which requires a fixup. Since we'll do 4-lane DSI regardless of which bridge chip is used, instead of adding "data-lanes" to parade-ps8640 dts fragment, let's just move "data-lanes" from the bridge dts to sc7180-trogdor.dtsi. Signed-off-by: Philip Chen <philipchen@chromium.org> Reviewed-by: Stephen Boyd <swboyd@chromium.org> Reviewed-by: Douglas Anderson <dianders@chromium.org> Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org> Link: https://lore.kernel.org/r/20211029152647.v3.2.If23c83a786fc4d318a1986f43803f22b4b1d82cd@changeid
Diffstat (limited to 'tools/perf/scripts/python/flamegraph.py')
0 files changed, 0 insertions, 0 deletions