- 10 Jul, 2023 40 commits
-
-
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:
Konrad Dybcio <konrad.dybcio@linaro.org> Link: https://lore.kernel.org/r/20230625-pm8953-thermal-v1-1-2b4247d2f769@z3ntu.xyzSigned-off-by:
Bjorn Andersson <andersson@kernel.org>
-
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:
Johan Hovold <johan+linaro@kernel.org> Tested-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:
Marijn Suijten <marijn.suijten@somainline.org> Signed-off-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 <krzysztof.kozlowski@linaro.org> Reviewed-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: -
Krzysztof Kozlowski authored
There is no 'msg-size' property in ramoops, so assume intention was for 'pmsg-size': sm6350-sony-xperia-lena-pdx213.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': sm6125-xiaomi-laurel-sprout.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': sm6125-sony-xperia-seine-pdx201.dtb: ramoops@ffc00000: Unevaluated properties are not allowed ('msg-size' was unexpected) Signed-off-by: -
Krzysztof Kozlowski authored
FSA4480 has only one port according to bindings: sm8450-hdk.dtb: typec-mux@42: 'port' is a required property Signed-off-by:
-
Krzysztof Kozlowski authored
FSA4480 has only one port according to bindings: sm8350-hdk.dtb: typec-mux@42: 'port' is a required property Signed-off-by:
-
Krzysztof Kozlowski authored
Use 'wakeup-source' instead of 'gpio-key,wakeup' to indicate key can wake-up the device: sm6115-fxtec-pro1x.dtb: gpio-keys: key-volume-up: Unevaluated properties are not allowed ('gpio-key,wakeup' was unexpected) Signed-off-by: -
Krzysztof Kozlowski authored
Bindings except certain pattern for gpio-keys children: sc8180x-lenovo-flex-5g.dtb: gpio-keys: 'lid' does not match any of the regexes: '^(button|event|key|switch|(button|event|key|switch)-[a-z0-9-]+|[a-z0-9-]+-(button|event|key|switch))$', 'pinctrl-[0-9]+' Signed-off-by:
-
Krzysztof Kozlowski authored
Panel takes only one port: sc8180x-primus.dtb: panel: 'ports' does not match any of the regexes: 'pinctrl-[0-9]+' Signed-off-by:
-
Krzysztof Kozlowski authored
Panel takes only one port: sc8180x-lenovo-flex-5g.dtb: panel: 'ports' does not match any of the regexes: 'pinctrl-[0-9]+' Signed-off-by:
-
Krzysztof Kozlowski authored
Bindings expect thermal node names to end with 'thermal': sc8180x-lenovo-flex-5g.dtb: thermal-zones: 'gpu-thermal-bottom', 'gpu-thermal-top' do not match any of the regexes: '^[a-zA-Z][a-zA-Z0-9\\-]{1,12}-thermal$', 'pinctrl-[0-9]+' Signed-off-by: -
Krzysztof Kozlowski authored
ADC channel node names were changed to require generic 'channel'. The user-visible part is defined via label. sc8180x-lenovo-flex-5g.dtb: adc@3100: 'die-temp@6', 'ref-gnd@0', 'vref-1p25@1' do not match any of the regexes: '^channel@[0-9a-f]+$', 'pinctrl-[0-9]+' Signed-off-by:
-
Krzysztof Kozlowski authored
ADC channel node names were changed to require generic 'channel'. The user-visible part is defined via label. sc7180-acer-aspire1.dtb: adc@3100: 'charger-thermistor@4f', 'thermistor@4e' do not match any of the regexes: '^channel@[0-9a-f]+$', 'pinctrl-[0-9]+' Signed-off-by:
Nikita Travkin <nikita@trvn.ru> Link: https://lore.kernel.org/r/20230617171541.286957-8-krzysztof.kozlowski@linaro.orgSigned-off-by:
-
Krzysztof Kozlowski authored
Use generic node names for I2C devices. Signed-off-by:
-
