- 17 Jun, 2022 4 commits
-
-
Alim Akhtar authored
Adds support for Tesla Full Self-Driving (FSD) ufs phy driver. This SoC has different cdr lock status offset. Signed-off-by:
Bharat Uppal <bharat.uppal@samsung.com> Signed-off-by:
Alim Akhtar <alim.akhtar@samsung.com> Reviewed-by:
Chanho Park <chanho61.park@samsung.com> Reviewed-by:
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Link: https://lore.kernel.org/r/20220610104119.66401-4-alim.akhtar@samsung.comSigned-off-by:
Vinod Koul <vkoul@kernel.org>
-
Alim Akhtar authored
Move CDR lock offset to drv data so that it can be extended for other SoCs which are having CDR lock at different register offset. Signed-off-by:
-
Alim Akhtar authored
Add tesla,fsd-ufs-phy compatible for Tesla Full Self-Driving (FSD) SoC. Signed-off-by:
-
Douglas Anderson authored
We're supposed to list the supplies in the dt bindings but there are none in the eDP PHY bindings. Looking at the driver in Linux, I can see that there seem to be two relevant supplies: "vdda-phy" and "vdda-pll". Let's add those to the bindings. NOTE: from looking at the Qualcomm datasheet for sc7280, it's not immediately clear how to figure out how to fill in these supplies. The only two eDP related supplies are simply described as "power for eDP 0.9V circuits" and "power for eDP 1.2V circuits". From guessing and from comparing how a similar PHY is hooked up on other similar Qualcomm boards, I'll make the educated guess that the 1.2V supply goes to "vdda-phy" and the 0.9V supply goes to "vdda-pll" and I'll use that in the example here. Signed-off-by:
Douglas Anderson <dianders@chromium.org> Reviewed-by:
Sankeerth Billakanti <quic_sbillaka@quicinc.com> Link: https://lore.kernel.org/r/20220425140619.2.Iae013f0ff4599294189f3a6e91376fad137bbabf@changeidSigned-off-by:
-
- 09 Jun, 2022 32 commits
-
-
Dmitry Baryshkov authored
Switch qcom-qmp-usb driver to use reset_control_bulk_assert / _deassert functions rather than hardcoding the loops in the driver itself. Acked-by:
Bjorn Andersson <bjorn.andersson@linaro.org> Tested-by: Bjorn Andersson <bjorn.andersson@linaro.org> # UFS, PCIe and USB on SC8180X Signed-off-by:
Dmitry Baryshkov <dmitry.baryshkov@linaro.org> Link: https://lore.kernel.org/r/20220607213203.2819885-31-dmitry.baryshkov@linaro.orgSigned-off-by:
-
Dmitry Baryshkov authored
Switch qcom-qmp-pcie-msm8996 driver to use reset_control_bulk_assert / _deassert functions rather than hardcoding the loops in the driver itself. Acked-by:
-
Dmitry Baryshkov authored
Switch qcom-qmp-pcie driver to use reset_control_bulk_assert / _deassert functions rather than hardcoding the loops in the driver itself. Acked-by:
-
Dmitry Baryshkov authored
Switch qcom-qmp-combo driver to use reset_control_bulk_assert / _deassert functions rather than hardcoding the loops in the driver itself. Acked-by:
-
Dmitry Baryshkov authored
Each USB QMP PHY device provides just a single UFS PHY. Drop support for handling multiple child PHYs. Use phy->init_count to check if the PHY was initialized rather than duplicating this count. Acked-by:
-
Dmitry Baryshkov authored
Each UFS QMP PHY device provides just a single UFS PHY. Drop support for handling multiple child PHYs. Acked-by:
-
Dmitry Baryshkov authored
Each PCIe QMP PHY device provides just a single PCIe PHY. Drop support for handling multiple child PHYs. Acked-by:
-
Dmitry Baryshkov authored
Remove the conditionals and options that are not used by any of USB PHY devices. Acked-by:
-
Dmitry Baryshkov authored
Remove the conditionals and options that are not used by any of UFS PHY devices. Acked-by:
-
Dmitry Baryshkov authored
Remove the conditionals and options that are not used by the MSM8996 PCIe PHY device. Hardcode has_lane_rst and has_phy_com_ctrl as this is the case for this PHY. Acked-by:
-
Dmitry Baryshkov authored
Remove the conditionals and options that are not used by any of PCIe PHY devices. Acked-by:
-
Dmitry Baryshkov authored
Remove the conditionals and options that are not used by any of combo USB+DP PHY devices. Acked-by:
-
Dmitry Baryshkov authored
Drop remaining support for PHY types other than USB. Acked-by:
-
Dmitry Baryshkov authored
Drop remaining support for PHY types other than UFS. Acked-by:
-
Dmitry Baryshkov authored
Drop remaining support for PHY types other than PCIe. Acked-by:
-
Dmitry Baryshkov authored
Drop remaining support for PHY types other than PCIe. Acked-by:
-
Dmitry Baryshkov authored
Drop remaining support for unused PHY types (PCIe, UFS). Acked-by:
-
Dmitry Baryshkov authored
As we have switched to the new (split) QMP PHY driver, drop the old monolithic QMP driver source. Acked-by:
-
Dmitry Baryshkov authored
Use new split QMP PHY driver and remove all monolith phy-qcom-qmp driver. Acked-by:
-
Dmitry Baryshkov authored
Change all symbol names to start with qcom_qmp_phy_usb_ rather than old qcom_qmp_phy_ Acked-by:
-
Dmitry Baryshkov authored
Change all symbol names to start with qcom_qmp_phy_ufs_ rather than old qcom_qmp_phy_ Acked-by:
-
Dmitry Baryshkov authored
Change all symbol names to start with qcom_qmp_phy_pcie_msm8996_ rather than old qcom_qmp_phy_. Acked-by:
-
Dmitry Baryshkov authored
Change all symbol names to start with qcom_qmp_phy_pcie_ rather than old qcom_qmp_phy_ Acked-by:
-
Dmitry Baryshkov authored
Change all symbol names to start with qcom_qmp_phy_combo_ rather than old qcom_qmp_phy_ Acked-by:
-
Dmitry Baryshkov authored
Drop support for all non-USB+DP compatibles from the new qmp-combo driver. Currently this will result in duplication (both in terms of code and in terms of config tables) with USB PHY support. This will be sorted out later, after fixing the combo PHY init/reinit issues. Acked-by:
-
Dmitry Baryshkov authored
Drop support for all non-USB compatibles from the new qmp-usb driver. Acked-by:
-
Dmitry Baryshkov authored
Drop support for all non-UFS compatibles from the new qmp-ufs driver. Acked-by:
-
Dmitry Baryshkov authored
Drop support for all compatibles from the new qmp-pcie driver except the qcom,msm8996-qmp-pcie-phy. This PHY differs from the rest of PCIe PHYs, so it warrants a separate device driver. Acked-by:
-
Dmitry Baryshkov authored
Drop support for all non-PCIe compatibles from the new qmp-pcie driver. The MSM8996 compat is also removed, it is going to be handled by a separate driver. Acked-by:
-
Dmitry Baryshkov authored
In order to split and cleanup the single monstrous QMP PHY driver, create blind copies of the current file. They will be used for: - PCIe (and a separate msm8996 PCIe PHY driver) - UFS - USB - Combo DP + USB Acked-by:
-
Fabien Parent authored
Add binding documentation for the MT8365 SoC. Signed-off-by:
Fabien Parent <fparent@baylibre.com> Acked-by:
-
Fabien Parent authored
Add binding documentation for the MT8365 SoC. Signed-off-by:
-
- 08 Jun, 2022 4 commits
-
-
Chanho Park authored
For exynos auto v9's UFS MPHY, We should use 0x50 offset of TSRV register configurations. So, it must be s/PHY_TRSV_REG_CFG/PHY_TRSV_REG_CFG_AUTOV9/g Fixes: d6451924 ("phy: samsung-ufs: support exynosauto ufs phy driver") Signed-off-by:
-
Abel Vesa authored
Add compatible for i.MX8DXL USB PHY. Signed-off-by:
Abel Vesa <abel.vesa@nxp.com> Acked-by:
Rob Herring <robh@kernel.org> Link: https://lore.kernel.org/r/20220607111625.1845393-9-abel.vesa@nxp.comSigned-off-by:
-
Chanho Park authored
To support secondary ufs phy device, we need to get an offset for phy isolation from the syscon DT node. If the first index argument of the node is existing, we can read the offset value and set it as isol->offset. Reviewed-by:
-
Chanho Park authored
To change an offset of pmu_isol, we need to store its data instead of having drvdata's pointer. The definition of the pmu_isol structure should be extracted from samsung_ufs_phy_drvdata and rename the name with samsung_ufs_phy_ prefix. Suggested-by:
-
