On 21/12/2022 04:12, Johan Hovold wrote:
On Wed, Dec 21, 2022 at 12:34:46AM -0300, Lux Aliaga wrote:
On 16/12/2022 08:24, Konrad Dybcio wrote:
On 15.12.2022 20:04, Lux Aliaga wrote:
Adds a UFS host controller node and its corresponding PHY to
the sm6125 platform.
+ reg = <0x04807000 0x1c4>;
+
+ power-domains = <&gcc UFS_PHY_GDSC>;
+
+ clock-names = "ref", "ref_aux";
+ clocks = <&gcc GCC_UFS_MEM_CLKREF_CLK>, <&gcc GCC_UFS_PHY_PHY_AUX_CLK>;
+
+ resets = <&ufs_mem_hc 0>;
+ reset-names = "ufsphy";
+
+ #address-cells = <1>;
+ #size-cells = <1>;
+ ranges;
+
+ status = "disabled";
+
+ ufs_mem_phy_lanes: lanes@4807400 {
+ reg = <0x4807400 0x098>,
+ <0x4807600 0x130>,
+ <0x4807c00 0x16c>;
+ #phy-cells = <0>;
+ };
I believe this is deprecated. See [1].
[1] https://lore.kernel.org/linux-arm-msm/20221104092045.17410-1-johan+linaro@xxxxxxxxxx/T/#m988f3fe3d83b76bac247aea2d9dac34f37728d65
I've looked into the documentation and this is only for the sc8280xp.
This PHY is defined as it is for the msm8996 and derivatives.
No, it's not just for sc8280xp. It's intended for all new bindings (i.e.
do not add more platforms to the msm8996 schema file).
Johan
Alright. But this would mean writing a new config for the sm6125
specifically. If we're changing how the bindings for UFS PHYs work,
wouldn't it make more sense to change the sm6115 config instead, since
they're defined pretty much the same?
--
Lux Aliaga
https://nixgoat.me/
