From patchwork Sun Nov 3 01:36:39 2019 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Patchwork-Submitter: =?utf-8?q?Andreas_F=C3=A4rber?= X-Patchwork-Id: 178365 Delivered-To: patch@linaro.org Received: by 2002:a92:409a:0:0:0:0:0 with SMTP id d26csp2570006ill; Sat, 2 Nov 2019 18:37:02 -0700 (PDT) X-Google-Smtp-Source: APXvYqz6su5QVXnfZImv+sJVB/8LxOM7zYSKVzB7dusAQtTmXddDIxPX0WDWym8bXy3i3L24DFGt X-Received: by 2002:a05:6402:205c:: with SMTP id bc28mr4288282edb.124.1572745022346; Sat, 02 Nov 2019 18:37:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1572745022; cv=none; d=google.com; s=arc-20160816; b=Q/RcsRNuM6YGlm4/WGJn5IVuw4SCWy3xeffxKEHgvw8a93Df1d+8qa+5SPk0xX9yCX B0GgDYpiB3hkAA8uR2dVc2FtO+WrwMpOYtPlQOzTwhbebWlFVOEr8Rr1KvKvAa1EQiaq 0MUdQy0ogWTQcJeCvY2DV3N9PDBu9oOcl6gCJGcT3FG33H0+OLJcDvvmWXH42+wgsq9H nSyk+H34jx3xmEoh8jEdWWGcL4VwpvlvEVAlXjm/muxULSGHUg1MCqUQqIiVb4KMrsAw xNORYjwsIoq/rw2H6vFcOctBw8PkPYSUIIYl+YfmtFrCO+B4+KppaoE7Gsx2+3Da8LLD Jh/Q== 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=xGh0S4VoKiNzS4Myr8kiF35v4pIvY4Dz1So/upIIZ28=; b=ptZbj6UFl8D2rZHsFJB5STneRVx4tZDacfo6yCMPJcrmoM4ZKUSFLk1OhK3GCfEXbh GLogQAgdpvlSpP6gORZmkEtR4n54bbJnSK4RuE5989aYChuGiEhPVkiuAjJHNUw83hDI lmbDv5dk4PmcuRJZeYwwdGhR4PsgLX2itnssmc6OtRKBHA4vj5zpXXjcaZwN/JsnKqVg g2+7ZQbzl3SxUdeWQU0wQK2LBMaiD9thjvJ9lxksJ0yT2XoXUrjZ4+xXn2edhphvdcdC JHrc9D2gitTXSfhe9U8BO/BNK1gScP8Q/HeiYhRBunhToJHst+6wFHqrRXTSQzNMIX23 jVUw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id r20si3906087edm.17.2019.11.02.18.37.02; Sat, 02 Nov 2019 18:37:02 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727536AbfKCBg5 (ORCPT + 26 others); Sat, 2 Nov 2019 21:36:57 -0400 Received: from mx2.suse.de ([195.135.220.15]:59452 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727346AbfKCBg4 (ORCPT ); Sat, 2 Nov 2019 21:36:56 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id BE909AFA8; Sun, 3 Nov 2019 01:36:54 +0000 (UTC) From: =?utf-8?q?Andreas_F=C3=A4rber?= To: linux-realtek-soc@lists.infradead.org Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, =?utf-8?q?Andreas_F=C3=A4rber?= , Rob Herring , Mark Rutland , devicetree@vger.kernel.org Subject: [RFC 05/11] dt-bindings: soc: realtek: rtd1195-chip: Extend reg property Date: Sun, 3 Nov 2019 02:36:39 +0100 Message-Id: <20191103013645.9856-6-afaerber@suse.de> X-Mailer: git-send-email 2.16.4 In-Reply-To: <20191103013645.9856-1-afaerber@suse.de> References: <20191103013645.9856-1-afaerber@suse.de> MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Allow to optionally specify a second register to identify the chip. Whether needed and which register to specify depends on the family; RTD1295 family will want the CHIP_INFO1 register. Signed-off-by: Andreas Färber --- A SoC specific binding would defeat the purpose of the generic Linux driver; is it possible to check the root node's compatible in an if: expression to prohibit using more than one reg on "realtek,rtd1195"? .../devicetree/bindings/soc/realtek/realtek,rtd1195-chip.yaml | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) -- 2.16.4 diff --git a/Documentation/devicetree/bindings/soc/realtek/realtek,rtd1195-chip.yaml b/Documentation/devicetree/bindings/soc/realtek/realtek,rtd1195-chip.yaml index 565ad2419553..e431cf559b66 100644 --- a/Documentation/devicetree/bindings/soc/realtek/realtek,rtd1195-chip.yaml +++ b/Documentation/devicetree/bindings/soc/realtek/realtek,rtd1195-chip.yaml @@ -11,13 +11,15 @@ maintainers: description: | The Realtek SoCs have some registers to identify the chip and revision. + To identify the exact model within a family, further registers are needed. properties: compatible: const: "realtek,rtd1195-chip" reg: - maxItems: 1 + minItems: 1 + maxItems: 2 required: - compatible @@ -29,4 +31,10 @@ examples: compatible = "realtek,rtd1195-chip"; reg = <0x1801a200 0x8>; }; + - | + chip-info@9801a200 { + compatible = "realtek,rtd1195-chip"; + reg = <0x9801a200 0x8>, + <0x98007028 0x4>; + }; ...