From patchwork Sun Feb 4 16:56:35 2024 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Dmitry Baryshkov X-Patchwork-Id: 769923 Received: from mail-lf1-f45.google.com (mail-lf1-f45.google.com [209.85.167.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 7172B23758 for ; Sun, 4 Feb 2024 16:56:38 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.167.45 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1707065800; cv=none; b=N8TVJgH4lPn934MGLeWrzM1SyZuUdZHHfm0JpLFYhcVz0a3XMd3Qehp47lRDn4uH3lM1/Dp9Iu5QOp8iMfj1P5GZLdnqO3G5jy+aDOh0YCrdd31hdJ/YWze54raCQdMFsCrEqLtFzrvXCN/8hitsx3wHsJke35KMDsLifbfW+XA= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1707065800; c=relaxed/simple; bh=/naVz0yogTrAGGrLDcPYQNkmDO6KhHPaYIn8ugEJCtY=; h=From:Date:Subject:MIME-Version:Content-Type:Message-Id:To:Cc; b=H8y9NuxkLqPrlmWe+a/X4sDa+B54VFMpsXsSBGQ8H80RfrpcGVYu4AB/VlpMDroAIu+jRJES70kubpTTjgeigF/a+TgiJbgrEypV9uwU4k6awW1MAfkti6x1naaLeZ/SmfEzs0WKv5FK7FLwot6xsr9oW8YbLOxKxBEyZx6Yi7M= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linaro.org; spf=pass smtp.mailfrom=linaro.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b=g/1nShbv; arc=none smtp.client-ip=209.85.167.45 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linaro.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linaro.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="g/1nShbv" Received: by mail-lf1-f45.google.com with SMTP id 2adb3069b0e04-5114b1e8819so741762e87.1 for ; Sun, 04 Feb 2024 08:56:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1707065796; x=1707670596; darn=vger.kernel.org; h=cc:to:message-id:content-transfer-encoding:mime-version:subject :date:from:from:to:cc:subject:date:message-id:reply-to; bh=wa9WkUM08vxQljPPw+aDlDsFQkr1vS2kut5JZm66AZI=; b=g/1nShbvzLTOLiurm0+TFEuNEf+hR655N8YAMdSKjPwngmfrqBvBQXsYAzTqBp8IuT hYEohmZULdXtPZdC/CpG3PrWhDNbllF5HO8DaH204/RKmo8wTNb0dlXu1IXtYZmtqrCG rfxIWrcJv9K0w2hBjY0kbSTxSxCCRyOy18GcoqwVAKWliXTZ4VCvwVxz2a0Mw04SOMmz 6PtkyD6ZG7n1R8wqVrbSGDlz9MD4704/ZkZMc3cswhXu4aT7ePo0u143r1b/YvG3m4dd yjFov5aoAj7UnTpI6WWlvgBciSmRz8+f5bm3tZtj0c2IucXNM3h+w9+/fxN0gtbWQYz9 FvCQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1707065796; x=1707670596; h=cc:to:message-id:content-transfer-encoding:mime-version:subject :date:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=wa9WkUM08vxQljPPw+aDlDsFQkr1vS2kut5JZm66AZI=; b=eopJ5Zyre/c7hSmh46Gm2I8ljXKl+KyGpsCIaEYKc3o2SFHMD0f7TgXhjyvhXoHH01 4XN16xBbRvRpp6kwMWTd3GP33KJsDMykK2aSF3wNh9JJRgMphXg17lnA2aP2u2ObmQlO ZioxhQYxpZYp/tM7W7Wm+vKTraJbt+UjOz25Av8fVwIscczEL/N8VrR8w8XEq6SPhJvw GtOVAD5cj4z5w1y/gRfaDQJc1ntzL0xrp5jobb1qlg1/n5eLoTng+JTpKrszD4XS5owt Aa3WKX7odaysi1Y7IqkQvhTffiAxiQK2uhea7c0vgV70LYeHV7gJGhQrdv7uVR8KooHM +Imw== X-Gm-Message-State: AOJu0YzhhCknCvKcGTkZ+2CXQja5ylFfkvx2sL3tHE2v8747tx7UjkIJ es2PWyPqthauhHqgxiH6KNIDDugG1gDQw6/q7UEIsvDhkYpSRsMKdGaRNYLGZW0= X-Google-Smtp-Source: AGHT+IGy22zr4BwSxp7w5EK4AqOBgOA7A4SiX8h9URT6Utr8E+g/C80ojnzM7eSTXJQgkRWpP6U45g== X-Received: by 2002:a05:6512:4011:b0:511:4995:c196 with SMTP id br17-20020a056512401100b005114995c196mr2659121lfb.59.1707065796428; Sun, 04 Feb 2024 08:56:36 -0800 (PST) X-Forwarded-Encrypted: i=0; AJvYcCX2qBH0w+34afAelcxhz6ixlYnrgnl8tULEvhz3PzSD0UHG+6SeAkKfIYXjWya8uC2ZoQF3Q1iv1nqIFjvhNdtkiQywHH3GIPlY9imk5DkNR5btZH2Q8GTDhRRsxMioihvS6oN4DtD+ne2nW9wv92GKpgaUGpRyrrMEZHHGX3ZeZFZABg926vfbdQ6f+VRhysVElG831KpcffeA3RW1zhigq2rXA7g8h3mlxP08IWwXkQa21z7qvqnB/KIT4+B8GA== Received: from umbar.lan ([192.130.178.91]) by smtp.gmail.com with ESMTPSA id o24-20020ac24e98000000b005114808c659sm456550lfr.41.2024.02.04.08.56.35 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 04 Feb 2024 08:56:35 -0800 (PST) From: Dmitry Baryshkov Date: Sun, 04 Feb 2024 18:56:35 +0200 Subject: [PATCH] dt-bindings: arm: qcom: drop the superfluous device compatibility schema Precedence: bulk X-Mailing-List: linux-arm-msm@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Message-Id: <20240204-qcom-drop-compat-v1-1-69d6cd92aa0e@linaro.org> X-B4-Tracking: v=1; b=H4sIAMLBv2UC/x2MQQqAIBAAvxJ7bkFFCvtKdIhtrT2UphFB+Pek2 8xh5oXMSTjD0LyQ+JYs4aii2wZom4+VUZbqYJSxyiiLJ4UdlxQiVojzhR0ZTY61d6qHmsXEXp5 /OU6lfLfho7ZiAAAA To: Bjorn Andersson , Konrad Dybcio , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Stephen Boyd Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org X-Mailer: b4 0.12.4 X-Developer-Signature: v=1; a=openpgp-sha256; l=3458; i=dmitry.baryshkov@linaro.org; h=from:subject:message-id; bh=/naVz0yogTrAGGrLDcPYQNkmDO6KhHPaYIn8ugEJCtY=; b=owEBbQGS/pANAwAKAYs8ij4CKSjVAcsmYgBlv8HD5vaz0YuS24rsw6R8TYihvwl8ym3O884kw IoQaCDSbq2JATMEAAEKAB0WIQRMcISVXLJjVvC4lX+LPIo+Aiko1QUCZb/BwwAKCRCLPIo+Aiko 1ZgXB/0RdtHykjPWyR4uE+ZVhlX5EAT1n/OSUoSajw39/zi9zM2Eb9Aum6EZBC+RlFDHhibCrxx hbWSK1ncF/dqvGQMv2ncSWshABiS6mgKvzNRA+TSpZicRQNl8lsk+2b2Uo8tel/vyISe1uql7dN DzJUcA/Cb8y0koQqALN8diJbrBqD+hZ44JMQSM8aVBiJlOMN5TnXGA4DM914/uB1DzZyZP77BY0 polhL0QYZhWeIwYhqPLSDc1+17SBF0cTTt8KBpDxN6LsJVfCBfBn2L8gkP81o8D3lUqdtq1Mco5 o5cTbrBoDm4tsKbo3oUUymgvPGYBNsDFKyVpJLEvjp2IdgWn X-Developer-Key: i=dmitry.baryshkov@linaro.org; a=openpgp; fpr=8F88381DD5C873E4AE487DA5199BF1243632046A The idea impressed in the commit b32e592d3c28 ("devicetree: bindings: Document qcom board compatible format") never got actually adopted. As can be seen from the existing board DT files, no device actually used the PMIC / foundry / version parts of the compatible string. Drop this compatibility string description to avoid possible confusion and keep just the generic terms and the SoC list. Fixes: b32e592d3c28 ("devicetree: bindings: Document qcom board compatible format") Signed-off-by: Dmitry Baryshkov Reviewed-by: Bjorn Andersson --- Documentation/devicetree/bindings/arm/qcom.yaml | 51 +++---------------------- 1 file changed, 5 insertions(+), 46 deletions(-) --- base-commit: 076d56d74f17e625b3d63cf4743b3d7d02180379 change-id: 20240204-qcom-drop-compat-6c21c9e1f907 Best regards, diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml index 1999a5f2f254..2b993b4c51dc 100644 --- a/Documentation/devicetree/bindings/arm/qcom.yaml +++ b/Documentation/devicetree/bindings/arm/qcom.yaml @@ -10,17 +10,10 @@ maintainers: - Bjorn Andersson description: | - Some qcom based bootloaders identify the dtb blob based on a set of - device properties like SoC and platform and revisions of those components. - To support this scheme, we encode this information into the board compatible - string. - - Each board must specify a top-level board compatible string with the following - format: - - compatible = "qcom,[-][-]-[/][-]" - - The 'SoC' and 'board' elements are required. All other elements are optional. + For devices using the Qualcomm SoC the "compatible" properties consists of + one or several "manufacturer,model" strings, describing the device itself, + followed by one or several "qcom," strings, describing the SoC used in + the device. The 'SoC' element must be one of the following strings: @@ -90,43 +83,9 @@ description: | sm8650 x1e80100 - The 'board' element must be one of the following strings: - - adp - cdp - dragonboard - idp - liquid - mtp - qcp - qrd - rb2 - ride - sbc - x100 - - The 'soc_version' and 'board_version' elements take the form of v. - where the minor number may be omitted when it's zero, i.e. v1.0 is the same - as v1. If all versions of the 'board_version' elements match, then a - wildcard '*' should be used, e.g. 'v*'. - - The 'foundry_id' and 'subtype' elements are one or more digits from 0 to 9. - - Examples: - - "qcom,msm8916-v1-cdp-pm8916-v2.1" - - A CDP board with an msm8916 SoC, version 1 paired with a pm8916 PMIC of version - 2.1. - - "qcom,apq8074-v2.0-2-dragonboard/1-v0.1" - - A dragonboard board v0.1 of subtype 1 with an apq8074 SoC version 2, made in - foundry 2. - There are many devices in the list below that run the standard ChromeOS bootloader setup and use the open source depthcharge bootloader to boot the - OS. These devices do not use the scheme described above. For details, see: + OS. These devices use the bootflow explained at https://docs.kernel.org/arch/arm/google/chromebook-boot-flow.html properties: