- 28 May, 2024 22 commits
-
-
Marc Gonzalez authored
The ath10k driver waits for an "MSA_READY" indicator to complete initialization. If the indicator is not received, then the device remains unusable. cf. ath10k_qmi_driver_event_work() Several msm8998-based devices are affected by this issue. Oddly, it seems safe to NOT wait for the indicator, and proceed immediately when QMI_EVENT_SERVER_ARRIVE. Jeff Johnson wrote: The feedback I received was "it might be ok to change all ath10k qmi to skip waiting for msa_ready", and it was pointed out that ath11k (and ath12k) do not wait for it. However with so many deployed devices, "might be ok" isn't a strong argument for changing the default behavior. cf. also https://wiki.postmarketos.org/wiki/Qualcomm_Snapdragon_835_(MSM8998)#WLANSigned-off-by:
Marc Gonzalez <mgonzalez@freebox.fr> Acked-by:
Jeff Johnson <quic_jjohnson@quicinc.com> Reviewed-by:
Konrad Dybcio <konrad.dybcio@linaro.org> Link: https://lore.kernel.org/r/0914f96e-fcfd-4088-924a-fc1991bce75f@freebox.frSigned-off-by:
Bjorn Andersson <andersson@kernel.org>
-
Luca Weiss authored
Enable the vibrator on the PMI632 which is used on this phone. Signed-off-by:
Luca Weiss <luca.weiss@fairphone.com> Link: https://lore.kernel.org/r/20240418-fp3-vibra-v1-2-b636b8b3ff32@fairphone.comSigned-off-by:
-
Luca Weiss authored
Add a node for the vibrator module found inside the PMI632. Signed-off-by:
-
Rob Herring (Arm) authored
Arm heterogeneous configurations should have separate PMU nodes for each CPU uarch as the uarch specific events can be different. The "arm,armv8-pmuv3" compatible is also intended for s/w models rather than specific uarch implementations. All the kryo CPUs are missing PMU compatibles, so they can't be fixed. Signed-off-by:
"Rob Herring (Arm)" <robh@kernel.org> Link: https://lore.kernel.org/r/20240417204247.3216703-1-robh@kernel.orgSigned-off-by:
-
Luca Weiss authored
Follow the updated bindings and use a QCS404-specific compatible for the HFPLL on this SoC. Signed-off-by:
Luca Weiss <luca@z3ntu.xyz> Reviewed-by:
Dmitry Baryshkov <dmitry.baryshkov@linaro.org> Link: https://lore.kernel.org/r/20240218-hfpll-yaml-v2-3-31543e0d6261@z3ntu.xyzSigned-off-by:
-
Martijn Braam authored
Motorola Moto G 2015 is an msm8916 based smartphone. Supported features: - eMMC and SD; - Buttons; - Touchscreen; - USB; - Fuel Gauge; - Sound. Signed-off-by:
Martijn Braam <martijn@brixit.nl> Signed-off-by:
Stephan Gerhold <stephan@gerhold.net> [Nikita: Use common dtsi] Signed-off-by:
Nikita Travkin <nikita@trvn.ru> Reviewed-by:
-
Wiktor Strzębała authored
Motorola Moto E 2015 LTE is an msm8916 based smartphone. Supported features: - eMMC and SD; - Buttons; - Touchscreen; - USB; - Fuel Gauge; - Sound. Signed-off-by:
Wiktor Strzębała <wiktorek140@gmail.com> [Valérie: Sound and modem] Co-developed-by:
Valérie Roux <undev@unixgirl.xyz> Signed-off-by:
-
Ruby Iris Juric authored
Motorola Moto G4 Play is an msm8916 based smartphone. Supported features: - eMMC and SD; - Buttons; - Touchscreen; - USB; - Fuel Gauge; - Sound; - Accelerometer. msm8916 Moto devices share significant portion of the design so the common parts are separated into a common dtsi. Signed-off-by:
Ruby Iris Juric <ruby@srxl.me> Signed-off-by:
-
Raymond Hackley authored
Core Prime LTE uses ST LIS2HH12 accelerometer. Add support for it. [Stephen: Use common &st_accel definition from common dtsi] Signed-off-by:
Raymond Hackley <raymondhackley@protonmail.com> Link: https://lore.kernel.org/r/20240406111348.14358-4-raymondhackley@protonmail.comSigned-off-by:
-
Siddharth Manthan authored
Some Grand Prime use a ST LSM303C accelerometer/magnetometer combo. Add support for it. Signed-off-by:
Siddharth Manthan <siddharth.manthan@gmail.com> [Stephan: Move sensors to common dtsi (disabled by default)] Signed-off-by:
-
Joe Mason authored
Some Grand Prime use a Bosch BMC150 accelerometer/magnetometer combo. The chip provides two separate I2C devices for the accelerometer and magnetometer that are already supported by the bmc150-accel and bmc150-magn driver. Signed-off-by:
Joe Mason <buddyjojo06@outlook.com> [Stephan: Move sensors to common dtsi, disabled by default] Signed-off-by:
-
Nikita Travkin authored
Add compatible values for the msm8916 based Motorola smartphones. Signed-off-by:
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Link: https://lore.kernel.org/r/20240405-msm8916-moto-init-v1-1-502b58176d34@trvn.ruSigned-off-by:
-
Gianluca Boiano authored
This node is actually found on some msm8953 devices (xiaomi-mido) and allows irled enablement Signed-off-by:
Gianluca Boiano <morf3089@gmail.com> Reviewed-by:
-
Neil Armstrong authored
This documents Lenovo Smart Tab M10 (WiFi) (model tbx605f) which is a 10.1" tablet by Lenovo based on the SDM450 SoC. Signed-off-by:
Neil Armstrong <neil.armstrong@linaro.org> Acked-by:
-
Sumit Garg authored
Add Schneider Electric HMIBSC board DTS. The HMIBSC board is an IIoT Edge Box Core board based on the Qualcomm APQ8016E SoC. Support for Schneider Electric HMIBSC. Features: - Qualcomm Snapdragon 410C SoC - APQ8016 (4xCortex A53, Adreno 306) - 1GiB RAM - 8GiB eMMC, SD slot - WiFi and Bluetooth - 2x Host, 1x Device USB port - HDMI - Discrete TPM2 chip over SPI - USB ethernet adaptors (soldered) Co-developed-by:
Jagdish Gediya <jagdish.gediya@linaro.org> Signed-off-by:
Caleb Connolly <caleb.connolly@linaro.org> Reviewed-by:
Sumit Garg <sumit.garg@linaro.org> Link: https://lore.kernel.org/r/20240527053826.294526-4-sumit.garg@linaro.orgSigned-off-by:
-
Sumit Garg authored
Document the compatible for the Schneider Electric HMIBSC IIoT edge box core board based on the Qualcomm APQ8016E SoC. Acked-by:
-
Sumit Garg authored
Add vendor prefix for Schneider Electric (https://www.se.com/). Acked-by:
-
Dmitry Baryshkov authored
There is no need to mention and/or to touch in any way the intermediate (source) clocks. Drop them from MSM8996 UFSHCD schema, making it follow the example lead by all other platforms. Reviewed-by:
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org> Signed-off-by:
-
Dmitry Baryshkov authored
Instead of setting the frequency of the interim UFS_ICE_CORE_CLK_SRC clock, set the frequency of the leaf GCC_UFS_ICE_CORE_CLK clock directly. Reviewed-by:
-
Dmitry Baryshkov authored
Follow the example of other platforms and specify core_clk frequencies in the frequency table in addition to the core_clk_src frequencies. The driver should be setting the leaf frequency instead of some interim clock freq. Suggested-by:
Nitin Rawat <quic_nitirawa@quicinc.com> Fixes: 57fc67ef ("arm64: dts: qcom: msm8996: Add ufs related nodes") Reviewed-by:
-
Srinivas Kandagatla authored
The ADSP provides fastrpc/compute capabilities. Enable support for the fastrpc on this DSP. Signed-off-by:
Srinivas Kandagatla <srinivas.kandagatla@linaro.org> Signed-off-by:
-
Dmitry Baryshkov authored
MSM8996 provides limited glink support, so add corresponding device tree nodes. For example the following interfaces are provided on db820c: modem: 2080000.remoteproc:glink-edge.LOOPBACK_CTL_MPSS.-1.-1 2080000.remoteproc:glink-edge.glink_ssr.-1.-1 2080000.remoteproc:glink-edge.rpmsg_chrdev.0.0 adsp: 9300000.remoteproc:glink-edge.LOOPBACK_CTL_LPASS.-1.-1 9300000.remoteproc:glink-edge.glink_ssr.-1.-1 9300000.remoteproc:glink-edge.rpmsg_chrdev.0.0 Reviewed-by:
-
- 27 May, 2024 18 commits
-
-
Gabor Juhos authored
Add device tree source for the TP-Link Archer AX55 v1 [1] which is a dual-band WiFi router based on the IPQ5018 SoC. At the moment, only the UART, the GPIO LEDs and buttons are usable, but it makes it possible to boot an initramfs image on the device. The device tree can be extended in the future, once support for other periherals will be available for the platform. 1. https://www.tp-link.com/en/home-networking/wifi-router/archer-ax55/v1/Signed-off-by:
Gabor Juhos <j4g8y7@gmail.com> Link: https://lore.kernel.org/r/20240326-archer-ax55-v1-v4-2-dc5b54a4bb00@gmail.comSigned-off-by:
-
Gabor Juhos authored
Document the TP-Link Archer AX55 v1 which is a dual-band WiFi router based on the IPQ5018 SoC. Signed-off-by:
Conor Dooley <conor.dooley@microchip.com> Link: https://lore.kernel.org/r/20240326-archer-ax55-v1-v4-1-dc5b54a4bb00@gmail.comSigned-off-by:
-
Luca Weiss authored
Add the compatible for this Samsung smartphone ("phablet" as it was named in that era). Acked-by: -
Mrinmay Sarkar authored
The PCIe EP controller on SA8775P supports cache coherency, hence add the "dma-coherent" property to mark it as such. Signed-off-by:
Mrinmay Sarkar <quic_msarkar@quicinc.com> Reviewed-by:
-
Bryant Mairs authored
Add binding documentation for Samsung Galaxy Tab 4 8.0 Wi-Fi tablet which is based on Snapdragon 400 (apq8026) SoC. Acked-by:
Linus Walleij <linus.walleij@linaro.org> Acked-by:
Bryant Mairs <bryant@mai.rs> Link: https://lore.kernel.org/r/20240219214643.197116-2-bryant@mai.rsSigned-off-by:
-
Alexandru Gagniuc authored
The IPQ95xx uses an IPQ4019 compatible MDIO controller that is already supported. Add a DT node to expose it. Signed-off-by:
Alexandru Gagniuc <mr.nuke.me@gmail.com> Link: https://lore.kernel.org/r/20240507024758.2810514-2-mr.nuke.me@gmail.comSigned-off-by:
-
Adam Skladowski authored
Add node describing wireless connectivity subsystem. Signed-off-by:
Adam Skladowski <a39.skl@gmail.com> Link: https://lore.kernel.org/r/20240508163455.8757-5-a39.skl@gmail.comSigned-off-by:
-
Adam Skladowski authored
Add Adreno GPU node. Signed-off-by:
-
Adam Skladowski authored
Add MDSS nodes to support displays on MSM8976 SoC. Signed-off-by:
-
Adam Skladowski authored
Add the nodes describing the apps and gpu iommu and its context banks that are found on msm8976 SoCs. Signed-off-by:
-
Luca Weiss authored
Add the different services found on APR on some devices with SC7280 SoC. Additionally add an empty sound node in the root node as is seen on other SoC dtsi files so device dt's can easily use that. Signed-off-by:
-
Dmitry Baryshkov authored
Follow other Qualcomm platforms and rename pm8150b_role_switch_in to pm8150_hs_in. Corresponding port is described as HS port rather than role switching. Signed-off-by:
-
Dmitry Baryshkov authored
Follow example of other platforms. Rename HS graph nodes to contain 'dwc3_hs' and link SS lanes from DWC3 controllers to QMP PHYs. Signed-off-by:
-
Dmitry Baryshkov authored
Follow example of other platforms. Rename HS graph nodes to contain 'dwc3_hs' and link SS lanes from DWC3 controllers to QMP PHYs. Signed-off-by:
-
Dmitry Baryshkov authored
Follow example of other platforms. Rename HS graph nodes to contain 'dwc3_hs' and link SS lanes from DWC3 controllers to QMP PHYs. Signed-off-by:
-
Dmitry Baryshkov authored
To follow other Qualcomm platforms, update QMP USB+DP PHYs to use newer bindings rather than old bindings which had PHYs as subdevices. Signed-off-by:
-
Dmitry Baryshkov authored
The SuperSpeed signals originate from the DWC3 host controller and then are routed through the Combo QMP PHY, where they are multiplexed with the DisplayPort signals. Add corresponding OF graph link. Reported-by:
-
Dmitry Baryshkov authored
The OF graph should describe physical signals. There is no 'role switch' signal between Type-C connector and the DWC3 USB controller. Rename endpoints to mention USB HS signal instead (this follows the example lead by other plaforms, including QRB2210 RB1, QRB4210 RB2 and all PMIC GLINK platforms). Reviewed-by:
Bryan O'Donoghue <bryan.odonoghue@linaro.org> Signed-off-by:
-
