- 24 Oct, 2021 3 commits
-
-
Bhupesh Sharma authored
Enable two of the remoteprocs found on SA8155p platform - 'audio and compute'. Also specify firmware path for them. Cc: Bjorn Andersson <bjorn.andersson@linaro.org> Signed-off-by:
Bhupesh Sharma <bhupesh.sharma@linaro.org> Signed-off-by:
Bjorn Andersson <bjorn.andersson@linaro.org> Link: https://lore.kernel.org/r/20210928140929.2549459-3-bhupesh.sharma@linaro.org
-
Bhupesh Sharma authored
Add fastrpc nodes for sDSP, cDSP, and aDSP. Cc: Bjorn Andersson <bjorn.andersson@linaro.org> Signed-off-by:
-
Ola Jeppsson authored
Add fastrpc nodes for sDSP, cDSP, and aDSP. Signed-off-by:
Ola Jeppsson <ola@snap.com> Acked-by:
Heinrich Fink <hfink@snap.com> Acked-by:
Olivier Schonken <oschonken@snapchat.com> Signed-off-by:
-
- 20 Oct, 2021 1 commit
-
-
Caleb Connolly authored
Like the c630, the OnePlus 6 is also capable of using both antenna channels for 2.4 and 5ghz wifi, however unlike the c630 only the first channel is used for bluetooth. Signed-off-by:
Caleb Connolly <caleb@connolly.tech> Signed-off-by:
-
- 18 Oct, 2021 5 commits
-
-
Dmitry Baryshkov authored
Now that the pmic-mpp is a proper hierarchical IRQ chip, add interrupt controller properties ('interrupt-controller' and '#interrupt-cells'). The interrupts property is no longer needed so remove it. Signed-off-by:Dmitry Baryshkov <dmitry.baryshkov@linaro.org> Signed-off-by:
-
Dmitry Baryshkov authored
Now that the pmic-mpp is a proper hierarchical IRQ chip, add interrupt controller properties ('interrupt-controller' and '#interrupt-cells'). The interrupts property is no longer needed so remove it. Signed-off-by: -
Dmitry Baryshkov authored
The majority of device tree nodes for mpps use xxxx-state as pinctrl nodes. Change names of mpps pinctrl nodes for the apq8016-sbc board to follow that pattern. Signed-off-by:
-
Dmitry Baryshkov authored
Add missing "qcom,spmi-mpp" to the compatible list as required by the node description. Also add gpio-ranges property to mpps device tree node, adding the mapping between pinctrl and GPIO pins. Signed-off-by:
-
Dmitry Baryshkov authored
Add missing "qcom,spmi-mpp" to the compatible list as required by the node description. Also add gpio-ranges property to mpps device tree node, adding the mapping between pinctrl and GPIO pins. Signed-off-by:
-
- 16 Oct, 2021 5 commits
-
-
Maulik Shah authored
Add device node for Sleep stats driver which provides various low power mode stats on msm8996, msm8998, qcs404, sdm630 and sm6125. Cc: devicetree@vger.kernel.org Signed-off-by:
Maulik Shah <mkshah@codeaurora.org> Tested-by:
Shawn Guo <shawn.guo@linaro.org> Signed-off-by:
-
Maulik Shah authored
Add device node for Sleep stats driver which provides various low power mode stats on sc7180, sc7280, sm8150, sm8250 and sm8350. Also update the reg size of aoss_qmp device to 0x400. Cc: devicetree@vger.kernel.org Signed-off-by:
-
Philip Chen authored
Add a dts fragment file to support the sc7180 boards with the second source edp bridge, Parade ps8640. Signed-off-by:
Philip Chen <philipchen@chromium.org> Reviewed-by:
Douglas Anderson <dianders@chromium.org> Reviewed-by:
Stephen Boyd <swboyd@chromium.org> Signed-off-by:
-
Philip Chen authored
Factor out ti-sn65dsi86 edp bridge as a separate dts fragment. This helps us introduce the second source edp bridge later. Signed-off-by:
-
Arnaud Ferraris authored
A new 'chassis-type' root node property has recently been approved for the device-tree specification, in order to provide a simple way for userspace to detect the device form factor and adjust their behavior accordingly. This patch fills in this property for end-user devices (such as laptops, smartphones and tablets) based on Qualcomm ARM64 processors. Signed-off-by:
Arnaud Ferraris <arnaud.ferraris@collabora.com> Reviewed-by: Stephan Gerhold <stephan@gerhold.net> # msm8916 Signed-off-by:
-
- 15 Oct, 2021 5 commits
-
-
Dmitry Baryshkov authored
Switch dispcc and videocc into using MMCX domain directly. Drop the now unused mmcx regulator. Signed-off-by:
Ulf Hansson <ulf.hansson@linaro.org> Signed-off-by:
-
Rajesh Patil authored
Add "qcom,sc7180-qspi" compatible in qspi node Signed-off-by:
Rajesh Patil <rajpat@codeaurora.org> Reviewed-by:
-
Bjorn Andersson authored
Now that the SMEM binding and driver allows the SMEM node to be described in the reserved-memory region directly, move the compatible and hwlock properties to the reserved-memory node and drop the standadlone node. Signed-off-by:
Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org> Link: https://lore.kernel.org/r/20210930182111.57353-5-bjorn.andersson@linaro.org
-
Stephan Gerhold authored
Using underscores in device tree nodes is not very common. Additionally, the _region suffix in "smem_region@..." is not really useful since it's obvious that it describes a reserved memory region. Signed-off-by:
Stephan Gerhold <stephan@gerhold.net> Signed-off-by:
-
Stephan Gerhold authored
Commit 0f6b380d ("arm64: dts: qcom: apq8016-sbc: Update modem and WiFi firmware path") added "firmware-name"s to the APQ8016 SBC (DB410c) device tree to separate the (test key)-signed firmware from other devices. However, the added names are a bit confusing. The "modem" firmware used by DB410c is actually a simplified version for APQ8016 that lacks most of the modem functionality (phone calls, SMS etc) that is available on MSM8916. Placing it in "qcom/msm8916/modem.mbn" suggests that it supports all functionality for MSM and not just the reduced functionality for APQ. Request the firmware from "qcom/apq8016/modem.mbn" instead to clarify this. Do the same for "wcnss.mbn" for consistency (although the WCNSS firmware works just fine on MSM8916). Finally, add a "_sbc" suffix to the WCNSS_qcom_wlan_nv.bin firmware file. It seems like the nv.bin firmware is somewhat board specific and can therefore vary a bit from device to device. This makes it more clear which board it is intended to be used for. Signed-off-by:
-
- 28 Sep, 2021 5 commits
-
-
Shawn Guo authored
29.5V (29p5) is obviously wrong for regulator l4 and l5. Correct them to be 2.95V (2p95). No functional change. Signed-off-by:
-
Marijn Suijten authored
Some multiline properties (spread out over multiple lines to keep length in check) were not indented properly, leading to misalignment with the items above. The DT file is still small enough to address this early in the process. Signed-off-by:
Marijn Suijten <marijn.suijten@somainline.org> Reviewed-by:
Martin Botka <martin.botka@somainline.org> Signed-off-by:
-
Stephan Gerhold authored
At the moment, longcheer-l8150 is using a dummy extcon-usb-gpio device that permanently enables USB gadget mode. This workaround allows USB to work but is actually wrong and confusing. The "vbus-gpio" used there refers to an unused (floating) GPIO that is pulled up to make extcon-usb-gpio report USB gadget mode permanently. Replace this with the new &pm8916_usbin extcon device that actually reports if an USB cable is attached or not. This allows the USB PHY to be turned off when there is no USB cable attached and is much cleaner overall. Fixes: 16e8e807 ("arm64: dts: qcom: Add device tree for Longcheer L8150") Signed-off-by:
-
Stephan Gerhold authored
At the moment, USB gadget mode on MSM8916 works only with an extcon device that reports the correct USB mode. This might be because the USB PHY needs to be configured appropriately. Unfortunately there is currently no simple approach to get such an extcon device during early bring-up. The extcon device for USB VBUS (i.e. gadget/peripheral mode) is typically provided by the charging driver which is almost always very complex to port. On pretty much all devices with PM8916, the USB VBUS is also connected to the PM8916 "USB_IN" pad, no matter if they use the linear charger integrated into PM8916 or not. The state of this pad can be checked with the "USBIN_VALID" interrupt of PM8916. The "qcom,pm8941-misc" binding exists to expose an "usb_vbus" and/or "usb_id" interrupt from the PMIC as an extcon device. Add a &pm8916_usbin node to pm8916.dtsi which can be used as simple extcon device for devices that are currently lacking a proper charger driver. Signed-off-by:
-
Stephan Gerhold authored
While removing the size from the "reg" properties in pm8916.dtsi, commit bd6429e8 ("ARM64: dts: qcom: Remove size elements from pmic reg properties") mistakenly also removed the second register address for the rtc@6000 device. That one did not represent the size of the register region but actually the address of the second "alarm" register region of the rtc@6000 device. Now there are "reg-names" for two "reg" elements, but there is actually only one "reg" listed. Since the DT schema for "qcom,pm8941-rtc" only expects one "reg" element anyway, just drop the "reg-names" entirely to fix this. Fixes: bd6429e8 ("ARM64: dts: qcom: Remove size elements from pmic reg properties") Signed-off-by:
-
- 27 Sep, 2021 16 commits
-
-
Sibi Sankar authored
Update MSS node to support MSA based modem boot on SC7280 SoCs. Signed-off-by:
Sibi Sankar <sibis@codeaurora.org> Reviewed-by:
-
Sibi Sankar authored
This patch adds Q6V5 MSS PAS remoteproc node for SC7280 SoCs. Signed-off-by:
Matthias Kaehlcke <mka@chromium.org> Reviewed-by:
-
Sibi Sankar authored
Add miscellaneous nodes to boot the modem and support post-mortem debug on SC7280 SoCs. Signed-off-by:
-
Sibi Sankar authored
Add, delete and update platform specific reserved memory nodes. Signed-off-by:
-
Sibi Sankar authored
Add missing reserved regions as described in v1 of SC7280 memory map. Signed-off-by:
-
AngeloGioacchino Del Regno authored
This device has a physical matrix keyboard, connected to a GPIO expander, for which there's still no support yet. Though, some of the keys are connected to the MSM8998 GPIOs and not as a matrix, so these can be added. Signed-off-by:
AngeloGioacchino Del Regno <angelogioacchino.delregno@somainline.org> Signed-off-by:
-
AngeloGioacchino Del Regno authored
This smartphone has a Goodix GT8296 touch IC, reachable at address 0x14 on blsp2 i2c-1. Signed-off-by:
-
AngeloGioacchino Del Regno authored
Add configuration for the physical keyboard LEDs, including the caps lock indicator and keyboard backlight. Signed-off-by:
-
AngeloGioacchino Del Regno authored
Add device tree support for the F(x)tec Pro 1 (QX1000) smartphone; this is a minimal configuration to boot to serial console. Signed-off-by:
kernel test robot <lkp@intel.com> Signed-off-by:
-
Stephan Gerhold authored
At the moment, playing audio on Secondary MI2S will just end up getting stuck, without actually playing any audio. This happens because the wrong bit clock is configured when playing audio on Secondary MI2S. The PRI_I2S_CLK (better name: SPKR_I2S_CLK) is used by the SPKR audio mux block that provides both Primary and Secondary MI2S. The SEC_I2S_CLK (better name: MIC_I2S_CLK) is used by the MIC audio mux block that provides Tertiary MI2S. Quaternary MI2S is also part of the MIC audio mux but has its own clock (AUX_I2S_CLK). This means that (quite confusingly) the SEC_I2S_CLK is not actually used for Secondary MI2S as the name would suggest. Secondary MI2S needs to have the same clock as Primary MI2S configured. Fix the clock list for the lpass node in the device tree and add a comment to clarify this confusing naming. With these changes, audio can be played correctly on Secondary MI2S. Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org> Fixes: 3761a361 ("arm64: dts: qcom: add lpass node") Tested-by:
Vincent Knecht <vincent.knecht@mailoo.org> Signed-off-by:
-
Stephan Gerhold authored
So far there were no interrupts set up for the BMC150 accelerometer + magnetometer combo because they were broken for some reason. It turns out Longcheer L8150 actually has a BMC156 which is very similar to BMC150, but only has an INT2 pin for the accelerometer part. This requires some minor changes in the bmc150-accel driver which is now supported by using the more correct bosch,bmc156_accel compatible. Unfortunately it looks like even INT2 is not functional on most boards because the interrupt line is not actually connected to the BMC156. However, there are two pads next to the chip that can be shorted to make it work if needed. While at it, add the missing interrupts for the magnetometer part and extra BMG160 gyroscope, those seem to work without any problems. Also correct the magnetometer compatible to bosch,bmc156_magn for clarity (no functional difference for the magnetometer part). Tested-by:
Nikita Travkin <nikita@trvn.ru> Signed-off-by:
-
Sai Prakash Ranjan authored
Add IMEM and pil info DT nodes for SC7180 SoC which will help in the post-mortem debug. Signed-off-by:
Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org> [bjorn: Dropped dload-mode subnode, as no agreement was reached on this binding] Signed-off-by:
-
Konrad Dybcio authored
Add missing include to make it compile. Signed-off-by:
Konrad Dybcio <konrad.dybcio@somainline.org> Signed-off-by:
-
Konrad Dybcio authored
Add initial SM6350 SoC and Sony Xperia 10 III (PDX213, Lena platform) device trees. There is no sign of another Lena devices on the horizon, so a common DTSI is not created for now. 10 III features a Full HD OLED display and 5G support, among other nice things like USB3. The bootloader is VERY unpleasant, to get a bootable setup you have to run: mkbootimg --kernel arch/arm64/boot/Image.gz --ramdisk [some initrd] \ --dtb arch/arm64/boot/dts/qcom/sm6350-sony-xperia-lena-pdx213.dtb \ --cmdline "[some cmdline]" --base 0 --kernel_offset 0x8000 \ --ramdisk_offset 0x1000000 --dtb_offset 0x1f00000 --os_version 11 \ --os_patch_level "2021-08" --tags_offset 0x100 --pagesize 4096 \ --header_version 2 -o mainline.img adb reboot bootloader // You have to either pull vbmeta{"","_system"} from // /dev/block/bootdevice/by-name/ or build one as a part of AOSP build process fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img fastboot --disable-verity --disable-verification flash vbmeta_system \ vbmeta_system.img fastboot flash boot mainline.img fastboot erase dtbo // This will take approx 70s... fastboot reboot Signed-off-by: -
Konrad Dybcio authored
Add a node for the APPS SMMU to allow for managing memory access to peripherals such as the USB controller. While at it, add iommus property to the USB1 node to make sure its registers can be accessed, as they seem to be gated by default. Signed-off-by:
-
Konrad Dybcio authored
Add SDHCI1/2 nodes for eMMC and uSD card respectively. Do note that most SM6350 devices seem to come with UFS. Signed-off-by:
-
