From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 34F39C64EC4 for ; Thu, 2 Feb 2023 13:38:33 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232408AbjBBNib (ORCPT ); Thu, 2 Feb 2023 08:38:31 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36664 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230456AbjBBNi3 (ORCPT ); Thu, 2 Feb 2023 08:38:29 -0500 Received: from mail-wm1-x334.google.com (mail-wm1-x334.google.com [IPv6:2a00:1450:4864:20::334]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2696A88CEA for ; Thu, 2 Feb 2023 05:38:28 -0800 (PST) Received: by mail-wm1-x334.google.com with SMTP id l8so1409028wms.3 for ; Thu, 02 Feb 2023 05:38:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:from:to:cc:subject:date:message-id:reply-to; bh=C2GNH5vdMMAxeW3/q88hsHEut53C5OA4g89R8Sa30oA=; b=sHeLh7rejmRl+Gs2HPwza9sBAUoFpbJedUDKUDHSvVf62Tt9ocWNLHxaEhcWrift9c WXietGBQxmTdvzLyoc8L7B3aVXpk7Rm6he0GNmhG6CQEN3iwwIMbR1SxYZ1t0CFfWwF0 Sr5WK/9m8siRIGJebaEnnl7PchVOqiGUqRzzW+5pmOrlHwqNeLuAK4zoNiCHnaTqnDru bnSf9zC402o9bfX4a4QfzUo2befObSYEKoDcevtFqKuStcTtd0POLq1OgDDV45qbPz0H BIQZrkO64QCVPHYv0C8YBFMtmmKBrHs2vrVJpgFYMO7lHbiCPqiIQqBK2x2vNAxFlhsX rjHg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=C2GNH5vdMMAxeW3/q88hsHEut53C5OA4g89R8Sa30oA=; b=iPwAnkAvonnIdyg1qAUpXkaYT1Yr0YOG0nxw3FhxxxpC0+RW7Dwx82ExF9Z0a1roKG 8YjqDSCKZfz/UvOjAA8zMQ+lXGmsgRVFQzwusBInVuDMtmQq4k1Fi1HRB7zoz6WYLjtD gdV1kpXhEiOrguaKnoLavpUTTybIE39AP3oqWXrlDWZeSTlRjA6iANnELSkDrsIJNeNy QhLLpMUsjVuAihTziifApa2bV4c4CfEEwHdfJyXmR3prdOkBJ2h0vRPwYKOBBnOE3p4N aO8TwmJOplmKPojkoHflKrAoSzfm4r8VFFL42mYAYrSVFez92o5p7QQKCo6UvO0UWxZR K1jA== X-Gm-Message-State: AO0yUKW4FtZKVDvMs5+vJsop40x0FL1LP+wJ0DnK3rbHN+fekZviATMc dtmF/+o7izwbMZotM22DX2Th5Q== X-Google-Smtp-Source: AK7set/pSxSbtteJLy+n0jBpDdMHf8zvoXMVU/bki2S6y/dGnUgfpt3devM6jAVBRRAIgjX33ZWNLQ== X-Received: by 2002:a05:600c:5113:b0:3df:9858:c02e with SMTP id o19-20020a05600c511300b003df9858c02emr1920935wms.3.1675345106716; Thu, 02 Feb 2023 05:38:26 -0800 (PST) Received: from hackbox.lan ([94.52.112.99]) by smtp.gmail.com with ESMTPSA id y10-20020a05600c364a00b003daf7721bb3sm4672657wmq.12.2023.02.02.05.38.25 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 02 Feb 2023 05:38:26 -0800 (PST) From: Abel Vesa To: Andy Gross , Bjorn Andersson , Konrad Dybcio , Lee Jones , Rob Herring , Krzysztof Kozlowski , "vkoul@kernel.org" , Kishon Vijay Abraham I Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, Linux Kernel Mailing List , linux-phy@lists.infradead.org Subject: [RFC v3 0/7] sm8550: Add support for eUSB2 repeater Date: Thu, 2 Feb 2023 15:38:09 +0200 Message-Id: <20230202133816.4026990-1-abel.vesa@linaro.org> X-Mailer: git-send-email 2.34.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This patchset adds support for the eUSB2 repeater found in pmic PM8550B, used along with SM8550. Since there is no dedicated generic framework for eUSB2 repeaters, the most appropriate subsystem to model it is the generic phy. This patchset also adds support for such repeater to the eUSB2 PHY found in SM8550. Basically, the eUSB2 PHY will have its own "phy" which is actually a repeater. This patchset is based on the following patchset: https://lore.kernel.org/all/?q=20230126131415.1453741-1-abel.vesa%40linaro.org Changes since v2: * moved the bindings qcom,spmi-pmic patch before the repeater schema patch in order to avoid the repeater schema validation failure due to phy pattern property not being found in qcom,spmi-pmic schema Changes since v1: * the repeater driver is implemented now as a PHY rather than adding a new generic framework for USB repeaters Abel Vesa (5): dt-bindings: mfd: qcom,spmi-pmic: Add pattern property for phy dt-bindings: phy: Add qcom,snps-eusb2-repeater schema file dt-bindings: phy: qcom,snps-eusb2-repeater: Add phy related properties phy: qcom: Add QCOM SNPS eUSB2 repeater driver arm64: dts: qcom: sm8550-mtp: Add eUSB2 repeater node Neil Armstrong (2): phy: qcom: phy-qcom-snps-eusb2: Add support for eUSB2 repeater arm64: dts: qcom: pm8550b: Add eUSB2 repeater node .../bindings/mfd/qcom,spmi-pmic.yaml | 4 + .../bindings/phy/qcom,snps-eusb2-phy.yaml | 9 + .../phy/qcom,snps-eusb2-repeater.yaml | 48 +++ arch/arm64/boot/dts/qcom/pm8550b.dtsi | 6 + arch/arm64/boot/dts/qcom/sm8550-mtp.dts | 8 + drivers/phy/qualcomm/Kconfig | 9 + drivers/phy/qualcomm/Makefile | 1 + .../phy/qualcomm/phy-qcom-eusb2-repeater.c | 278 ++++++++++++++++++ drivers/phy/qualcomm/phy-qcom-snps-eusb2.c | 18 +- 9 files changed, 380 insertions(+), 1 deletion(-) create mode 100644 Documentation/devicetree/bindings/phy/qcom,snps-eusb2-repeater.yaml create mode 100644 drivers/phy/qualcomm/phy-qcom-eusb2-repeater.c -- 2.34.1