Message ID | 20221107165027.54150-2-fabrizio.castro.jz@renesas.com |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a5d:6687:0:0:0:0:0 with SMTP id l7csp2167752wru; Mon, 7 Nov 2022 08:53:38 -0800 (PST) X-Google-Smtp-Source: AMsMyM6JppBmIQMQvOSEgONnmzAmV7ToiR5wVQn5K1Mp+t9INqrlFfDeovvJwcOR92WTFmBBuiSQ X-Received: by 2002:a17:907:9724:b0:7ae:4a00:582f with SMTP id jg36-20020a170907972400b007ae4a00582fmr12724367ejc.74.1667840017908; Mon, 07 Nov 2022 08:53:37 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1667840017; cv=none; d=google.com; s=arc-20160816; b=YbIN+8zP9jNmQ+6UxDaKCB534nxfqHJgBUTADmhLGLWhWVhSQEUnJOMVWneZjnVm1I tB3uWR+RiGFr8wazprZ3StC20LkiNCt1J6h13M3QQnkA7KviWxbcORDUPcw9OGoqNbxY CT8RwMZ+bDp966Id19Rid+TiI+R9Dg69tvpZQEoksDRD/biwBSUyGgTTs93fO/kdgejI +ccwsP/MEaYzxcu/Vegn6eKttNb8IFnZNOqtEjnAYyVoZmrSpbMkP7nSXUg9c1UTougy 1ZCaLirQwJEMHvcqihCgC7ki/jmUAj4OHV8a2zt9y+J4G/geCZgs2oLnkDNmNG72o1a2 7D9A== 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=ZeJwTtFxBv+BX0bSaYiWjdAfFkHdqS48kiBZm/3j7vM=; b=ZMZduJlMk+Eq9eqYY2VTqzQhJjUGg+NB25/gRjRworMzWwduxw3MTY1oXBIdY+FKms GqM0ZO9jKeqsbD6SzsAp5ksBssQ4PGvoxhyB7gvZrHegiweQHgGIvkynpMhW/1R28s3T lDnXf0k3G4mKS7ZCfvvBUBtrN1zxwenL0JkmGZNX0NVP9m6dk0HoS9LFJRUggYqtTCJ4 iCvwqPei63hZuCMqGUvfClooDLJ4d3rxSx6atdjpaAIvuvkh/k5PSNsvP2d3Jgs4iy7m 75mgvixgJsESLpZzFfK32pYhgh1dmlbgEMPekZTm4u3fr2Jr6NavojIMTcxRwxwx86GI JCxw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=renesas.com Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id hp23-20020a1709073e1700b007a7424836d5si10259445ejc.234.2022.11.07.08.53.14; Mon, 07 Nov 2022 08:53:37 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=renesas.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232654AbiKGQvZ (ORCPT <rfc822;hjfbswb@gmail.com> + 99 others); Mon, 7 Nov 2022 11:51:25 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44220 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232756AbiKGQvG (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Mon, 7 Nov 2022 11:51:06 -0500 Received: from relmlie6.idc.renesas.com (relmlor2.renesas.com [210.160.252.172]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 6FBE4201A0; Mon, 7 Nov 2022 08:50:45 -0800 (PST) X-IronPort-AV: E=Sophos;i="5.96,145,1665414000"; d="scan'208";a="141793948" Received: from unknown (HELO relmlir5.idc.renesas.com) ([10.200.68.151]) by relmlie6.idc.renesas.com with ESMTP; 08 Nov 2022 01:50:45 +0900 Received: from mulinux.home (unknown [10.226.92.51]) by relmlir5.idc.renesas.com (Postfix) with ESMTP id EE1ED40078CD; Tue, 8 Nov 2022 01:50:40 +0900 (JST) From: Fabrizio Castro <fabrizio.castro.jz@renesas.com> To: Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Geert Uytterhoeven <geert+renesas@glider.be> Cc: Fabrizio Castro <fabrizio.castro.jz@renesas.com>, Magnus Damm <magnus.damm@gmail.com>, Biju Das <biju.das.jz@bp.renesas.com>, Wolfram Sang <wsa@kernel.org>, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org, Chris Paterson <Chris.Paterson2@renesas.com>, Biju Das <biju.das@bp.renesas.com>, Laurent Pinchart <laurent.pinchart@ideasonboard.com>, Jacopo Mondi <jacopo@jmondi.org> Subject: [PATCH v2 1/2] dt-bindings: i2c: renesas,rzv2m: Fix SoC specific string Date: Mon, 7 Nov 2022 16:50:26 +0000 Message-Id: <20221107165027.54150-2-fabrizio.castro.jz@renesas.com> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20221107165027.54150-1-fabrizio.castro.jz@renesas.com> References: <20221107165027.54150-1-fabrizio.castro.jz@renesas.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1748857014200425803?= X-GMAIL-MSGID: =?utf-8?q?1748857014200425803?= |
Series |
Fix r9a09g011 specific I2C compatible string
|
|
Commit Message
Fabrizio Castro
Nov. 7, 2022, 4:50 p.m. UTC
The preferred form for Renesas' compatible strings is: "<vendor>,<family>-<module>" Somehow the compatible string for the r9a09g011 I2C IP was upstreamed as renesas,i2c-r9a09g011 instead of renesas,r9a09g011-i2c, which is really confusing, especially considering the generic fallback is renesas,rzv2m-i2c. The first user of renesas,i2c-r9a09g011 in the kernel is not yet in a kernel release, it will be in v6.1, therefore it can still be fixed in v6.1. Even if we don't fix it before v6.2, I don't think there is any harm in making such a change. s/renesas,i2c-r9a09g011/renesas,r9a09g011-i2c/g for consistency. Fixes: ba7a4d15e2c4 ("dt-bindings: i2c: Document RZ/V2M I2C controller") Signed-off-by: Fabrizio Castro <fabrizio.castro.jz@renesas.com> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be> --- v2 - Improved changelog, as suggested by Geert and Krzysztof Documentation/devicetree/bindings/i2c/renesas,rzv2m.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
Comments
On 07/11/2022 17:50, Fabrizio Castro wrote: > The preferred form for Renesas' compatible strings is: > "<vendor>,<family>-<module>" > > Somehow the compatible string for the r9a09g011 I2C IP was upstreamed > as renesas,i2c-r9a09g011 instead of renesas,r9a09g011-i2c, which > is really confusing, especially considering the generic fallback > is renesas,rzv2m-i2c. > > The first user of renesas,i2c-r9a09g011 in the kernel is not yet in > a kernel release, it will be in v6.1, therefore it can still be > fixed in v6.1. > Even if we don't fix it before v6.2, I don't think there is any > harm in making such a change. > > s/renesas,i2c-r9a09g011/renesas,r9a09g011-i2c/g for consistency. > > Fixes: ba7a4d15e2c4 ("dt-bindings: i2c: Document RZ/V2M I2C controller") > Signed-off-by: Fabrizio Castro <fabrizio.castro.jz@renesas.com> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Best regards, Krzysztof
Dear All, This patch has been reviewed by both Geert Uytterhoeven and Krzysztof Kozlowski. The corresponding device tree patch has already been taken, I was hoping this patch could be applied to v6.3? Thanks, Fab > > On 07/11/2022 17:50, Fabrizio Castro wrote: > > The preferred form for Renesas' compatible strings is: > > "<vendor>,<family>-<module>" > > > > Somehow the compatible string for the r9a09g011 I2C IP was upstreamed > > as renesas,i2c-r9a09g011 instead of renesas,r9a09g011-i2c, which > > is really confusing, especially considering the generic fallback > > is renesas,rzv2m-i2c. > > > > The first user of renesas,i2c-r9a09g011 in the kernel is not yet in > > a kernel release, it will be in v6.1, therefore it can still be > > fixed in v6.1. > > Even if we don't fix it before v6.2, I don't think there is any > > harm in making such a change. > > > > s/renesas,i2c-r9a09g011/renesas,r9a09g011-i2c/g for consistency. > > > > Fixes: ba7a4d15e2c4 ("dt-bindings: i2c: Document RZ/V2M I2C controller") > > Signed-off-by: Fabrizio Castro <fabrizio.castro.jz@renesas.com> > > Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> > > Best regards, > Krzysztof
> This patch has been reviewed by both Geert Uytterhoeven and Krzysztof > Kozlowski. The corresponding device tree patch has already been > taken, I was hoping this patch could be applied to v6.3? linux-i2c was not on CC, so the patch was not in I2C patchwork. Thus, it was not on my list.
Hi Wolfram, Thanks for your reply. > > > > This patch has been reviewed by both Geert Uytterhoeven and > Krzysztof > > Kozlowski. The corresponding device tree patch has already been > > taken, I was hoping this patch could be applied to v6.3? > > linux-i2c was not on CC, so the patch was not in I2C patchwork. Thus, > it > was not on my list. Apologies for that, I'll resend it with linux-i2c in copy this time. Thanks, Fab
diff --git a/Documentation/devicetree/bindings/i2c/renesas,rzv2m.yaml b/Documentation/devicetree/bindings/i2c/renesas,rzv2m.yaml index c46378efc123..92e899905ef8 100644 --- a/Documentation/devicetree/bindings/i2c/renesas,rzv2m.yaml +++ b/Documentation/devicetree/bindings/i2c/renesas,rzv2m.yaml @@ -16,7 +16,7 @@ properties: compatible: items: - enum: - - renesas,i2c-r9a09g011 # RZ/V2M + - renesas,r9a09g011-i2c # RZ/V2M - const: renesas,rzv2m-i2c reg: @@ -66,7 +66,7 @@ examples: #include <dt-bindings/interrupt-controller/arm-gic.h> i2c0: i2c@a4030000 { - compatible = "renesas,i2c-r9a09g011", "renesas,rzv2m-i2c"; + compatible = "renesas,r9a09g011-i2c", "renesas,rzv2m-i2c"; reg = <0xa4030000 0x80>; interrupts = <GIC_SPI 232 IRQ_TYPE_EDGE_RISING>, <GIC_SPI 236 IRQ_TYPE_EDGE_RISING>;