- 26 May, 2023 12 commits
-
-
Devi Priya authored
Add the initial device tree support for the Reference Design Platform (RDP) 453 based on IPQ9574 family of SoCs. This patch adds support for Console UART, SPI NOR and SMPA1 regulator node. Signed-off-by:
Devi Priya <quic_devipriy@quicinc.com> Signed-off-by:
Bjorn Andersson <andersson@kernel.org> Link: https://lore.kernel.org/r/20230526153152.777-3-quic_devipriy@quicinc.com
-
Devi Priya authored
Document AL02-C8 (Reference Design Platform 453) board based on IPQ9574 family of SoCs. Signed-off-by:
Conor Dooley <conor.dooley@microchip.com> Signed-off-by:
-
Devi Priya authored
Add the initial device tree support for the Reference Design Platform (RDP) 449 based on IPQ9574 family of SoCs. This patch adds support for Console UART, SPI NOR and SMPA1 regulator node. Signed-off-by:
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Signed-off-by:
-
Devi Priya authored
Document AL02-C6 (Reference Design Platform 449) board based on IPQ9574 family of SoCs. Signed-off-by:
-
Devi Priya authored
Add the initial device tree support for the Reference Design Platform (RDP) 418 based on IPQ9574 family of SoCs. This patch adds support for Console UART, SPI NOR, eMMC and SMPA1 regulator node. Co-developed-by:
Anusha Rao <quic_anusha@quicinc.com> Signed-off-by:
-
Devi Priya authored
Document AL02-C2 (Reference Design Platform 418) board based on IPQ9574 family of SoCs. Signed-off-by:
-
Devi Priya authored
Add cpu freq nodes in the device tree to bump cpu frequency above 800MHz. Reviewed-by:
Konrad Dybcio <konrad.dybcio@linaro.org> Co-developed-by:
Praveenkumar I <quic_ipkumar@quicinc.com> Signed-off-by:
-
Devi Priya authored
Add support for SMPA1 regulator node in IPQ9574. Reviewed-by:
-
Devi Priya authored
Add RPM Glink & RPM message RAM nodes to support frequency scaling on IPQ9574. Reviewed-by:
-
Devi Priya authored
Add the APCS & A73 PLL nodes to support CPU frequency scaling. Signed-off-by:
-
Devi Priya authored
Rename the dts after Reference Design Platform(RDP) to adopt standard naming convention. Acked-by:
-
Luca Weiss authored
This file is using definitions from the spmi-vadc header, so we need to include it. Fixes: 11975b9b ("arm64: dts: qcom: Add pm7250b PMIC") Signed-off-by:
Luca Weiss <luca.weiss@fairphone.com> Signed-off-by:
-
- 25 May, 2023 28 commits
-
-
Bryan O'Donoghue authored
Add a basic booting DTS for the Sony Xperia M4 Aqua aka "tulip". Tulip is paired with: - wcn3660 - smb1360 battery charger - 720p Truly NT35521 Panel Reviewed-by:
Bryan O'Donoghue <bryan.odonoghue@linaro.org> Signed-off-by:
-
Bryan O'Donoghue authored
The apq8039-t2 is an apq8039 based board paired with a wcn3680b WiFi chipset. Co-developed-by:
Shawn Guo <shawn.guo@linaro.org> Signed-off-by:
Jun Nie <jun.nie@linaro.org> Signed-off-by:
Benjamin Li <benl@squareup.com> Signed-off-by:
James Willcox <jwillcox@squareup.com> Signed-off-by:
Leo Yan <leo.yan@linaro.org> Signed-off-by:
Joseph Gates <jgates@squareup.com> Signed-off-by:
Max Chen <mchen@squareup.com> Signed-off-by:
Zac Crosby <zac@squareup.com> Signed-off-by:
-
Stephan Gerhold authored
The msm8939-pm8916.dtsi include configures the regulator supplies of MSM8939 used together with PM8916, as recommended by Qualcomm. In rare cases where boards deviate from the recommended design they can just avoid using this include. Signed-off-by:
Stephan Gerhold <stephan@gerhold.net> Reviewed-by:
-
Bryan O'Donoghue authored
Add msm8939 a derivative SoC of msm8916. This SoC contains a number of key differences to msm8916. - big.LITTLE Octa Core - quad 1.5GHz + quad 1.0GHz - DRAM 1x800 LPDDR3 - Camera 4+4 lane CSI - Venus @ 1080p60 HEVC - DSI x 2 - Adreno A405 - WiFi wcn3660/wcn3680b 802.11ac Co-developed-by:
Vincent Knecht <vincent.knecht@mailoo.org> Signed-off-by:
-
Bryan O'Donoghue authored
Add vendor prefix for Square (https://squareup.com). Acked-by:
-
Rudraksha Gupta authored
The list of supported 'SoC's didn't include msm8960 even though qcom,msm8960-cdp exists. Signed-off-by:
Rudraksha Gupta <guptarud@gmail.com> Signed-off-by:
-
Luca Weiss authored
The phone features a notification LED connected to the pmi632. Configure the RGB led found on it. Reviewed-by:
Luca Weiss <luca@z3ntu.xyz> Signed-off-by:
-
Luca Weiss authored
The PMI632, commonly found on SoCs with SDM632 has various standard functions like ADC, GPIOs, LPG and more. Reviewed-by:
-
Dylan Van Assche authored
The SHIFT6mq (axolotl) is an SDM845-based smartphone with 2 flash LEDs. One LED is white, the other one is yellow. Define both LEDs in the DTS so they can be used as flash or torch and enable the flash LED controller to control them in PMI8998. Signed-off-by:
Dylan Van Assche <me@dylanvanassche.be> Reviewed-by:
Caleb Connolly <caleb.connolly@linaro.org> Signed-off-by:
-
Dylan Van Assche authored
Qualcomm PMIC PMI8998 has a 3 channel flash LED driver which is used by many phones for 1 or 2 flash LEDs. Each LED can be used in flash mode or torch mode. Add the flash LED controller node to PMI8998 DTS. Signed-off-by:
-
Bhupesh Sharma authored
Add CPU idle-state nodes and power-domains in Qualcomm sm6115 SoC dtsi. Signed-off-by:
Bhupesh Sharma <bhupesh.sharma@linaro.org> Signed-off-by:
-
Stephan Gerhold authored
Some of the regulators must be always-on to ensure correct operation of the system, e.g. PM8916 L2 for the LPDDR RAM, L5 for most digital I/O and L7 for the CPU PLL (strictly speaking the CPU PLL might only need an active-only vote but this is not supported for regulators in mainline currently). The RPM firmware seems to enforce that internally, these supplies stay on even if we vote for them to power off (and there is no other processor running). This means it's pointless to keep sending enable/disable requests because they will just be ignored. Also, drivers are much more likely to get a wrong impression of the regulator status, because regulator_is_enabled() will return false when there are no users, even though the regulator is always on. Describe this properly by marking the regulators as always-on. Signed-off-by:
-
Stephan Gerhold authored
Right now each MSM8916 device has a huge block of regulator constraints with allowed voltages for each regulator. For lack of better documentation these voltages are often copied as-is from the vendor device tree, without much extra thought. Unfortunately, the voltages in the vendor device trees are often misleading or even wrong, e.g. because: - There is a large voltage range allowed and the actual voltage is only set somewhere hidden in some messy vendor driver. This is often the case for pm8916_{l14,l15,l16} because they have a broad range of 1.8-3.3V by default. - The voltage is actually wrong but thanks to the voltage constraints in the RPM firmware it still ends up applying the correct voltage. To have proper regulator constraints it is important to review them in context of the usage. The current setup in the MSM8916 device trees makes this quite hard because each device duplicates the standard voltages for components of the SoC and mixes those with minor device-specific additions and dummy voltages for completely unused regulators. The actual usage of the regulators for the SoC components is in msm8916-pm8916.dtsi, so it can and should also define the related voltage constraints. These are not board-specific but defined in the APQ8016E/PM8916 Device Specification. The board DT can then focus on describing the actual board-specific regulators, which makes it much easier to review and spot potential mistakes there. Note that this commit does not make any functional change. All used regulators still have the same regulator constraints as before. Unused regulators do not have regulator constraints anymore because most of these were too broad or even entirely wrong. They should be added back with proper voltage constraints when there is an actual usage. Signed-off-by: -
Stephan Gerhold authored
Goal of the msm8916-pm8916.dtsi is to reduce the boilerplate necessary to create a device tree for a typical board with the MSM8916 SoC combined with the PM8916 PMIC. > 99% of all MSM8916 boards use the same standard setup where many of the PM8916 regulators have a fixed purpose and only some are left up for board-specific use. While MSM8916 (and perhaps MSM8939 soon) is currently the only platform with such an include, it has definitely proven useful. With more than 30 boards using it (not all of them upstream yet) it simplifies the review a lot and reduces the chance of configuring the standard components incorrectly. In preparation of extending its scope slightly, add a comment at the top that clearly explains what the .dtsi represents and when it should (or should not) be used. Signed-off-by:
-
Stephan Gerhold authored
Some of the power supplies for the analog audio codec in PM8916 are wired externally. While most boards use the regulators currently specified in pm8916.dtsi, in theory it could be connected differently. We already have msm8916-pm8916.dtsi that models that standard setup used by most devices so move the -supply properties there and keep the base pm8916.dtsi independent. Currently all MSM8916 boards in mainline make use of msm8916-pm8916.dtsi, so it is not necessary to adjust any other boards. Signed-off-by:
-
Stephan Gerhold authored
Not every device has something connected to the digital audio codec in MSM8916 and/or the analog audio codec in PM8916. Disable those by default so the hardware is only powered up when necessary. Signed-off-by:
-
Stephan Gerhold authored
The regulator constraints for most MSM8916 devices (except DB410c) were originally taken from Qualcomm's msm-3.10 vendor device tree (for lack of better documentation). Unfortunately it turns out that Qualcomm's voltages are slightly off as well and do not match the voltage constraints applied by the RPM firmware. This means that we sometimes request a specific voltage but the RPM firmware actually applies a much lower or higher voltage. This is particularly critical for pm8916_l11 which is used as SD card VMMC regulator: The SD card can choose a voltage from the current range of 1.8 - 2.95V. If it chooses to run at 1.8V we pretend that this is fine but the RPM firmware will still silently end up configuring 2.95V. This can be easily reproduced with a multimeter or by checking the SPMI hardware registers of the regulator. Fix this by making the voltages match the actual "specified range" in the PM8916 Device Specification which is enforced by the RPM firmware. Signed-off-by:
-
Stephan Gerhold authored
The 96Boards specification expects a 1.8V power rail on the low-speed expansion connector that is able to provide at least 0.18W / 100 mA. According to the DB410c hardware user manual this is done by connecting both L15 and L16 in parallel with up to 55mA each (for 110 mA total) [1]. Unfortunately the current regulator setup in the DB410c device tree does not implement the specification correctly and only provides 5 mA: - Only L15 is marked always-on, so L16 is never enabled. - Without specifying a load the regulator is put into LPM where it can only provide 5 mA. Fix this by: - Adding proper voltage constraints for L16. - Making L16 always-on. - Adding regulator-system-load for both L15 and L16. 100 mA should be available in total, so specify 50 mA for each. (The regulator hardware can only be in normal (55 mA) or low-power mode (5 mA) so this will actually result in the expected 110 mA total...) [1]: https://www.96boards.org/documentation/consumer/dragonboard/dragonboard410c/hardware-docs/hardware-user-manual.md.html#power-supplies Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org> Fixes: 828dd5d6 ("arm64: dts: apq8016-sbc: make 1.8v available on LS expansion") Signed-off-by: -
Stephan Gerhold authored
For some reason DB410c has completely bogus regulator constraints that actually just correspond to the programmable voltages which are already provided by the regulator driver. Some of them are not just outside the recommended operating conditions of the APQ8016E SoC but even exceed the absolute maximum ratings, potentially risking permanent device damage. In practice it's not quite as dangerous thanks to the RPM firmware: It turns out that it has its own voltage constraints and silently clamps all regulator requests. For example, requesting 3.3V for L5 (allowed by the current regulator constraints!) still results in 1.8V being programmed in the actual regulator hardware. Experimentation with various voltages shows that the internal RPM voltage constraints roughly correspond to the safe "specified range" in the PM8916 Device Specification (rather than the "programmable range" used inside apq8016-sbc.dtsi right now). Combine those together with some fixed voltages used in the old msm-3.10 device tree from Qualcomm to give DB410c some actually valid voltage constraints. Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org> Fixes: 4c7d53d1 ("arm64: dts: apq8016-sbc: add regulators support") Signed-off-by:
-
Jianhua Lu authored
Remove a redundant empty line introduced by commit 51c4c2bd ("arm64: dts: qcom: sm8250-xiaomi-elish-boe: Add mdss and dsi panel") Signed-off-by:
Jianhua Lu <lujianhua000@gmail.com> Signed-off-by:
-
Kathiravan T authored
Add QUP(SPI / I2C) peripheral, PRNG, WDOG and the remaining UART nodes. While at it, enable the SPI NOR in RDP433 board. Signed-off-by:
Kathiravan T <quic_kathirav@quicinc.com> Signed-off-by:
-
Krzysztof Kozlowski authored
Enable Display Subsystem with Visionox VTDR6130 Panel (same as on MTP8550). Signed-off-by:
Dmitry Baryshkov <dmitry.baryshkov@linaro.org> Reviewed-by:
-
Krzysztof Kozlowski authored
MDP in sm8550.dtsi is not disabled (although its parent MDSS is), so board DTS does not have to enable it. Suggested-by:
-
Krzysztof Kozlowski authored
Enable the Display Clock Controller by default in SoC DTSI so unused clocks can be turned off. It does not require any external resources, so as core SoC component should be always available to boards. Suggested-by:
-
Krzysztof Kozlowski authored
Enable PM8550 PMIC flash LED controller and add two flash LEDs using four current outputs. Signed-off-by:
-
Krzysztof Kozlowski authored
Add node for PM8550 PMIC flash LED controller. Signed-off-by:
-
Luca Weiss authored
Somehow wifi was placed further up in the file than where it should be. Move it down so the nodes are sorted by reg again. Signed-off-by:
-
Konrad Dybcio authored
We need more granularity for things like the GPU. Add the missing levels. This unfortunately requires some re-indexing, resulting in an ugly diff. Signed-off-by:
Neil Armstrong <neil.armstrong@linaro.org> Signed-off-by:
-
