- 22 Mar, 2023 18 commits
-
-
Krzysztof Kozlowski authored
Fix typo in USB DWC3 node maximum speed property. Fixes: a41b6175 ("arm64: dts: qcom: sm8250: Add device tree for Xiaomi Mi Pad 5 Pro") 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/20230304130315.51595-1-krzysztof.kozlowski@linaro.org
-
Bartosz Golaszewski authored
Enable the high-speed UART port connected to the Bluetooth controller on the sa8775p-adp development board. Signed-off-by:
Bartosz Golaszewski <bartosz.golaszewski@linaro.org> Reviewed-by:
-
Bartosz Golaszewski authored
Enable the high-speed UART port connected to the GNSS controller on the sa8775p-adp development board. Signed-off-by:
-
Bartosz Golaszewski authored
Add two UART nodes that are known to be used by existing development boards with this SoC. Signed-off-by:
-
Bartosz Golaszewski authored
Enable the SPI interface exposed on the sa8775p-ride development board. Signed-off-by:
-
Bartosz Golaszewski authored
Add the SPI controller node for the interface exposed on the sa8775p-ride development board. Signed-off-by:
-
Bartosz Golaszewski authored
This enables the I2C interface on the sa8775p-ride development board. Signed-off-by:
-
Bartosz Golaszewski authored
Add a disabled node for the I2C interface that's exposed on the sa8775p-ride development board. Signed-off-by:
-
Bartosz Golaszewski authored
Enable the second instance of the QUPv3 engine on the sa8775p-ride board. Signed-off-by:
-
Bartosz Golaszewski authored
Add the second instance of the QUPv3 engine to the sa8775p.dtsi. Signed-off-by:
-
Danila Tikhonov authored
Add a node describing the flash block found on pm8150l. Signed-off-by:
Danila Tikhonov <danila@jiaxyga.com> Signed-off-by:
-
Bhupesh Sharma authored
As per documentation, Qualcomm SDM845 SoC supports BAM DMA engine v1.7.4, so use the correct compatible strings. Signed-off-by:
Bhupesh Sharma <bhupesh.sharma@linaro.org> Reviewed-by:
-
Neil Armstrong authored
Add the pmic glink node linked with the DWC3 USB controller switched to OTG mode and tagged with usb-role-switch. Reviewed-by:
Neil Armstrong <neil.armstrong@linaro.org> Signed-off-by:
-
Neil Armstrong authored
Add the pmic glink node linked with the DWC3 USB controller switched to OTG mode and tagged with usb-role-switch. Reviewed-by:
-
Neil Armstrong authored
Add the pmic glink node linked with the DWC3 USB controller switched to OTG mode and tagged with usb-role-switch. Signed-off-by:
Dmitry Baryshkov <dmitry.baryshkov@linaro.org> Reviewed-by:
-
Neil Armstrong authored
Add ports subnodes in dwc3 node to avoid repeating the same description in each board DT. Reviewed-by:
-
Neil Armstrong authored
Add ports subnodes in dwc3 node to avoid repeating the same description in each board DT. Reviewed-by:
-
Neil Armstrong authored
Add ports subnodes in dwc3 node to avoid repeating the same description in each board DT. Reviewed-by:
-
- 20 Mar, 2023 3 commits
-
-
Bhupesh Sharma authored
Normally the 'pinctrl' properties of a SDHC controller and the chip detect pin settings are dependent on the type of the slots (for e.g uSD card slot), regulators and GPIO(s) available on the board(s). So, move the same from the sm6115 dtsi file to the respective board file(s). Reviewed-by:
Marijn Suijten <marijn.suijten@somainline.org> Signed-off-by:
-
Bhupesh Sharma authored
Normally the 'maximum-speed' and 'dr_mode' properties of a USB controller + port is dependent on the type of the ports, regulators and mode change interrupt routing available on the board(s). So, move the same from the sm6115 dtsi file to respective board file(s). Reviewed-by:
-
Bhupesh Sharma authored
There is only one USB controller present on SM6115 / SM4250 Qualcomm SoC, so drop the numbering used with USB node's label names in the dtsi and the related sm4250-oneplus-billie2.dts. Reviewed-by:
-
- 16 Mar, 2023 19 commits
-
-
Johan Hovold authored
Fix the external display controller nodes which erroneously described the controllers as belonging to CX rather than MMCX. Fixes: 19d3bb90 ("arm64: dts: qcom: sc8280xp: Add USB-C-related DP blocks") Signed-off-by:
Johan Hovold <johan+linaro@kernel.org> Signed-off-by:
-
Stephan Gerhold authored
The reg address of the tsens_mode nvmem cell is correct but the unit address does not match (0xec vs 0xef). Fix it. No functional change. Fixes: 24aafd04 ("arm64: dts: qcom: msm8916: specify per-sensor calibration cells") Signed-off-by:
Stephan Gerhold <stephan.gerhold@kernkonzept.com> Reviewed-by:
-
Neil Armstrong authored
Miscellaneous DT fixes to remove spurious blank line and enhance readability. Fixes: ffc50b2d ("arm64: dts: qcom: Add base SM8550 dtsi") Fixes: d7da51db ("arm64: dts: qcom: sm8550: add display hardware devices") Signed-off-by:
-
Neil Armstrong authored
The node is incomplete and doesn't need a subnode, add the missing properties and move everything to the root of qup-spi0-cs-state node. Fixes: ffc50b2d ("arm64: dts: qcom: Add base SM8550 dtsi") Signed-off-by:
-
Krzysztof Kozlowski authored
gpio-keys,wakeup is a deprecated property: sm8250-xiaomi-elish.dtb: gpio-keys: key-vol-up: Unevaluated properties are not allowed ('gpio-key,wakeup' was unexpected) Signed-off-by: -
Krzysztof Kozlowski authored
gpio-keys,wakeup is a deprecated property: sm8250-sony-xperia-edo-pdx206.dtb: gpio-keys: key-vol-down: Unevaluated properties are not allowed ('gpio-key,wakeup' was unexpected) Signed-off-by: -
Krzysztof Kozlowski authored
gpio-keys,wakeup is a deprecated property: sm6115p-lenovo-j606f.dtb: gpio-keys: key-volume-up: Unevaluated properties are not allowed ('gpio-key,wakeup' was unexpected) Signed-off-by: -
Krzysztof Kozlowski authored
gpio-keys,wakeup is a deprecated property: sdm630-sony-xperia-nile-voyager.dtb: gpio-keys: key-vol-down: Unevaluated properties are not allowed ('gpio-key,wakeup' was unexpected) Signed-off-by: -
Krzysztof Kozlowski authored
gpio-keys,wakeup is a deprecated property: sc7280-idp.dtb: gpio-keys: key-volume-up: Unevaluated properties are not allowed ('gpio-key,wakeup' was unexpected) Signed-off-by: -
Krzysztof Kozlowski authored
gpio-keys,wakeup is a deprecated property: msm8998-sony-xperia-yoshino-lilac.dtb: gpio-keys: button-vol-down: Unevaluated properties are not allowed ('gpio-key,wakeup' was unexpected) Signed-off-by: -
Krzysztof Kozlowski authored
gpio-keys,wakeup is a deprecated property: msm8998-fxtec-pro1.dtb: gpio-hall-sensors: event-hall-sensor1: Unevaluated properties are not allowed ('gpio-key,wakeup' was unexpected) Signed-off-by: -
Krzysztof Kozlowski authored
gpio-keys,wakeup is a deprecated property: sm8150-sony-xperia-kumano-bahamut.dtb: gpio-keys: key-camera-focus: Unevaluated properties are not allowed ('gpio-key,wakeup' was unexpected) Signed-off-by: -
Douglas Anderson authored
The mrbland board was never actually produced and there has been no activity around the board for quite some time. It seems highly unlikely to magically get revived. There should be nobody in need of these device trees, so let's delete them. If somehow the project resurrects itself then we can re-add support, perhaps just for -rev1+. Signed-off-by:
Douglas Anderson <dianders@chromium.org> Reviewed-by:
-
Douglas Anderson authored
lazor-rev0 was a pile of parts. While I kept the pile of parts for lazor running on my desk for longer than I usually do, those days are still long past. Let's finally delete support for lazor-rev0. Signed-off-by:
-
Douglas Anderson authored
The earliest kingoftown that I could find in my pile of boards was -rev2 and even that revision looks pretty rough (plastics on the case are very unfinished). Though I don't actually have details about how many -rev0 devices were produced, I can't imagine anyone still using one. Let's delete support. Signed-off-by:
-
Douglas Anderson authored
The earliest wormdingler I could find in my pile of hardware is -rev1. I believe that -rev0 boards were just distributed as a pile of components with no case. At this point I can't imagine anyone needing to make wormdingler-rev0 work, so let's delete support for it. Signed-off-by:
-
Adam Skladowski authored
In order for consumers of RPMCC XO clock to probe successfully their parent needs to be feed with reference clock to obtain proper rate, add fixed xo-board clock and supply it to rpmcc to make consumers happy. Frequency setting is left per board basis just like on other recent trees. Fixes: 0484d3ce ("arm64: dts: qcom: Add DTS for MSM8976 and MSM8956 SoCs") Fixes: ff7f6d34 ("arm64: dts: qcom: Add support for SONY Xperia X/X Compact") Signed-off-by:
Adam Skladowski <a39.skl@gmail.com> Reviewed-by:
-
Manivannan Sadhasivam authored
For 1MiB of the I/O region, the I/O ports of the legacy PCI devices are located in the range of 0x0 to 0x100000. Hence, fix the bogus PCI addresses (0x60200000, 0x40200000) specified in the ranges property for I/O region. While at it, let's use the missing 0x prefix for the addresses. Fixes: 6daee406 ("arm64: dts: qcom: sm8350: add PCIe devices") Reported-by:
Arnd Bergmann <arnd@arndb.de> Link: https://lore.kernel.org/linux-arm-msm/7c5dfa87-41df-4ba7-b0e4-72c8386402a8@app.fastmail.com/Signed-off-by:
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org> Reviewed-by:
-
Manivannan Sadhasivam authored
For 1MiB of the I/O region, the I/O ports of the legacy PCI devices are located in the range of 0x0 to 0x100000. Hence, fix the bogus PCI addresses (0x60200000, 0x40200000) specified in the ranges property for I/O region. While at it, let's use the missing 0x prefix for the addresses. Fixes: bc6588bc ("arm64: dts: qcom: sm8450: add PCIe1 root device") Fixes: 7b09b1b4 ("arm64: dts: qcom: sm8450: add PCIe0 RC device") Reported-by:
-
