- 10 Jul, 2023 40 commits
-
-
Konrad Dybcio authored
The RPMCC node should be fed a reference to the XO fixed clock. Do so. Signed-off-by:
Konrad Dybcio <konrad.dybcio@linaro.org> Reviewed-by:
Jeffrey Hugo <quic_jhugo@quicinc.com> Link: https://lore.kernel.org/r/20230627-topic-98_rpmcc-v1-1-4024e43ad0fc@linaro.orgSigned-off-by:
Bjorn Andersson <andersson@kernel.org>
-
Konrad Dybcio authored
UART6 is used for debug (routed via uSD pins) and UART9 is connected to the bluetooth chip. Set indexed aliases to make the GENI UART driver happy and route serial traffic through the debug uart by default. Fixes: 30a7f99b ("arm64: dts: qcom: Add support for SONY Xperia XZ2 / XZ2C / XZ3 (Tama platform)") Signed-off-by:
Marijn Suijten <marijn.suijten@somainline.org> Link: https://lore.kernel.org/r/20230627-topic-tama_uart-v1-1-0fa790248db8@linaro.orgSigned-off-by:
-
Konrad Dybcio authored
The interrupt line was previously not described. Take care of that. Fixes: 1e39255e ("arm64: dts: msm8996: Add device node for qcom,dwc3") Signed-off-by:
-
Konrad Dybcio authored
'pin-switch-delay-us' is not used anywhere in the mainline kernel. Drop it. Signed-off-by:
Bryan O'Donoghue <bryan.odonoghue@linaro.org> Link: https://lore.kernel.org/r/20230627-topic-more_bindings-v1-4-6b4b6cd081e5@linaro.orgSigned-off-by:
-
Konrad Dybcio authored
Add the missing property to fix the dt checker warning: qcom/apq8039-t2.dtb: l2-cache: 'cache-unified' is a required property Fixes: 61550c6c ("arm64: dts: qcom: Add msm8939 SoC") Signed-off-by:
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Reviewed-by:
-
Konrad Dybcio authored
As of today, the only cool and legal way to get ARM64 SMP going is via PSCI (or spin tables). Sadly, not all chip and device vendors were considerate of this in the early days of arm64. Qualcomm, for example reused their tried-and-true spin-up method from MSM8974 and their Krait/ arm32 Cortex designs. MSM8916 supports SMP with its arm32 dt overlay, as probably could 8939. But the arm64 DT should not define non-PSCI SMP or CPUidle stuff. Drop the qcom,idle-state-spc compatible (associated with Qualcomm-specific CPUIdle) to make the dt checker happy: apq8039-t2.dtb: idle-states: cpu-sleep-0:compatible: ['qcom,idle-state-spc', 'arm,idle-state'] is too long Fixes: 61550c6c ("arm64: dts: qcom: Add msm8939 SoC") Signed-off-by:
Benjamin Li <benl@squareup.com> Link: https://lore.kernel.org/r/20230627-topic-more_bindings-v1-2-6b4b6cd081e5@linaro.orgSigned-off-by:
-
Konrad Dybcio authored
Commit 2b616f86 ("arm64: dts: qcom: sc7180: rename labels for DSI nodes") broke reg-names, possibly with search-and-replace. Fix it. Fixes: 2b616f86 ("arm64: dts: qcom: sc7180: rename labels for DSI nodes") Signed-off-by:
-
Konrad Dybcio authored
Add the CPU OPP tables including core frequency and L3 bus frequency. The L3 throughput values were chosen by studying the frequencies available in HW LUT and picking the highest one that's less than the CPU frequency. They will be replaced with a dynamic, bwmon-style decision maker once support for MEMLAT is introduced upstream. Available values from the HW LUT: 300000 556800 652800 768000 844800 921600 1171200 1382400 1497600 This commit dramatically improves overall performance of the system. Signed-off-by:
-
Johan Hovold authored
Unless explicitly specified the interrupt-parent property is inherited from the parent node on Linux even though this may not be in full compliance with the devicetree specification. Following commit 2d5cab92 ("arm64: dts: qcom: sc8280xp-pmics: Specify interrupt parent explicitly"), add an explicit interrupt parent also for the PMIC RTC node for the benefit of other operating systems which may be confused by this omission. Note that any such OS must still implement a fallback to the root interrupt domain as most devicetrees are written under the assumption that the interrupt parent is inherited. Reported-by:
Patrick Wildt <patrick@blueri.se> Signed-off-by:
Johan Hovold <johan+linaro@kernel.org> Acked-by:
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org> Reviewed-by:
-
Luca Weiss authored
With the ICE driver now merged let's convert the ufs node to use the new style. Signed-off-by:
Luca Weiss <luca.weiss@fairphone.com> Reviewed-by:
-
Rob Herring authored
The defined value for "status" is "disabled", not "disable". Signed-off-by:
Rob Herring <robh@kernel.org> Reviewed-by:
-
Bjorn Andersson authored
Merge a set of new SC8280XP GCC GDSC constants from a topic branch, in order to allow them being used in DeviceTree source.
-
Konrad Dybcio authored
There are 10 more GDSCs that we've not been caring about, and by extension (and perhaps even more importantly), not putting to sleep. Add them. Fixes: a66a82f2 ("dt-bindings: clock: Add Qualcomm SC8280XP GCC bindings") Acked-by:
-
Luca Weiss authored
Define the themal zones using the temperature values found in the downstream 4.9 sources so that the spmi-temp-alarm driver becomes active. Signed-off-by:
Luca Weiss <luca@z3ntu.xyz> Reviewed-by:
-
Sridharan S N authored
Add a dtsi file to include interfaces that are common across IPQ5332 RDPs. Signed-off-by:
Sridharan S N <quic_sridsn@quicinc.com> Link: https://lore.kernel.org/r/20230623090001.27778-1-quic_sridsn@quicinc.comSigned-off-by:
-
Konrad Dybcio authored
The SCM interconnect path was missing. Add it. Fixes: 152d1faf ("arm64: dts: qcom: add SC8280XP platform") Signed-off-by:
-
Bartosz Golaszewski authored
Enable the first 1Gb ethernet port on sa8775p-ride development board. Signed-off-by:
Bartosz Golaszewski <bartosz.golaszewski@linaro.org> Reviewed-by:
Andrew Halaney <ahalaney@redhat.com> Link: https://lore.kernel.org/r/20230622120142.218055-6-brgl@bgdev.plSigned-off-by:
-
Bartosz Golaszewski authored
Add the MDC and MDIO pin functions for ethernet0 on sa8775p-ride. Signed-off-by:
-
Bartosz Golaszewski authored
Enable the internal PHY on sa8775p-ride. Signed-off-by:
-
Bartosz Golaszewski authored
Add the node for the first ethernet interface on sa8775p platforms. Signed-off-by:
-
Bartosz Golaszewski authored
Add the internal SGMII/SerDes PHY node for sa8775p platforms. Signed-off-by:
-
Neil Armstrong authored
Qualcomm's Mobile Test Platforms devices are handsets, set the chassis-type property to 'handset'. Signed-off-by:
Neil Armstrong <neil.armstrong@linaro.org> Reviewed-by:
-
Neil Armstrong authored
Qualcomm's Mobile Test Platforms devices are handsets, set the chassis-type property to 'handset'. Signed-off-by:
-
Neil Armstrong authored
Qualcomm's Hardware Development Kits devices are embedded platforms, set the chassis-type property to 'embedded'. Signed-off-by:
-
Neil Armstrong authored
Qualcomm's Reference Devices are handsets, set the chassis-type property to 'handset'. Signed-off-by:
-
Neil Armstrong authored
Qualcomm's Mobile Test Platforms devices are handsets, set the chassis-type property to 'handset'. Signed-off-by:
-
Raymond Hackley authored
Sony Xperia M4 Aqua is a handset. Add the chassis-type = "handset"; to it. Signed-off-by:
Raymond Hackley <raymondhackley@protonmail.com> Reviewed-by:
-
Konrad Dybcio authored
Enable the A610 GPU and provide a firmware path to the ZAP blob. Signed-off-by:
-
Konrad Dybcio authored
Enable the A610 GPU and provide a firmware path to the ZAP blob. Reviewed-by:
Dmitry Baryshkov <dmitry.baryshkov@linaro.org> Signed-off-by:
-
Konrad Dybcio authored
Enable the required nodes, add the required pins and tweak a regulator to enable non-simplefb display on the Tab P11. Do note that there exists a second SKU with a different panel+touch combo, but due to insufficient information, that will need to be handled separately. Signed-off-by:
-
Konrad Dybcio authored
Introduce nodes for the A610 GPU and its GMU wrapper along with the speedbin fuse entry in QFPROM. Reviewed-by:
-
Bjorn Andersson authored
The external regulators in the CRD seems to have inherited their names from the X13s DeviceTree, correct them. Signed-off-by:
Bjorn Andersson <quic_bjorande@quicinc.com> Reviewed-by:
-
Bjorn Andersson authored
The vreg_misc_3p3 regulator is controlled by PMC8280_1 GPIO 2, not 1, on the CRD. Fixes: ccd3517f ("arm64: dts: qcom: sc8280xp: Add reference device") Signed-off-by:
-
Konrad Dybcio authored
Set up the corresponding GPIOs properly and add the leftover hardware buttons to mark this piece of the puzzle complete. Fixes: 46e14907 ("arm64: dts: qcom: sm8250-edo: Add hardware keys") Reviewed-by:
-
Konrad Dybcio authored
Xperia 1 II / PRO use the Dialog SLG51000 PMIC for powering some camera sensors. Add the required nodes to support it and remove its remnants from -edo.dtsi, as it's absent on 5 II. Signed-off-by:
-
Konrad Dybcio authored
Sony ever so graciously provides GPIO line names in their downstream kernel (though sometimes they are not 100% accurate and you can judge that by simply looking at them and with what drivers they are used). Add these to the PDX203&206 DTSIs to better document the hardware. Diff between 203 and 206: pm8009_gpios < "CAM_PWR_LD_EN", > "NC", pm8150_gpios < "NC", > "G_ASSIST_N", < "WLC_EN_N", /* GPIO_10 */ > "NC", /* GPIO_10 */ Which is due to 5 II having an additional Google Assistant hardware button and 1 II having a wireless charger & different camera wiring to accommodate the additional 3D iToF sensor. Signed-off-by:
-
Konrad Dybcio authored
Sony ever so graciously provides GPIO line names in their downstream kernel (though sometimes they are not 100% accurate and you can judge that by simply looking at them and with what drivers they are used). Add these to the PDX203&206 DTSIs to better document the hardware. Diff between 203 and 206: < "CAM_PWR_A_CS", > "FRONTC_PWR_EN", < "CAM4_MCLK", < "TOF_RST_N", > "NC", > "NC", < "WLC_I2C_SDA", < "WLC_I2C_SCL", /* GPIO_120 */ > "NC", > "NC", < "WLC_INT_N", > "NC", Which makes sense, as 203 has a 3D iToF, slightly different camera power wiring and WLC (WireLess Charging). Signed-off-by:
-
Jakob Hauser authored
For the regulators, apply the same settings as in the downstream devicetree [1], including the "regulator-always-on" for the SAFE_LDO. For the voltage of SAFE_LDO, however, there is only one voltage of 4.9 V available in the mainline driver [2][3]. The values of the battery data evolve from following sources: - precharge current: 450 mA corresponds to the default value of the chip. It doesn't get changed by the downstream Android driver. Therefore let's stick to this value. - constant charge current: The 1000 mA are taken from the downstream devicetree of the serranove battery. It's not easy to spot. The value is in the line "input_current_limit" [4]. The rows are according to the power supply type, the 4th value stands for "main supply" [5]. That's the value used by the Android driver when a charging cable is plugged into the device. - charge termination current: In the downstream devicetree of the battery that's the line "full_check_current_1st", which contains the 150 mA [6]. - precharge voltage: This one doesn't get set in the downstream Android driver. The chip's default is 2.8 V. That seemed too low to have a notable effect of handling the battery gentle. The chosen value of 3.5 V is a bit arbitrary and possibly rather high. As the device is already several years old and therefore most batteries too, a value on the safe side seems reasonable. - constant charge voltage: The value of 4.35 V is set in the line "chg_float_voltage" of the downstream battery devicetree [7]. The "connector" sub-node in the extcon node, the "battery" node in the general section and the line "power-supplies" in the fuel-gauge node result from the way of implementation documented in the dt-bindings of rt5033-charger [8] and mfd rt5033 [9]. [1] https://github.com/msm8916-mainline/linux-downstream/blob/GT-I9195I/arch/arm/boot/dts/samsung/msm8916/msm8916-sec-serranovelte-eur-r03.dtsi#L135-L181 [2] https://github.com/torvalds/linux/blob/v6.3/include/linux/mfd/rt5033-private.h#L211-L212 [3] https://github.com/torvalds/linux/blob/v6.3/drivers/regulator/rt5033-regulator.c#L83 [4] https://github.com/msm8916-mainline/linux-downstream/blob/GT-I9195I/arch/arm/boot/dts/samsung/msm8916/msm8916-sec-serranovelte-battery-r01.dtsi#L100 [5] https://github.com/msm8916-mainline/linux-downstream/blob/GT-I9195I/include/linux/power_supply.h#L173-L177 [6] https://github.com/msm8916-mainline/linux-downstream/blob/GT-I9195I/arch/arm/boot/dts/samsung/msm8916/msm8916-sec-serranovelte-battery-r01.dtsi#L102 [7] https://github.com/msm8916-mainline/linux-downstream/blob/GT-I9195I/arch/arm/boot/dts/samsung/msm8916/msm8916-sec-serranovelte-battery-r01.dtsi#L95 [8] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/Documentation/devicetree/bindings/power/supply/richtek,rt5033-charger.yaml?h=next-20230616 [9] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/Documentation/devicetree/bindings/mfd/richtek,rt5033.yaml?h=next-20230616Signed-off-by:
Jakob Hauser <jahau@rocketmail.com> Link: https://lore.kernel.org/r/20230619203743.8136-1-jahau@rocketmail.comSigned-off-by:
-
Krzysztof Kozlowski authored
There is no 'msg-size' property in ramoops, so assume intention was for 'pmsg-size': sm8250-sony-xperia-edo-pdx206.dtb: ramoops@ffc00000: Unevaluated properties are not allowed ('msg-size' was unexpected) Signed-off-by: -
Krzysztof Kozlowski authored
There is no 'msg-size' property in ramoops, so assume intention was for 'pmsg-size': sm8150-sony-xperia-kumano-griffin.dtb: ramoops@ffc00000: Unevaluated properties are not allowed ('msg-size' was unexpected) Signed-off-by:
-
