- 31 May, 2024 7 commits
-
-
Tengfei Fan authored
The usb-role-switch is SM8550 SoC property, so move it from board dts to SM8550 SoC dtsi. Signed-off-by:
Tengfei Fan <quic_tengfan@quicinc.com> Reviewed-by:
Dmitry Baryshkov <dmitry.baryshkov@linaro.org> Link: https://lore.kernel.org/r/20240531090422.158813-2-quic_tengfan@quicinc.comSigned-off-by:
Bjorn Andersson <andersson@kernel.org>
-
Tengfei Fan authored
Add a simple-mfd representing IMEM on SA8775p and define the PIL relocation info region, so that post mortem tools will be able to locate the loaded remoteprocs. Signed-off-by:
Konrad Dybcio <konrad.dybcio@linaro.org> Reviewed-by:
Mukesh Ojha <quic_mojha@quicinc.com> Link: https://lore.kernel.org/r/20240531093531.238075-3-quic_tengfan@quicinc.comSigned-off-by:
-
Tengfei Fan authored
Add qcom,sa8775p-imem compatible name support. Signed-off-by:
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Link: https://lore.kernel.org/r/20240531093531.238075-2-quic_tengfan@quicinc.comSigned-off-by:
-
David Wronek authored
It looks like "cdsp_mem" was pasted in the license header by accident. Fix the typo by removing it. Signed-off-by:
David Wronek <david@mainlining.org> Fixes: ba2c082a ("arm64: dts: qcom: sm8550: Add support for Samsung Galaxy Z Fold5") Reviewed-by:
-
Unnathi Chalicheemala authored
Chipsets before SM8450 have only one broadcast register (Broadcast_OR) which is used to broadcast writes and check for status bit 0 only in all channels. >From SM8450 onwards, a new Broadcast_AND region was added which checks for status bit 1. This hasn't been updated and Broadcast_OR region was wrongly being used to check for status bit 1 all along. Hence mapping Broadcast_AND region's address space to LLCC in SM8650. Signed-off-by:
Unnathi Chalicheemala <quic_uchalich@quicinc.com> Link: https://lore.kernel.org/r/3a8804b35f44485637398faa9c0bda76813fe4d7.1717014052.git.quic_uchalich@quicinc.comSigned-off-by:
-
Unnathi Chalicheemala authored
Chipsets before SM8450 have only one broadcast register (Broadcast_OR) which is used to broadcast writes and check for status bit 0 only in all channels. >From SM8450 onwards, a new Broadcast_AND region was added which checks for status bit 1. This hasn't been updated and Broadcast_OR region was wrongly being used to check for status bit 1 all along. Hence mapping Broadcast_AND region's address space to LLCC in SM8550. Signed-off-by:
-
Unnathi Chalicheemala authored
Chipsets before SM8450 have only one broadcast register (Broadcast_OR) which is used to broadcast writes and check for status bit 0 only in all channels. >From SM8450 onwards, a new Broadcast_AND region was added which checks for status bit 1. This hasn't been updated and Broadcast_OR region was wrongly being used to check for status bit 1 all along. Hence mapping Broadcast_AND region's address space to LLCC in SM8450. Signed-off-by:
-
- 30 May, 2024 3 commits
-
-
Tengfei Fan authored
Add llcc support for the SA8775p platform. Signed-off-by:
-
Caleb Connolly authored
The SHIFTphone 8 is an upcoming QCM6490 smartphone, it has the following features: * 12GB of RAM, 512GB UFS storage * 1080p display. * Hardware kill switches for cameras and microphones * UART access via type-c SBU pins (enabled by an internal switch) Initial support includes: * Framebuffer display * UFS and sdcard storage * Battery monitoring and USB role switching via pmic glink * Bluetooth * Thermals * Wifi Signed-off-by:
Caleb Connolly <caleb@postmarketos.org> Reviewed-by:
Luca Weiss <luca.weiss@fairphone.com> Link: https://lore.kernel.org/r/20240530-otter-bringup-v3-2-79e7a28c1b08@linaro.org [bjorn: Fixed indent of block comments] Signed-off-by:
-
Caleb Connolly authored
The SHIFTphone 8 (codename otter) is a smartphone based on the QCM6490 SoC. Acked-by:
-
- 29 May, 2024 1 commit
-
-
Konrad Dybcio authored
During the initial bringup, all of the peripherals on non-SMB PMICs were either not used, or were not necessary to accomplish certain goals. This however, left a hole in the hardware description. Add the missing ones. Note that the PM8010 errors out on reads on the CRD (works fine on the QCP) for reasons unknown, but that shall be ironed out in the future.. Signed-off-by:
-
- 28 May, 2024 29 commits
-
-
Alexandru Marc Serdeliuc authored
Add support for Samsung Galaxy Z Fold5 (q5q) foldable phone based on sm8550 Currently working features: - Framebuffer - UFS - i2c - Buttons Signed-off-by:
Alexandru Marc Serdeliuc <serdeliuk@yahoo.com> Link: https://lore.kernel.org/r/20240411-samsung-galaxy-zfold5-q5q-v6-2-8142297515aa@yahoo.comSigned-off-by:
-
Alexandru Marc Serdeliuc authored
This documents Samsung Galaxy Z Fold5 (samsung,q5q) which is a foldable phone by Samsung based on the sm8550 SoC. Acked-by:
Rob Herring <robh@kernel.org> Signed-off-by:
-
Georgi Djakov authored
Add the device-tree nodes for the TBUs (translation buffer units) that are present on the sc7280 platforms. The TBUs can be used debug the kernel and provide additional information when a context faults occur. Describe all the registers, clocks, interconnects and power-domain resources that are needed for each of the TBUs. Signed-off-by:
Georgi Djakov <quic_c_gdjako@quicinc.com> Link: https://lore.kernel.org/r/20240417133731.2055383-8-quic_c_gdjako@quicinc.comSigned-off-by:
-
Georgi Djakov authored
Add the device-tree nodes for the TBUs (translation buffer units) that are present on the sdm845 platforms. The TBUs can be used debug the kernel and provide additional information when a context faults occur. Describe the all registers, clocks, interconnects and power-domain resources that are needed for each of the TBUs. Signed-off-by:
-
Krishna chaitanya chundru authored
PCIe host controller driver needs to choose the appropriate performance state of RPMh power domain and interconnect bandwidth based on the PCIe data rate. Hence, add the OPP table support to specify RPMh performance states and interconnect peak bandwidth. It should be noted that the different link configurations may share the same aggregate bandwidth, e.g., a 2.5 GT/s x2 link and a 5.0 GT/s x1 link have the same bandwidth and share the same OPP entry. Reviewed-by:
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org> Signed-off-by:
Krishna chaitanya chundru <quic_krichai@quicinc.com> Link: https://lore.kernel.org/r/20240518-opp_support-v13-4-78c73edf50de@quicinc.comSigned-off-by:
-
Krishna chaitanya chundru authored
Add PCIe-MEM & CPU-PCIe interconnect path to the PCIe nodes. Reviewed-by:
-
Sagar Cheluvegowda authored
Ethernet devices are cache coherent, mark it as such in the dtsi. Fixes: ff499a0f ("arm64: dts: qcom: sa8775p: add the first 1Gb ethernet interface") Fixes: e952348a ("arm64: dts: qcom: sa8775p: add a node for EMAC1") Signed-off-by:
Sagar Cheluvegowda <quic_scheluve@quicinc.com> Link: https://lore.kernel.org/r/20240514-mark_ethernet_devices_dma_coherent-v4-1-04e1198858c5@quicinc.comSigned-off-by:
-
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:
-
Luca Weiss authored
Enable the vibrator on the PMI632 which is used on this phone. Signed-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:
-
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:
-
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:
-
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:
-
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:
-
