Received: by 2002:a05:6a10:d5a5:0:0:0:0 with SMTP id gn37csp759275pxb; Thu, 30 Sep 2021 17:05:52 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxd5lSOabi8qcCT5lnBr625RPcbP3D5/9cx533UMQ3UaNzP+ALhbXLDHJ1ga08pyWHanKVS X-Received: by 2002:a62:8141:0:b0:447:96be:ac2 with SMTP id t62-20020a628141000000b0044796be0ac2mr8150100pfd.61.1633046751990; Thu, 30 Sep 2021 17:05:51 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1633046751; cv=none; d=google.com; s=arc-20160816; b=Ztnzf6Bx6hQ6w9Jgg1mdZiwB2E01LvMgyTKE8ayYdkB4cdqxymV4aijN9XntwouZ7m paUWeAskk4Tu+CYyNHuz7lgRTKoOJgMnIp/40mKuOhqC/IyqKnIMvU/VQP2IKPFJbuvm ll/LXWW+91vWJeCNbxpZ2QhHqqMzxGVgKhVktJsFDSqTyJmmj+80Lp3E3CVnKM57+Ws/ bdKosZwDQE3XP4RBdXTeDDe/6wYwWBlNgOXjZYfYMJGqs4bU12fh/H7h2HLOLUNxuUH7 6eFmH06Lz1pjEb9gxmKPLdkC0pQ9PqMzuS19C8QeU63wlm8lRES7C1kZbyOzbErXpQVH kNfA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=kZR44bSfR7ZUDmJbxUPRsrJfHdYAarPBY/B+1jyjEhw=; b=r8mgUInHNP6Nm+7KhFfz5r4bzuGZLgXQPsdMUvA0R6BrMpijQM3BX2LF8EpR8kubHD LYYv3/lRiDs1WVlH3IDtxH8uFR1Vr1JmC1rwRBZOoPkDTOtCooRYK3T3gxPR1zddMTus LEuhBU57v8ra4bmt0+hwfy/2kx93/vILGuv2itbEpaUQWf3YKJEwVJER1CsidskFMh1H WjeWVt4lWG3uSPnCFQ0XgsNFfQN1cl/Jk+HrhVLuSh5nebQL9yh32pSSTDfyQcoTtV+d TvLQ3ZiDb75ZjGCfwXRqB1zxcMq1hYvosI7X8quXIRT4973piTi4LRiQBRDTAd6U6pwV Mu4w== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=nxp.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id k14si5801826pgg.149.2021.09.30.17.05.38; Thu, 30 Sep 2021 17:05:51 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=nxp.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1351142AbhJAAGP (ORCPT + 99 others); Thu, 30 Sep 2021 20:06:15 -0400 Received: from inva020.nxp.com ([92.121.34.13]:60602 "EHLO inva020.nxp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1345765AbhJAAGH (ORCPT ); Thu, 30 Sep 2021 20:06:07 -0400 Received: from inva020.nxp.com (localhost [127.0.0.1]) by inva020.eu-rdc02.nxp.com (Postfix) with ESMTP id F08021A0D89; Fri, 1 Oct 2021 02:04:22 +0200 (CEST) Received: from smtp.na-rdc02.nxp.com (usphx01srsp001v.us-phx01.nxp.com [134.27.49.11]) by inva020.eu-rdc02.nxp.com (Postfix) with ESMTP id B5A2E1A0D85; Fri, 1 Oct 2021 02:04:22 +0200 (CEST) Received: from right.am.freescale.net (right.am.freescale.net [10.81.116.142]) by usphx01srsp001v.us-phx01.nxp.com (Postfix) with ESMTP id EBDB640A55; Thu, 30 Sep 2021 17:04:21 -0700 (MST) From: Li Yang To: Shawn Guo , Rob Herring , devicetree@vger.kernel.org, Oleksij Rempel , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Cc: Li Yang Subject: [PATCH v2 02/16] dt-bindings: i2c: imx: update schema to align with original txt binding Date: Thu, 30 Sep 2021 19:04:03 -0500 Message-Id: <20211001000417.15334-3-leoyang.li@nxp.com> X-Mailer: git-send-email 2.25.1.377.g2d2118b In-Reply-To: <20211001000417.15334-1-leoyang.li@nxp.com> References: <20211001000417.15334-1-leoyang.li@nxp.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Virus-Scanned: ClamAV using ClamSMTP Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org When the binding was converted from txt to yaml, it actually added more constrains than the original txt binding which was already used in many in-tree DTSes. Some of the newly added constrains are either not valid or not neccessary. Not all SoCs use ipg as the clock name for i2c. There is no point in having SoC integration information defined in i2c binding. Remove the clock name requirement in the schema. The original txt binding didn't require the order of tx and rx for dmas/dma-names. Many in tree DTSes are already using the other order. Both orders should just work fine. Update the schema to allow both. Signed-off-by: Li Yang --- v2: Updated the patch description Documentation/devicetree/bindings/i2c/i2c-imx.yaml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/Documentation/devicetree/bindings/i2c/i2c-imx.yaml b/Documentation/devicetree/bindings/i2c/i2c-imx.yaml index 3592d49235e0..da55d37a09a4 100644 --- a/Documentation/devicetree/bindings/i2c/i2c-imx.yaml +++ b/Documentation/devicetree/bindings/i2c/i2c-imx.yaml @@ -54,20 +54,20 @@ properties: maxItems: 1 clock-names: - const: ipg + maxItems: 1 clock-frequency: enum: [ 100000, 400000 ] dmas: - items: - - description: DMA controller phandle and request line for RX - - description: DMA controller phandle and request line for TX + minItems: 2 + maxItems: 2 dma-names: + minItems: 2 + maxItems: 2 items: - - const: rx - - const: tx + enum: [ "rx", "tx" ] sda-gpios: maxItems: 1 -- 2.25.1