Message ID | 20230623081242.109131-3-tanure@linux.com |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a59:994d:0:b0:3d9:f83d:47d9 with SMTP id k13csp5615673vqr; Fri, 23 Jun 2023 01:24:17 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ7ZJj7KwBIQ8Fc2yk+DPuq4w6iZoqMoNgBSGycepOLtOfHz5MpNU3rlnT/BSKkFd6O+1Jxo X-Received: by 2002:a17:90b:1046:b0:25e:2e68:fdec with SMTP id gq6-20020a17090b104600b0025e2e68fdecmr9973176pjb.47.1687508657667; Fri, 23 Jun 2023 01:24:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1687508657; cv=none; d=google.com; s=arc-20160816; b=X8j8+sp8KvSFMgYBhu4MlZonHP9xf0yEBiEksdyafXlsfztApHpeafWfj6LccK55P0 kF19fVQKx/puDwlmo8LCQJedcfQXxYrPmzv8w57PBI6mSHcX44OK6z+wyhwjw4/Cxclz TDl2jSZ4RpK9XJ3/FFqLr6xdVqPDLZT8Jvcke6mHyAQM7IotBqKsTPAV+x1j0g/DgWAy CghTVFoCChVJo0Ld1phPBeEMYyS6Wqq6/aGG7oR8FMLSs0v+yuRKFVHzDiZgEUZuxGme 5aNRFQts5D/ePo9RKTxunO3TQCLtTAQsEjwMVUap/kDegK1RvJRAaM3XcZf63Rg3a7UP fPGA== 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=hGvZYo2Xe8nWteW+0mB4VjnmUSaAF1CaOPdHGsKnyTU=; b=wPpWM+BobAuabOV0xfc5KgN19w4MAMEF/GyV+DgsWx3pR+2K8+QfNRPMwTP2TgqoTf +uw+yggYDkfNmhT+rBTTeLqFcChe2M7Il0lpkAEMIcOC1rjTuO+SDeA5HN/a0pVj+ZOA HPVlLg8JWLAqqxY1XE1B/CpBrYlzOyEcNrukpmWpd/JwsDFEX/AU6GB44WEmNUigoOiI EoDdigPrXct3HCVPQTJBfG8kTYwsP76FdQLrLvgG2jIJs8yoLGGUi/bKgEHg5Nnf5YCF iX384Di62o/q3nF7yxmutAcw8J5PnS+W3EfCCaZXKH64Mt1z45/vUejwgjfjHbkldmZG hpXw== 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 Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id s15-20020a17090a764f00b0025e8047d512si1458394pjl.147.2023.06.23.01.24.01; Fri, 23 Jun 2023 01:24:17 -0700 (PDT) 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231768AbjFWIMz (ORCPT <rfc822;maxin.john@gmail.com> + 99 others); Fri, 23 Jun 2023 04:12:55 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51766 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231175AbjFWIMt (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Fri, 23 Jun 2023 04:12:49 -0400 Received: from mail-lf1-f54.google.com (mail-lf1-f54.google.com [209.85.167.54]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 636B61FEF; Fri, 23 Jun 2023 01:12:48 -0700 (PDT) Received: by mail-lf1-f54.google.com with SMTP id 2adb3069b0e04-4f875b267d9so383029e87.1; Fri, 23 Jun 2023 01:12:48 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687507966; x=1690099966; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=hGvZYo2Xe8nWteW+0mB4VjnmUSaAF1CaOPdHGsKnyTU=; b=YH68iH/UlDCgUZIunI2Z1XOlLO+wfo//pkUFRYmF9stx6gxqRWyFlyFHf0Dq2mhFuZ rWRhio/BLRpLACKwsD02wi0ziCEuf7sJxxClnX4RipnjCTFilzchKCdt8T0mCxExpYth HijWA5OfMp8KgxshPOX68+pvCgFlx6ybZuoLoQe4y1fMqUK2+ehR1Dcw0nHtdJItrmxL OUvTk+K09qqz/fU3xQ6Fx4QhjnyuKTQpjTlkX1snwdalLiFMxJI+rvJCnRJToZXrlr4X o8XukkYQXvFEv9Mqj8x7EbA4Bvbw/eyJ85151BKQzAh5ND9Z+DsOsYCSBuMFh7YffMVq H8wg== X-Gm-Message-State: AC+VfDzbBTd82UiFegyva13/yretUWAqTN/VW4CqwHzEfQIwhlj1T7A6 7KMJTUdY30D9zAAeK9/3FaY= X-Received: by 2002:a19:8c49:0:b0:4f8:6e6e:4100 with SMTP id i9-20020a198c49000000b004f86e6e4100mr9597994lfj.52.1687507966306; Fri, 23 Jun 2023 01:12:46 -0700 (PDT) Received: from ryzen.lan (cpc87451-finc19-2-0-cust61.4-2.cable.virginm.net. [82.11.51.62]) by smtp.gmail.com with ESMTPSA id l21-20020a7bc455000000b003f9b29ba838sm1594141wmi.35.2023.06.23.01.12.45 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 23 Jun 2023 01:12:45 -0700 (PDT) From: Lucas Tanure <tanure@linux.com> To: Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Conor Dooley <conor+dt@kernel.org>, Neil Armstrong <neil.armstrong@linaro.org>, Jerome Brunet <jbrunet@baylibre.com>, Kevin Hilman <khilman@baylibre.com> Cc: Nick <nick@khadas.com>, Artem <art@khadas.com>, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-amlogic@lists.infradead.org, linux-arm-kernel@lists.infradead.org, Lucas Tanure <tanure@linux.com> Subject: [PATCH v5 2/4] dt-bindings: serial: amlogic,meson-uart: Add compatible string for T7 Date: Fri, 23 Jun 2023 09:12:40 +0100 Message-ID: <20230623081242.109131-3-tanure@linux.com> X-Mailer: git-send-email 2.41.0 In-Reply-To: <20230623081242.109131-1-tanure@linux.com> References: <20230623081242.109131-1-tanure@linux.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1.4 required=5.0 tests=BAYES_00, FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM,HEADER_FROM_DIFFERENT_DOMAINS, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=no 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?1769481077993554325?= X-GMAIL-MSGID: =?utf-8?q?1769481077993554325?= |
Series |
Add Amlogic A311D2 and Khadas Vim4 Board Support
|
|
Commit Message
Lucas Tanure
June 23, 2023, 8:12 a.m. UTC
Amlogic T7 SoCs uses the same UART controller as S4 SoCs and G12A.
There is no need for an extra compatible line in the driver, but
add T7 compatible line for documentation.
Signed-off-by: Lucas Tanure <tanure@linux.com>
---
.../devicetree/bindings/serial/amlogic,meson-uart.yaml | 4 ++++
1 file changed, 4 insertions(+)
Comments
On 23/06/2023 10:12, Lucas Tanure wrote: > Amlogic T7 SoCs uses the same UART controller as S4 SoCs and G12A. > There is no need for an extra compatible line in the driver, but > add T7 compatible line for documentation. > > Signed-off-by: Lucas Tanure <tanure@linux.com> > --- > .../devicetree/bindings/serial/amlogic,meson-uart.yaml | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml b/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml > index 01ec45b3b406..ad970c9ed1c7 100644 > --- a/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml > +++ b/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml > @@ -50,6 +50,10 @@ properties: > items: > - const: amlogic,meson-g12a-uart > - const: amlogic,meson-gx-uart > + - description: UART controller on T7 compatible SoCs Your description is rather incorrect. This is UART on SoCs compatible with S4, not with T7. Otherwise what do you expect to grow later when adding more compatible devices? Just drop the description, it's kind of obvious when done correctly (but can be misleading if done wrong). Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Best regards, Krzysztof
On Fri, Jun 23, 2023 at 9:51 AM Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> wrote: > > On 23/06/2023 10:12, Lucas Tanure wrote: > > Amlogic T7 SoCs uses the same UART controller as S4 SoCs and G12A. > > There is no need for an extra compatible line in the driver, but > > add T7 compatible line for documentation. > > > > Signed-off-by: Lucas Tanure <tanure@linux.com> > > --- > > .../devicetree/bindings/serial/amlogic,meson-uart.yaml | 4 ++++ > > 1 file changed, 4 insertions(+) > > > > diff --git a/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml b/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml > > index 01ec45b3b406..ad970c9ed1c7 100644 > > --- a/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml > > +++ b/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml > > @@ -50,6 +50,10 @@ properties: > > items: > > - const: amlogic,meson-g12a-uart > > - const: amlogic,meson-gx-uart > > + - description: UART controller on T7 compatible SoCs > > Your description is rather incorrect. This is UART on SoCs compatible > with S4, not with T7. Otherwise what do you expect to grow later when > adding more compatible devices? Just drop the description, it's kind of > obvious when done correctly (but can be misleading if done wrong). > > Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> > Sorry, but S4 is already added in another way, which accepts just an S4 compatible string. But for T7 we need a fallback. Could you let me know what you're asking here? Redo S4 and add T7? Or do T7 in another different way that I didn't get? Do you want a v6 patch series? If yes, could you be more clear about how you want it? > > Best regards, > Krzysztof >
On 23/06/2023 19:53, Lucas Tanure wrote: > On Fri, Jun 23, 2023 at 9:51 AM Krzysztof Kozlowski > <krzysztof.kozlowski@linaro.org> wrote: >> >> On 23/06/2023 10:12, Lucas Tanure wrote: >>> Amlogic T7 SoCs uses the same UART controller as S4 SoCs and G12A. >>> There is no need for an extra compatible line in the driver, but >>> add T7 compatible line for documentation. >>> >>> Signed-off-by: Lucas Tanure <tanure@linux.com> >>> --- >>> .../devicetree/bindings/serial/amlogic,meson-uart.yaml | 4 ++++ >>> 1 file changed, 4 insertions(+) >>> >>> diff --git a/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml b/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml >>> index 01ec45b3b406..ad970c9ed1c7 100644 >>> --- a/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml >>> +++ b/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml >>> @@ -50,6 +50,10 @@ properties: >>> items: >>> - const: amlogic,meson-g12a-uart >>> - const: amlogic,meson-gx-uart >>> + - description: UART controller on T7 compatible SoCs >> >> Your description is rather incorrect. This is UART on SoCs compatible >> with S4, not with T7. Otherwise what do you expect to grow later when >> adding more compatible devices? Just drop the description, it's kind of >> obvious when done correctly (but can be misleading if done wrong). >> >> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> >> > Sorry, but S4 is already added in another way, which accepts just an > S4 compatible string. > But for T7 we need a fallback. > Could you let me know what you're asking here? Redo S4 and add T7? Or > do T7 in another different way that I didn't get? I comment only about the description, so why touching anything else? You did not add here T7 compatible SoCs. You added here S4 compatible SoCs. > Do you want a v6 patch series? If yes, could you be more clear about > how you want it? No need. If you are going to send v6, you can as well drop the description. --- This is an automated instruction, just in case, because many review tags are being ignored. If you do not know the process, here is a short explanation: Please add Acked-by/Reviewed-by/Tested-by tags when posting new versions, under or above your Signed-off-by tag. Tools like b4 can help here. However, there's no need to repost patches *only* to add the tags. The upstream maintainer will do that for acks received on the version they apply. https://elixir.bootlin.com/linux/v5.17/source/Documentation/process/submitting-patches.rst#L540 Best regards, Krzysztof
On Fri, Jun 23, 2023 at 6:56 PM Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> wrote: > > On 23/06/2023 19:53, Lucas Tanure wrote: > > On Fri, Jun 23, 2023 at 9:51 AM Krzysztof Kozlowski > > <krzysztof.kozlowski@linaro.org> wrote: > >> > >> On 23/06/2023 10:12, Lucas Tanure wrote: > >>> Amlogic T7 SoCs uses the same UART controller as S4 SoCs and G12A. > >>> There is no need for an extra compatible line in the driver, but > >>> add T7 compatible line for documentation. > >>> > >>> Signed-off-by: Lucas Tanure <tanure@linux.com> > >>> --- > >>> .../devicetree/bindings/serial/amlogic,meson-uart.yaml | 4 ++++ > >>> 1 file changed, 4 insertions(+) > >>> > >>> diff --git a/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml b/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml > >>> index 01ec45b3b406..ad970c9ed1c7 100644 > >>> --- a/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml > >>> +++ b/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml > >>> @@ -50,6 +50,10 @@ properties: > >>> items: > >>> - const: amlogic,meson-g12a-uart > >>> - const: amlogic,meson-gx-uart > >>> + - description: UART controller on T7 compatible SoCs > >> > >> Your description is rather incorrect. This is UART on SoCs compatible > >> with S4, not with T7. Otherwise what do you expect to grow later when > >> adding more compatible devices? Just drop the description, it's kind of > >> obvious when done correctly (but can be misleading if done wrong). > >> > >> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> > >> > > Sorry, but S4 is already added in another way, which accepts just an > > S4 compatible string. > > But for T7 we need a fallback. > > Could you let me know what you're asking here? Redo S4 and add T7? Or > > do T7 in another different way that I didn't get? > > I comment only about the description, so why touching anything else? You > did not add here T7 compatible SoCs. You added here S4 compatible SoCs. > > > Do you want a v6 patch series? If yes, could you be more clear about > > how you want it? > > No need. If you are going to send v6, you can as well drop the description. > I can't just remove that line, as it doesn't pass the checks. I will change it to S4. > > --- > > This is an automated instruction, just in case, because many review tags > are being ignored. If you do not know the process, here is a short > explanation: > > Please add Acked-by/Reviewed-by/Tested-by tags when posting new > versions, under or above your Signed-off-by tag. Tools like b4 can help > here. However, there's no need to repost patches *only* to add the tags. > The upstream maintainer will do that for acks received on the version > they apply. > > https://elixir.bootlin.com/linux/v5.17/source/Documentation/process/submitting-patches.rst#L540 > > Best regards, > Krzysztof >
diff --git a/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml b/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml index 01ec45b3b406..ad970c9ed1c7 100644 --- a/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml +++ b/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml @@ -50,6 +50,10 @@ properties: items: - const: amlogic,meson-g12a-uart - const: amlogic,meson-gx-uart + - description: UART controller on T7 compatible SoCs + items: + - const: amlogic,meson-t7-uart + - const: amlogic,meson-s4-uart reg: maxItems: 1