- 20 Sep, 2023 31 commits
-
-
Dmitry Baryshkov authored
Follow the rest of the platforms and add "ref" clocks to both PCIe PHYs found on the Qualcomm SM8150 platform. Fixes: a1c86c68 ("arm64: dts: qcom: sm8150: Add PCIe nodes") Signed-off-by:
Dmitry Baryshkov <dmitry.baryshkov@linaro.org> Link: https://lore.kernel.org/r/20230820142035.89903-15-dmitry.baryshkov@linaro.orgSigned-off-by:
Bjorn Andersson <andersson@kernel.org>
-
Dmitry Baryshkov authored
Change the PCIe QMP PHY to use newer style of QMP PHY bindings (single resource region, no per-PHY subnodes). Reviewed-by:
Konrad Dybcio <konrad.dybcio@linaro.org> Signed-off-by:
-
Dmitry Baryshkov authored
Change the PCIe QMP PHY to use newer style of QMP PHY bindings (single resource region, no per-PHY subnodes). While we are at it, rename PHY nodes to `phy@`. Signed-off-by:
-
Dmitry Baryshkov authored
Change the PCIe QMP PHY to use newer style of QMP PHY bindings (single resource region, no per-PHY subnodes). Signed-off-by:
-
Dmitry Baryshkov authored
Change the PCIe QMP PHY to use newer style of QMP PHY bindings (single resource region, no per-PHY subnodes). Reviewed-by:
-
Dmitry Baryshkov authored
Change the PCIe QMP PHY to use newer style of QMP PHY bindings (single resource region, no per-PHY subnodes). Signed-off-by:
-
Dmitry Baryshkov authored
Change the PCIe QMP PHY to use newer style of QMP PHY bindings (single resource region, no per-PHY subnodes). Reviewed-by:
-
Krzysztof Kozlowski authored
Qualcomm Embedded USB Debugger (EUD) second port should point to Type-C USB connector. Such connector was defined directly in root node of sc7280.dtsi which is clearly wrong. SC7280 is a chip, so physically it does not have USB Type-C port. The connector is usually accessible through some USB switch or controller. Doug Anderson said that he wasn't ever able to use EUD on Herobrine boards, probably because of invalid or missing DTS description - DTS is saying EUD is on usb_2 node, which is connected to a USB Hub, not to the Type-C port. Correct the EUD/USB connector topology by removing the top-level fake USB connector and EUD port pointing to it, and disabling the incomplete EUD device node. This fixes also dtbs_check warnings: sc7280-herobrine-crd.dtb: connector: ports:port@0: 'reg' is a required property Link: https://lore.kernel.org/all/CAD=FV=Xt26=rBf99mzkAuwwtb2f-jnKtnHaEhXnthz0a5zke4Q@mail.gmail.com/ Fixes: 9ee402cc ("arm64: dts: qcom: sc7280: Fix EUD dt node syntax") Cc: Souradeep Chowdhury <quic_schowdhu@quicinc.com> Cc: Bhupesh Sharma <bhupesh.sharma@linaro.org> Signed-off-by:
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Reviewed-by:
Douglas Anderson <dianders@chromium.org> Link: https://lore.kernel.org/r/20230820075626.22600-1-krzysztof.kozlowski@linaro.orgSigned-off-by:
-
Konrad Dybcio authored
As pointed out by Richard, I missed a non-continuity in one of the ranges. Fix it. Reported-by:
Richard Acayan <mailingradian@gmail.com> Fixes: b51ee205 ("arm64: dts: qcom: sdm670: Add PDC") Signed-off-by:
-
Luca Weiss authored
Since we have those defines available in a header, let's use them everywhere where qcom,vmid property is used. Signed-off-by:
Luca Weiss <luca.weiss@fairphone.com> Reviewed-by:
Bryan O'Donoghue <bryan.odonoghue@linaro.org> Link: https://lore.kernel.org/r/20230818-qcom-vmid-defines-v1-1-45b610c96b13@fairphone.comSigned-off-by:
-
Andrew Halaney authored
There's an irq hooked up, so let's describe it. Prior to commit 9757300d ("pinctrl: qcom: Add intr_target_width field to support increased number of interrupt targets") one would not see the IRQ fire, despite some (invasive) debugging showing that the GPIO was in fact asserted, resulting in the interface staying down. Now that the IRQ is properly routed we can describe it. Signed-off-by:
Andrew Halaney <ahalaney@redhat.com> Reviewed-by:
Bartosz Golaszewski <bartosz.golaszewski@linaro.org> Reviewed-by:
-
Andrew Halaney authored
There's an irq hooked up, so let's describe it. Prior to commit 9757300d ("pinctrl: qcom: Add intr_target_width field to support increased number of interrupt targets") one would not see the IRQ fire, despite some (invasive) debugging showing that the GPIO was in fact asserted, resulting in the interface staying down. Now that the IRQ is properly routed we can describe it. Signed-off-by:
-
Dmitry Baryshkov authored
Add displayport altmode declaration to the Type-C controller node to enable DP altmode negotiation. Signed-off-by:
-
Dmitry Baryshkov authored
Enable the onboard displayport controller, connect it to QMP PHY. Signed-off-by:
-
Dmitry Baryshkov authored
Add the nb7vpq904m, onboard USB-C redriver / retimer. Signed-off-by:
-
Dmitry Baryshkov authored
Declare the displayport controller present on the Qualcomm SM8250 SoC. Signed-off-by:
-
Bryan O'Donoghue authored
Switch on USB orientation-switching for usb_1_qmp via TCPM. Detecting the orientation switch is required to get the PHY to reset and bring-up the PHY with the CC lines set to the appropriate lane. Signed-off-by:
-
Bryan O'Donoghue authored
Switch on usb-role-switching for usb_1 via TCPM. We need to declare usb-role-switch in &usb_1 and associate with the remote-endpoint in TCPM which provides the necessary signal. Signed-off-by:
-
Bryan O'Donoghue authored
Switch on TCPM for the RB5. Here we declare as a source only not a sink since qrb5165 doesn't support powering exclusively from the type-c port. Reviewed-by:
-
Bryan O'Donoghue authored
Switch on VBUS for the Type-C port. We need to support a higher amperage than the bootloader set 2 Amps. Reviewed-by:
-
Bryan O'Donoghue authored
Type-C port management functionality lives inside of the PMIC block on pm8150b. The Type-C port management logic controls orientation detection, vbus/vconn sense and to send/receive Type-C Power Domain messages. Signed-off-by:
-
Bryan O'Donoghue authored
ports for orientation switching input and output. The individual board dts files will instantiate port@0, port@1 and/or port@2 depending on the supported feature-set. Reviewed-by:
-
Douglas Anderson authored
It was asserted that the "/delete-property/ VBAT-supply;" that we needed to do in the rt5682s dts fragment was ugly. Let's change up all the trogdor device trees to make it explicit which version of "rt5682" we have and avoid the need for the "delete-property". As a side effect, this nicely gets rid of the need for a delete-node in coachz, which doesn't use "rt5682" at all. A few notes: - This doesn't get rid of every "/delete-node/" in trogdor, just the one that was used for rt5682s. - Though we no longer have any "/delete-node/", we do still override the "model" in the "sound" node in one case (in pompom) since that uses the "2mic" sound setup. This is validated to produce the same result (other than a few properties being reordered) when taking the dtbs generated by the kernel build and then doing: for dtb in *trogdor*.dtb; do dtc -I dtb -O dts $dtb -o out/$dtb.dts; done Suggested-by:Sheng-Liang Pan <sheng-liang.pan@quanta.corp-partner.google.com> Link: https://lore.kernel.org/r/20230816112143.2.I29a5a330b6994afca81871f74bbacaf55b155937@changeidSigned-off-by:
-
Douglas Anderson authored
Several trogdor boards have moved from the older rt5862i to the newer rt5862s, at least on newer revisions of boards. Let's get rid of the dts duplication across boards and promote this to a fragment. Note: The old boards used to override the "compatible" in the "sound" node with the exact same thing that was in "sc7180-trogdor.dtsi" ("google,sc7180-trogdor"). I got rid of that. This is validated to produce the same result when taking the dtbs generated by the kernel build and then doing: for dtb in *trogdor*.dtb; do dtc -I dtb -O dts $dtb -o out/$dtb.dts; done Signed-off-by: -
Robert Marko authored
Add the required DT node for watchdog operation. Signed-off-by:
Robert Marko <robimarko@gmail.com> Reviewed-by:
-
Krzysztof Kozlowski authored
Bluetooth requires VDDIO supply and Doug Anderson suggested it is vreg_l18b_1p8. Add one to satisfy `dtbs_check`: sc7280-crd-r3.dtb: bluetooth: 'vddio-supply' is a required property Signed-off-by:
-
Konrad Dybcio authored
Configure the USB3 PHY to enable USB3 functionality Signed-off-by:
-
Konrad Dybcio authored
Add the three LEDs (blue/yellow/green) connected to TLMM GPIOs. Signed-off-by:
-
Konrad Dybcio authored
Enable the ADSP, MPSS and Wi-Fi. Tighten up the Wi-Fi regulators to make them compliant with that the chip expects. The Wi-Fi reports: qmi chip_id 0x120 chip_family 0x4007 board_id 0xff soc_id 0x40670000 Signed-off-by:
-
Konrad Dybcio authored
Commit b4fe47d1 ("arm64: dts: qcom: qrb2210-rb1: Add regulators") introduced regulator settings that were never put in place, as all of the properties ended 'microvolts' instead of 'microvolt' (which dt schema did not check for back then). Fix the microvolts-microvolt typo and adjust voltage ranges where it's necessary to fit within the volt = base + n*step formula. Reported-by:
Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org> Reported-by:
-
Konrad Dybcio authored
Newer RB1 board revisions have a debug UART on QUP0. Sadly, it looks like even when ordering one in retail, customers receive prototype boards with "Enginering Sample" written on them. Use QUP4 for UART to make all known RB1 boards boot. Fixes: e1877196 ("arm64: dts: qcom: Add initial QTI RB1 device tree") Signed-off-by:
-
- 19 Sep, 2023 9 commits
-
-
Konrad Dybcio authored
Hook up the interrupts that signal the Limits Management Hardware has started some sort of throttling action. Fixes: 7dbd121a ("arm64: dts: qcom: sc7280: Add cpufreq hw node") Signed-off-by:
-
Dmitry Baryshkov authored
Change the UFS QMP PHY to use newer style of QMP PHY bindings (single resource region, no per-PHY subnodes). Signed-off-by:
-
Douglas Anderson authored
Let's provide the proper link from the touchscreen to the panel on trogdor devices where the touchscreen support it. This allows the OS to power sequence the touchscreen more properly. For the most part, this is just expected to marginally improve power consumption while the screen is off. However, in at least one trogdor model (wormdingler) it's suspected that this will fix some behavorial corner cases when the panel power cycles (like for a modeset) without the touchscreen power cycling. NOTE: some trogdor variants use touchscreens that don't (yet) support linking the touchscreen and the panel. Those variants are left alone. Reviewed-by:
Maxime Ripard <mripard@kernel.org> Signed-off-by:
Benjamin Tissoires <bentiss@kernel.org> Acked-by:
-
Nikita Travkin authored
gt510 has two capacitive keys on the bottom. Define keycodes to enable them. Signed-off-by:
Nikita Travkin <nikita@trvn.ru> Link: https://lore.kernel.org/r/20230725-gt5-panel-v1-3-7c787e33a614@trvn.ruSigned-off-by:
-
Siddharth Manthan authored
The device has a 8 inch lsl080al03 display. Add it to the device tree. Signed-off-by:
Siddharth Manthan <siddharth.manthan@gmail.com> Co-developed-by:
-
Jasper Korten authored
The device has a 9.7 inch ltl101at01 display. Add it to the device tree. Signed-off-by:
Jasper Korten <jja2000@gmail.com> Co-developed-by:
-
Marijn Suijten authored
Enable MDSS and DSI, and configure the Samsung SOFEF01-M ams597ut01 6.0" 1080x2520 panel. Reviewed-by:
Marijn Suijten <marijn.suijten@somainline.org> Link: https://lore.kernel.org/r/20230723-sm6125-dpu-v4-17-a3f287dd6c07@somainline.orgSigned-off-by:
-
Marijn Suijten authored
Add the DT nodes that describe the MDSS hardware on SM6125, containing one MDP (display controller) together with a single DSI and DSI PHY. No DisplayPort support is added for now. Reviewed-by:
-
Marijn Suijten authored
Enable and configure the dispcc node on SM6125 for consumption by MDSS later on. Signed-off-by:
-
