On 4/3/26 3:52 PM, Luca Weiss wrote:
> Add the nodes to describe the WCN6755 chip with its PMU and Bluetooth
> parts.
>
> Thanks to Alexander Koskovich for helping with the bringup, adding
> 'clocks' to the PMU node to make Bluetooth work.
>
> Signed-off-by: Luca Weiss <[email protected]>
> ---
[...]
> + wcn6750-pmu {
> + compatible = "qcom,wcn6755-pmu", "qcom,wcn6750-pmu";
> +
> + vddaon-supply = <&vreg_s3b>;
> + vddasd-supply = <&vreg_l7b>;
> + vddpmu-supply = <&vreg_s3b>;
> + vddrfa0p8-supply = <&vreg_s3b>;
> + vddrfa1p2-supply = <&vreg_s2b>;
> + vddrfa1p7-supply = <&vreg_s1b>;
> + vddrfa2p2-supply = <&vreg_s1j>;
> +
> + bt-enable-gpios = <&tlmm 53 GPIO_ACTIVE_HIGH>;
> +
> + clocks = <&rpmhcc RPMH_RF_CLK1>;
nit: I should have caught this.. intriguing order of properties where
supplies are topmost during r3g2 review, which is presumably where
this originated from.. not a big deal though..
[...]
> + bluetooth_enable_default: bluetooth-enable-default-state {
> + pins = "gpio53";
> + function = "gpio";
> + output-low;
> + bias-disable;
nit: you shouldn't need to initially actively drive the pin, a
pull-down should be sufficient
(if insist you do, output-foo is usually below bias properties)
with or without changes:
Reviewed-by: Konrad Dybcio <[email protected]>
Konrad
