Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp3287605ybt; Mon, 22 Jun 2020 21:16:26 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzBSLu2wNFdqYqlZZX9ay2YsoXN10j96LzRJEnoYRrE3NeyIuBPKiCdxBFwq1MViQCt85S2 X-Received: by 2002:a05:6402:17f6:: with SMTP id t22mr7263197edy.141.1592885785808; Mon, 22 Jun 2020 21:16:25 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1592885785; cv=none; d=google.com; s=arc-20160816; b=LQtEC2atZvb+TorQS8W31BkLKoyfGQ68NN9BAtDFXyq+ysmDmnPJbZSKOIoLhNabDa XK35Zz7ZMHdzOsgzkdIUMia+yJesIvY85xcwIqt/BJXee2cXeLrKRcId1XrlP3HunEfB 2/Xfv0HPkC1907BY7RXsp3Aljklm++ZAencVv8aWfp6IxYtyAUSlI1bVDPXz67DkiUvS FAqO25YwnSqaZcWjB3ENxr7HJmY7VRTuOtH4HMg7vlc+DnmOpd3hoRARIrlbPCfl3pPn EZ+usSSzNSx8GnTPxlVVdFQ6uoKWd3LYNJwKH8Miq/giBrFz+kJzqmw2ZRYPweYZzuLZ 1HoQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=5WPM/wtqX5R78+w4hNJT615kaa/5c2HUiRdfJ5fBNW4=; b=wP4wB4amd0VmGxHVIV4vkmn4t5vK4ha+4YhkjhFhGExpLUWpNU4lFjdUsPi1JZuYW8 WyN8ZEqy7OdP5xK6Ee5n5pYgMUSjmuPysXZVpEBjvBx4fY4Gyoe/LGrsPCCGPXUOQrR/ +P1CTZyl86t9M643ZmqNIZARG34j+qY/+kSNiL63mEzFne5RZHkN+eoo8XQRc8KM8vSr P0YM/uHj7SfSI3JdVhFgx20Egzz0yfE1AlXCtEXRq4B9gQcW7DsPwxgsoAUVegY/0yH2 e7L8WldzIN/Q1H21OVnMuZHkHEm0kjlp+rAwwrSHaqaDbsg/26zxUW8eSTWSmBPvoTea YexQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id mb24si717262ejb.233.2020.06.22.21.16.03; Mon, 22 Jun 2020 21:16:25 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731996AbgFWCvp (ORCPT + 99 others); Mon, 22 Jun 2020 22:51:45 -0400 Received: from mx2.suse.de ([195.135.220.15]:33024 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731858AbgFWCve (ORCPT ); Mon, 22 Jun 2020 22:51:34 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id C6987AE70; Tue, 23 Jun 2020 02:51:31 +0000 (UTC) From: =?UTF-8?q?Andreas=20F=C3=A4rber?= To: linux-realtek-soc@lists.infradead.org Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, =?UTF-8?q?James=20Tai=20=5B=E6=88=B4=E5=BF=97=E5=B3=B0=5D?= , =?UTF-8?q?Stanley=20Chang=20=5B=E6=98=8C=E8=82=B2=E5=BE=B7=5D?= , Edgar Lee , =?UTF-8?q?Andreas=20F=C3=A4rber?= , Rob Herring , devicetree@vger.kernel.org Subject: [PATCH v2 05/29] dt-bindings: soc: realtek: rtd1195-chip: Add iso-syscon property Date: Tue, 23 Jun 2020 04:50:42 +0200 Message-Id: <20200623025106.31273-6-afaerber@suse.de> X-Mailer: git-send-email 2.26.2 In-Reply-To: <20200623025106.31273-1-afaerber@suse.de> References: <20200623025106.31273-1-afaerber@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Allow to optionally specify a phandle to iso syscon to identify the chip. RTD1295 family will want to check the ISO_CHIP_INFO1 register. Signed-off-by: Andreas Färber --- A SoC specific binding would defeat the purpose of the generic Linux driver detecting the SoC based on registers. Simply allowing it all for SoC families seems the most flexible. v1 -> v2: * Instead of extending reg, allow optional iso-syscon property for RTD129x. Iso syscon currently does not have a compatible, and it may need to differ across SoC families. .../bindings/soc/realtek/realtek,rtd1195-chip.yaml | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/Documentation/devicetree/bindings/soc/realtek/realtek,rtd1195-chip.yaml b/Documentation/devicetree/bindings/soc/realtek/realtek,rtd1195-chip.yaml index 86a1de214782..dfe33c95f68d 100644 --- a/Documentation/devicetree/bindings/soc/realtek/realtek,rtd1195-chip.yaml +++ b/Documentation/devicetree/bindings/soc/realtek/realtek,rtd1195-chip.yaml @@ -11,6 +11,7 @@ maintainers: description: | The Realtek DHC SoCs have some registers to identify the chip and revision. + To identify the exact model within a family, further registers are needed. properties: compatible: @@ -19,6 +20,8 @@ properties: reg: maxItems: 1 + iso-syscon: true + required: - compatible - reg @@ -31,4 +34,10 @@ examples: compatible = "realtek,rtd1195-chip"; reg = <0x1801a200 0x8>; }; + - | + chip-info@9801a200 { + compatible = "realtek,rtd1195-chip"; + reg = <0x9801a200 0x8>; + iso-syscon = <&iso>; + }; ... -- 2.26.2