- 26 May, 2023 26 commits
-
-
Krzysztof Kozlowski authored
The spi-max-frequency property belongs to SPI devices, not SPI controller: ipq6018-cp01-c1.dtb: spi@78b5000: Unevaluated properties are not allowed ('spi-max-frequency' was unexpected) Signed-off-by:Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Reviewed-by:
Konrad Dybcio <konrad.dybcio@linaro.org> Signed-off-by:
Bjorn Andersson <andersson@kernel.org> Link: https://lore.kernel.org/r/20230416123730.300863-1-krzysztof.kozlowski@linaro.org
-
Vignesh Viswanathan authored
In IPQ SoCs, bootloader will collect the system RAM contents upon crash for the post morterm analysis. If we don't reserve the memory region used by bootloader, obviously linux will consume it and upon next boot on crash, bootloader will be loaded in the same region, which will lead to loose some of the data, sometimes we may miss out critical information. So lets reserve the region used by the bootloader. Similarly SBL copies some data into the reserved region and it will be used in the crash scenario. So reserve 1MB for SBL as well. While at it, drop the size padding in the reserved memory region, wherever applicable. Signed-off-by:
Vignesh Viswanathan <quic_viswanat@quicinc.com> Signed-off-by:
-
Vignesh Viswanathan authored
Like any other Qualcomm SoCs, IPQ8074 and IPQ6018 also supports the download mode to collect the RAM dumps if system crashes, to perform the post mortem analysis. Add support for the same. Signed-off-by:
-
Neil Armstrong authored
Add crypto engine (CE) and CE BAM related nodes and definitions for the SM8450 SoC. Tested-by:
Anders Roxell <anders.roxell@linaro.org> Tested-by:
Linux Kernel Functional Testing <lkft@linaro.org> Signed-off-by:
Neil Armstrong <neil.armstrong@linaro.org> [Bhupesh: Corrected the compatible list] Signed-off-by:
Bhupesh Sharma <bhupesh.sharma@linaro.org> Signed-off-by:
-
Bhupesh Sharma authored
Add crypto engine (CE) and CE BAM related nodes and definitions to 'sm8350.dtsi'. Co-developed-by and Signed-off-by: Robert Foss <rfoss@kernel.org> [Bhupesh: Switch to '#interconnect-cells = <2>', available since commit 4f287e31] Tested-by:
-
Bhupesh Sharma authored
Add crypto engine (CE) and CE BAM related nodes and definitions to 'sm8250.dtsi'. Co-developed-by and Signed-off-by: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org> Tested-by:
-
Bhupesh Sharma authored
Add crypto engine (CE) and CE BAM related nodes and definitions to 'sm8150.dtsi'. Tested-by:
-
Bhupesh Sharma authored
Add crypto engine (CE) and CE BAM related nodes and definitions to 'sm6115.dtsi'. Reviewed-by:
-
Bhupesh Sharma authored
As per documentation, Qualcomm SDM845 SoC supports SLIMBAM DMA engine v1.7.4, so use the correct compatible strings. Reviewed-by:
-
Bhupesh Sharma authored
As per documentation, Qualcomm SM8550 SoC supports BAM DMA engine v1.7.4, so use the correct compatible strings. Reviewed-by:
-
Kathiravan T authored
IPQ9574 has efuse region to determine the various HW quirks. Lets add the initial support and the individual fuses will be added as they are required. Reviewed-by:
Kathiravan T <quic_kathirav@quicinc.com> Signed-off-by:
-
Kathiravan T authored
IPQ6018 has efuse region to determine the various HW quirks. Lets add the initial support and the individual fuses will be added as they are required. Signed-off-by:
Dmitry Baryshkov <dmitry.baryshkov@linaro.org> Reviewed-by:
-
Kathiravan T authored
IPQ5332 has efuse region to determine the various HW quirks. Lets add the initial support and the individual fuses will be added as they are required. Reviewed-by:
-
Kathiravan T authored
Add the QFPROM compatible for IPQ5332, IPQ6018 and IPQ9574 Signed-off-by:
-
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:
-
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:
-
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:
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 14 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:
-
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:
-
