Message ID | 20230621133215.109254-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 k13csp4374601vqr; Wed, 21 Jun 2023 06:43:46 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ4VhQ+xL4gTfpJtxJb9+O4OrrHlA0aMIc/EkxtK2yuBvVZj2hDoGCPgJ+Yu1PZ3ctnsIo3V X-Received: by 2002:a05:6a00:1398:b0:668:7292:b2d4 with SMTP id t24-20020a056a00139800b006687292b2d4mr11137320pfg.8.1687355025813; Wed, 21 Jun 2023 06:43:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1687355025; cv=none; d=google.com; s=arc-20160816; b=F1scq4GKRFXLyV5K7BbZg/vFtdd/BjNeaRTNs92RJRFdXKg5WcDuz48AopAerXa8ow QGXtlGGax2nWXTCcRglA+l0FqDOh9d+mfAQyEMgH2Mc/JoK13bF491r8xKIHJwRJUC1j KnClIIXK9LcjQyoUxHDAvtqRtnnIXteuCnaAb7eoPdwFw2w5KQTogcYk6JMtWET2O+Ob f6jXw8kdLmHxZiZGUgAOnC1h0ZAKaB5JNeFkDGC1dvuqerrZkcxrZHAXuaPmnUwbf3fR cuaRT6V1dSnCOMVOh0vdpeKAhN8qsvIym6uSNj3kTJdPWFdkC40psZwzGHUqNBXO4FLX Ualg== 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=+epYfBWfb+1x9J48BBgefK4RbF1tT6DdUYZkz0j7yII=; b=tg4sUMvYoi9W4oLat6AGitTWqFcKpwJMYl8zeWfOBYDvV/5mRjyGJURNwd4COGyzUO wy2JRyL3oldTrw4hH+KiBe0F4M2YxmvE3bVSj9glUBlDUBjFP0kN9beMsscoC1cJg8xF Qnv1JC6YNh933yE4oBaQHBwVqreXisPCbfg1en3CQvtN+C+Dt/pMuyVok1wTFRwxAvYF /bh91qMgksz0FpK5ZEOfDuUYKaG6n/3IyTBWoTa4S8yapdNk2uDjJ5tmrgzJgntJWRlc XhsGAxevTn5k1KlgzYIduv+WHJHxiT6oBKlmbHQ/oHyRBKlrmTGDDeI0iYFD30L1dT0r 9Y3Q== 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 z11-20020a6552cb000000b00553ebb05d18si3254335pgp.112.2023.06.21.06.43.32; Wed, 21 Jun 2023 06:43:45 -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 S231768AbjFUNcd (ORCPT <rfc822;maxin.john@gmail.com> + 99 others); Wed, 21 Jun 2023 09:32:33 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60264 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231896AbjFUNc3 (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Wed, 21 Jun 2023 09:32:29 -0400 Received: from mail-oi1-f180.google.com (mail-oi1-f180.google.com [209.85.167.180]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5519E19AB; Wed, 21 Jun 2023 06:32:28 -0700 (PDT) Received: by mail-oi1-f180.google.com with SMTP id 5614622812f47-39ecf031271so2748802b6e.1; Wed, 21 Jun 2023 06:32:28 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687354347; x=1689946347; 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=+epYfBWfb+1x9J48BBgefK4RbF1tT6DdUYZkz0j7yII=; b=OMwS+96FQA1ZGTmDpCLiKjeF6afzAUFnejnLRpu6JHFTM0b1aNQwmxa6VbAibxcSWu udcm3Qh6+qgJY7qyjynpElBRwU0OoT22LmijPL+1fzFZQjVUULR1rX4B+P4Ct5i6iNb0 lb0K285TswW2+O7qtztiQzKXgtAXy+k3AGrtsnrFPc4FD1+HMIHcEkmzQrGkLrDNZKKc //ZiDHOQ8ceVUdjjQuANndEz5v0qRSCctrg0Qe1I8URZLyglm6DfZn5lI6voJHHRfz6X HZsxP3yTw8nM/u7VMLHQ/jaNiec+TSwj6JyFLBgHv63BUtGvDao9clCNuGJIIoQHeZa5 MWBw== X-Gm-Message-State: AC+VfDwvSsOt86IgHCn3ARRmFbW9lSVeqU6v1sev7Ik3W6aFcFYibQS/ NmRn+3x1Fg9hLcG9JwWvPdyL9B4OavmANF3r X-Received: by 2002:aca:f0b:0:b0:396:11b3:5851 with SMTP id 11-20020aca0f0b000000b0039611b35851mr16382216oip.54.1687354347631; Wed, 21 Jun 2023 06:32:27 -0700 (PDT) Received: from localhost.localdomain (cpc87451-finc19-2-0-cust61.4-2.cable.virginm.net. [82.11.51.62]) by smtp.gmail.com with ESMTPSA id bf24-20020a056808191800b00395f2c84b81sm2114206oib.54.2023.06.21.06.32.24 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 21 Jun 2023 06:32:26 -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 v3 2/3] dt-bindings: serial: amlogic,meson-uart: Add compatible string for T7 Date: Wed, 21 Jun 2023 14:32:14 +0100 Message-ID: <20230621133215.109254-3-tanure@linux.com> X-Mailer: git-send-email 2.41.0 In-Reply-To: <20230621133215.109254-1-tanure@linux.com> References: <20230621133215.109254-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?1769319983395646197?= X-GMAIL-MSGID: =?utf-8?q?1769319983395646197?= |
Series |
Add Amlogic A311D2 and Khadas Vim4 Board Support
|
|
Commit Message
Lucas Tanure
June 21, 2023, 1:32 p.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 | 2 ++
1 file changed, 2 insertions(+)
Comments
On 21/06/2023 15:32, 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 | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml b/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml > index 01ec45b3b406..860ab58d87b0 100644 > --- a/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml > +++ b/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml > @@ -33,6 +33,7 @@ properties: > - amlogic,meson8b-uart > - amlogic,meson-gx-uart > - amlogic,meson-s4-uart > + - amlogic,meson-t7-uart > - const: amlogic,meson-ao-uart > - description: Always-on power domain UART controller on G12A SoCs > items: > @@ -46,6 +47,7 @@ properties: > - amlogic,meson8b-uart > - amlogic,meson-gx-uart > - amlogic,meson-s4-uart > + - amlogic,meson-t7-uart It does not look like you tested the DTS against bindings. Please run `make dtbs_check` (see Documentation/devicetree/bindings/writing-schema.rst or https://www.linaro.org/blog/tips-and-tricks-for-validating-devicetree-sources-with-the-devicetree-schema/ for instructions). Best regards, Krzysztof
Lucas, On Wed, Jun 21, 2023 at 03:53:04PM +0200, Krzysztof Kozlowski wrote: > On 21/06/2023 15:32, 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 | 2 ++ > > 1 file changed, 2 insertions(+) > > > > diff --git a/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml b/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml > > index 01ec45b3b406..860ab58d87b0 100644 > > --- a/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml > > +++ b/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml > > @@ -33,6 +33,7 @@ properties: > > - amlogic,meson8b-uart > > - amlogic,meson-gx-uart > > - amlogic,meson-s4-uart > > + - amlogic,meson-t7-uart > > - const: amlogic,meson-ao-uart > > - description: Always-on power domain UART controller on G12A SoCs > > items: > > @@ -46,6 +47,7 @@ properties: > > - amlogic,meson8b-uart > > - amlogic,meson-gx-uart > > - amlogic,meson-s4-uart > > + - amlogic,meson-t7-uart > > It does not look like you tested the DTS against bindings. Please run > `make dtbs_check` (see > Documentation/devicetree/bindings/writing-schema.rst or > https://www.linaro.org/blog/tips-and-tricks-for-validating-devicetree-sources-with-the-devicetree-schema/ > for instructions). Check back on the previous version, I should've posted an untested version of what you need to add. Cheers, Conor.
On Wed, Jun 21, 2023 at 7:12 PM Conor Dooley <conor@kernel.org> wrote: > > Lucas, > > On Wed, Jun 21, 2023 at 03:53:04PM +0200, Krzysztof Kozlowski wrote: > > On 21/06/2023 15:32, 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 | 2 ++ > > > 1 file changed, 2 insertions(+) > > > > > > diff --git a/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml b/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml > > > index 01ec45b3b406..860ab58d87b0 100644 > > > --- a/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml > > > +++ b/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml > > > @@ -33,6 +33,7 @@ properties: > > > - amlogic,meson8b-uart > > > - amlogic,meson-gx-uart > > > - amlogic,meson-s4-uart > > > + - amlogic,meson-t7-uart > > > - const: amlogic,meson-ao-uart > > > - description: Always-on power domain UART controller on G12A SoCs > > > items: > > > @@ -46,6 +47,7 @@ properties: > > > - amlogic,meson8b-uart > > > - amlogic,meson-gx-uart > > > - amlogic,meson-s4-uart > > > + - amlogic,meson-t7-uart > > > > It does not look like you tested the DTS against bindings. Please run > > `make dtbs_check` (see > > Documentation/devicetree/bindings/writing-schema.rst or > > https://www.linaro.org/blog/tips-and-tricks-for-validating-devicetree-sources-with-the-devicetree-schema/ > > for instructions). > > Check back on the previous version, I should've posted an untested > version of what you need to add. I saw that, but adding a S4 doesn't make sense to me. And you didn't show the entire change, so I can't understand what you want there. > > Cheers, > Conor.
On 22/06/2023 07:32, Lucas Tanure wrote: > On Wed, Jun 21, 2023 at 7:12 PM Conor Dooley <conor@kernel.org> wrote: >> >> Lucas, >> >> On Wed, Jun 21, 2023 at 03:53:04PM +0200, Krzysztof Kozlowski wrote: >>> On 21/06/2023 15:32, 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 | 2 ++ >>>> 1 file changed, 2 insertions(+) >>>> >>>> diff --git a/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml b/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml >>>> index 01ec45b3b406..860ab58d87b0 100644 >>>> --- a/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml >>>> +++ b/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml >>>> @@ -33,6 +33,7 @@ properties: >>>> - amlogic,meson8b-uart >>>> - amlogic,meson-gx-uart >>>> - amlogic,meson-s4-uart >>>> + - amlogic,meson-t7-uart >>>> - const: amlogic,meson-ao-uart >>>> - description: Always-on power domain UART controller on G12A SoCs >>>> items: >>>> @@ -46,6 +47,7 @@ properties: >>>> - amlogic,meson8b-uart >>>> - amlogic,meson-gx-uart >>>> - amlogic,meson-s4-uart >>>> + - amlogic,meson-t7-uart >>> >>> It does not look like you tested the DTS against bindings. Please run >>> `make dtbs_check` (see >>> Documentation/devicetree/bindings/writing-schema.rst or >>> https://www.linaro.org/blog/tips-and-tricks-for-validating-devicetree-sources-with-the-devicetree-schema/ >>> for instructions). >> >> Check back on the previous version, I should've posted an untested >> version of what you need to add. > I saw that, but adding a S4 doesn't make sense to me. And you didn't > show the entire change, so I can't understand what you want there. For sure you need something which does not trigger errors. If you claim adding S4 as fallback does not make sense, then why did you use it? Sending a code which is clearly incorrect does not make sense. Best regards, Krzysztof
On Thu, Jun 22, 2023 at 7:05 AM Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> wrote: > > On 22/06/2023 07:32, Lucas Tanure wrote: > > On Wed, Jun 21, 2023 at 7:12 PM Conor Dooley <conor@kernel.org> wrote: > >> > >> Lucas, > >> > >> On Wed, Jun 21, 2023 at 03:53:04PM +0200, Krzysztof Kozlowski wrote: > >>> On 21/06/2023 15:32, 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 | 2 ++ > >>>> 1 file changed, 2 insertions(+) > >>>> > >>>> diff --git a/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml b/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml > >>>> index 01ec45b3b406..860ab58d87b0 100644 > >>>> --- a/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml > >>>> +++ b/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml > >>>> @@ -33,6 +33,7 @@ properties: > >>>> - amlogic,meson8b-uart > >>>> - amlogic,meson-gx-uart > >>>> - amlogic,meson-s4-uart > >>>> + - amlogic,meson-t7-uart > >>>> - const: amlogic,meson-ao-uart > >>>> - description: Always-on power domain UART controller on G12A SoCs > >>>> items: > >>>> @@ -46,6 +47,7 @@ properties: > >>>> - amlogic,meson8b-uart > >>>> - amlogic,meson-gx-uart > >>>> - amlogic,meson-s4-uart > >>>> + - amlogic,meson-t7-uart > >>> > >>> It does not look like you tested the DTS against bindings. Please run > >>> `make dtbs_check` (see > >>> Documentation/devicetree/bindings/writing-schema.rst or > >>> https://www.linaro.org/blog/tips-and-tricks-for-validating-devicetree-sources-with-the-devicetree-schema/ > >>> for instructions). > >> > >> Check back on the previous version, I should've posted an untested > >> version of what you need to add. > > I saw that, but adding a S4 doesn't make sense to me. And you didn't > > show the entire change, so I can't understand what you want there. > > For sure you need something which does not trigger errors. If you claim > adding S4 as fallback does not make sense, then why did you use it? > Sending a code which is clearly incorrect does not make sense. > Sorry, I think we are talking about different things. It does not make sense to me to add an S4 line in the documentation when it is already there. So I could not understand or make sense of the patch Conor sent in reply to my V2. Krzysztof, I will check again with dtbs_check and re-send. > > Best regards, > Krzysztof >
On Thu, Jun 22, 2023 at 07:43:31AM +0100, Lucas Tanure wrote: > On Thu, Jun 22, 2023 at 7:05 AM Krzysztof Kozlowski > <krzysztof.kozlowski@linaro.org> wrote: > > On 22/06/2023 07:32, Lucas Tanure wrote: > > > On Wed, Jun 21, 2023 at 7:12 PM Conor Dooley <conor@kernel.org> wrote: > > >> On Wed, Jun 21, 2023 at 03:53:04PM +0200, Krzysztof Kozlowski wrote: > > >>> On 21/06/2023 15:32, 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 | 2 ++ > > >>>> 1 file changed, 2 insertions(+) > > >>>> > > >>>> diff --git a/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml b/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml > > >>>> index 01ec45b3b406..860ab58d87b0 100644 > > >>>> --- a/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml > > >>>> +++ b/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml > > >>>> @@ -33,6 +33,7 @@ properties: > > >>>> - amlogic,meson8b-uart > > >>>> - amlogic,meson-gx-uart > > >>>> - amlogic,meson-s4-uart > > >>>> + - amlogic,meson-t7-uart > > >>>> - const: amlogic,meson-ao-uart > > >>>> - description: Always-on power domain UART controller on G12A SoCs > > >>>> items: > > >>>> @@ -46,6 +47,7 @@ properties: > > >>>> - amlogic,meson8b-uart > > >>>> - amlogic,meson-gx-uart > > >>>> - amlogic,meson-s4-uart > > >>>> + - amlogic,meson-t7-uart > > >>> > > >>> It does not look like you tested the DTS against bindings. Please run > > >>> `make dtbs_check` (see > > >>> Documentation/devicetree/bindings/writing-schema.rst or > > >>> https://www.linaro.org/blog/tips-and-tricks-for-validating-devicetree-sources-with-the-devicetree-schema/ > > >>> for instructions). > > >> > > >> Check back on the previous version, I should've posted an untested > > >> version of what you need to add. > > > I saw that, but adding a S4 doesn't make sense to me. And you didn't > > > show the entire change, so I can't understand what you want there. > > > > For sure you need something which does not trigger errors. If you claim > > adding S4 as fallback does not make sense, then why did you use it? > > Sending a code which is clearly incorrect does not make sense. > > > Sorry, I think we are talking about different things. It does not make > sense to me to add an S4 line in the documentation when it is already > there. So I could not understand or make sense of the patch Conor sent > in reply to my V2. That is just how it works. You need to spell out exactly which combinations are permitted. The current entry for s4 says that s4 is only permitted in isolation. Since you are adding "amlogic,meson-t7-uart", "amlogic,meson-s4-uart" you need to explicitly allow that combination. You'll notice if you look at the file that the gx uart appears more than once. Given the g12a was the most recently added compatible, it might make sense to follow the pattern that it had set, given the thing your original patch copied the match data from was the g12a. That change to the dt-binding would look like: diff --git a/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml b/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml index 01ec45b3b406..eae11e87b88a 100644 --- a/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml +++ b/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml @@ -50,6 +50,13 @@ properties: items: - const: amlogic,meson-g12a-uart - const: amlogic,meson-gx-uart + - description: + Everything-Else power domain UART controller on G12A compatible SoCs + items: + - enum: + - amlogic,meson-t7-uart + - const: amlogic,meson-g12a-uart + - const: amlogic,meson-gx-uart reg: maxItems: 1 /I/ don't really care whether you do that, or do the s4 version of it, but following the most recent pattern might make more sense. When I suggested s4, it was because I only looked at the driver patch rather than the code itself. > Krzysztof, I will check again with dtbs_check and re-send. Cheers, Conor.
On Thu, Jun 22, 2023 at 8:12 AM Conor Dooley <conor.dooley@microchip.com> wrote: > > On Thu, Jun 22, 2023 at 07:43:31AM +0100, Lucas Tanure wrote: > > On Thu, Jun 22, 2023 at 7:05 AM Krzysztof Kozlowski > > <krzysztof.kozlowski@linaro.org> wrote: > > > On 22/06/2023 07:32, Lucas Tanure wrote: > > > > On Wed, Jun 21, 2023 at 7:12 PM Conor Dooley <conor@kernel.org> wrote: > > > >> On Wed, Jun 21, 2023 at 03:53:04PM +0200, Krzysztof Kozlowski wrote: > > > >>> On 21/06/2023 15:32, 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 | 2 ++ > > > >>>> 1 file changed, 2 insertions(+) > > > >>>> > > > >>>> diff --git a/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml b/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml > > > >>>> index 01ec45b3b406..860ab58d87b0 100644 > > > >>>> --- a/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml > > > >>>> +++ b/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml > > > >>>> @@ -33,6 +33,7 @@ properties: > > > >>>> - amlogic,meson8b-uart > > > >>>> - amlogic,meson-gx-uart > > > >>>> - amlogic,meson-s4-uart > > > >>>> + - amlogic,meson-t7-uart > > > >>>> - const: amlogic,meson-ao-uart > > > >>>> - description: Always-on power domain UART controller on G12A SoCs > > > >>>> items: > > > >>>> @@ -46,6 +47,7 @@ properties: > > > >>>> - amlogic,meson8b-uart > > > >>>> - amlogic,meson-gx-uart > > > >>>> - amlogic,meson-s4-uart > > > >>>> + - amlogic,meson-t7-uart > > > >>> > > > >>> It does not look like you tested the DTS against bindings. Please run > > > >>> `make dtbs_check` (see > > > >>> Documentation/devicetree/bindings/writing-schema.rst or > > > >>> https://www.linaro.org/blog/tips-and-tricks-for-validating-devicetree-sources-with-the-devicetree-schema/ > > > >>> for instructions). > > > >> > > > >> Check back on the previous version, I should've posted an untested > > > >> version of what you need to add. > > > > I saw that, but adding a S4 doesn't make sense to me. And you didn't > > > > show the entire change, so I can't understand what you want there. > > > > > > For sure you need something which does not trigger errors. If you claim > > > adding S4 as fallback does not make sense, then why did you use it? > > > Sending a code which is clearly incorrect does not make sense. > > > > > Sorry, I think we are talking about different things. It does not make > > sense to me to add an S4 line in the documentation when it is already > > there. So I could not understand or make sense of the patch Conor sent > > in reply to my V2. > > That is just how it works. You need to spell out exactly which > combinations are permitted. The current entry for s4 says that s4 is > only permitted in isolation. > Since you are adding "amlogic,meson-t7-uart", "amlogic,meson-s4-uart" > you need to explicitly allow that combination. You'll notice if you look > at the file that the gx uart appears more than once. > > Given the g12a was the most recently added compatible, it might make > sense to follow the pattern that it had set, given the thing your > original patch copied the match data from was the g12a. That change to > the dt-binding would look like: > diff --git a/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml b/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml > index 01ec45b3b406..eae11e87b88a 100644 > --- a/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml > +++ b/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml > @@ -50,6 +50,13 @@ properties: > items: > - const: amlogic,meson-g12a-uart > - const: amlogic,meson-gx-uart > + - description: > + Everything-Else power domain UART controller on G12A compatible SoCs > + items: > + - enum: > + - amlogic,meson-t7-uart > + - const: amlogic,meson-g12a-uart > + - const: amlogic,meson-gx-uart > > reg: > maxItems: 1 > > /I/ don't really care whether you do that, or do the s4 version of it, > but following the most recent pattern might make more sense. When I > suggested s4, it was because I only looked at the driver patch rather > than the code itself. > > > Krzysztof, I will check again with dtbs_check and re-send. > > Cheers, > Conor. I am struggling to understand this. Everything I try fails the check.
On 22/06/2023 09:36, Lucas Tanure wrote: > On Thu, Jun 22, 2023 at 8:12 AM Conor Dooley <conor.dooley@microchip.com> wrote: >> >> On Thu, Jun 22, 2023 at 07:43:31AM +0100, Lucas Tanure wrote: >>> On Thu, Jun 22, 2023 at 7:05 AM Krzysztof Kozlowski >>> <krzysztof.kozlowski@linaro.org> wrote: >>>> On 22/06/2023 07:32, Lucas Tanure wrote: >>>>> On Wed, Jun 21, 2023 at 7:12 PM Conor Dooley <conor@kernel.org> wrote: >>>>>> On Wed, Jun 21, 2023 at 03:53:04PM +0200, Krzysztof Kozlowski wrote: >>>>>>> On 21/06/2023 15:32, 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 | 2 ++ >>>>>>>> 1 file changed, 2 insertions(+) >>>>>>>> >>>>>>>> diff --git a/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml b/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml >>>>>>>> index 01ec45b3b406..860ab58d87b0 100644 >>>>>>>> --- a/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml >>>>>>>> +++ b/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml >>>>>>>> @@ -33,6 +33,7 @@ properties: >>>>>>>> - amlogic,meson8b-uart >>>>>>>> - amlogic,meson-gx-uart >>>>>>>> - amlogic,meson-s4-uart >>>>>>>> + - amlogic,meson-t7-uart >>>>>>>> - const: amlogic,meson-ao-uart >>>>>>>> - description: Always-on power domain UART controller on G12A SoCs >>>>>>>> items: >>>>>>>> @@ -46,6 +47,7 @@ properties: >>>>>>>> - amlogic,meson8b-uart >>>>>>>> - amlogic,meson-gx-uart >>>>>>>> - amlogic,meson-s4-uart >>>>>>>> + - amlogic,meson-t7-uart >>>>>>> >>>>>>> It does not look like you tested the DTS against bindings. Please run >>>>>>> `make dtbs_check` (see >>>>>>> Documentation/devicetree/bindings/writing-schema.rst or >>>>>>> https://www.linaro.org/blog/tips-and-tricks-for-validating-devicetree-sources-with-the-devicetree-schema/ >>>>>>> for instructions). >>>>>> >>>>>> Check back on the previous version, I should've posted an untested >>>>>> version of what you need to add. >>>>> I saw that, but adding a S4 doesn't make sense to me. And you didn't >>>>> show the entire change, so I can't understand what you want there. >>>> >>>> For sure you need something which does not trigger errors. If you claim >>>> adding S4 as fallback does not make sense, then why did you use it? >>>> Sending a code which is clearly incorrect does not make sense. >>>> >>> Sorry, I think we are talking about different things. It does not make >>> sense to me to add an S4 line in the documentation when it is already >>> there. So I could not understand or make sense of the patch Conor sent >>> in reply to my V2. >> >> That is just how it works. You need to spell out exactly which >> combinations are permitted. The current entry for s4 says that s4 is >> only permitted in isolation. >> Since you are adding "amlogic,meson-t7-uart", "amlogic,meson-s4-uart" >> you need to explicitly allow that combination. You'll notice if you look >> at the file that the gx uart appears more than once. >> >> Given the g12a was the most recently added compatible, it might make >> sense to follow the pattern that it had set, given the thing your >> original patch copied the match data from was the g12a. That change to >> the dt-binding would look like: >> diff --git a/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml b/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml >> index 01ec45b3b406..eae11e87b88a 100644 >> --- a/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml >> +++ b/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml >> @@ -50,6 +50,13 @@ properties: >> items: >> - const: amlogic,meson-g12a-uart >> - const: amlogic,meson-gx-uart >> + - description: >> + Everything-Else power domain UART controller on G12A compatible SoCs >> + items: >> + - enum: >> + - amlogic,meson-t7-uart >> + - const: amlogic,meson-g12a-uart >> + - const: amlogic,meson-gx-uart >> >> reg: >> maxItems: 1 >> >> /I/ don't really care whether you do that, or do the s4 version of it, >> but following the most recent pattern might make more sense. When I >> suggested s4, it was because I only looked at the driver patch rather >> than the code itself. >> >>> Krzysztof, I will check again with dtbs_check and re-send. >> >> Cheers, >> Conor. > I am struggling to understand this. Everything I try fails the check. I just applied Conor's change on top of v6.4-rc1 and ran: make dt_binding_check DT_SCHEMA_FILES=Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml and the check was successful. Neil
On Thu, Jun 22, 2023 at 9:13 AM Neil Armstrong <neil.armstrong@linaro.org> wrote: > > On 22/06/2023 09:36, Lucas Tanure wrote: > > On Thu, Jun 22, 2023 at 8:12 AM Conor Dooley <conor.dooley@microchip.com> wrote: > >> > >> On Thu, Jun 22, 2023 at 07:43:31AM +0100, Lucas Tanure wrote: > >>> On Thu, Jun 22, 2023 at 7:05 AM Krzysztof Kozlowski > >>> <krzysztof.kozlowski@linaro.org> wrote: > >>>> On 22/06/2023 07:32, Lucas Tanure wrote: > >>>>> On Wed, Jun 21, 2023 at 7:12 PM Conor Dooley <conor@kernel.org> wrote: > >>>>>> On Wed, Jun 21, 2023 at 03:53:04PM +0200, Krzysztof Kozlowski wrote: > >>>>>>> On 21/06/2023 15:32, 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 | 2 ++ > >>>>>>>> 1 file changed, 2 insertions(+) > >>>>>>>> > >>>>>>>> diff --git a/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml b/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml > >>>>>>>> index 01ec45b3b406..860ab58d87b0 100644 > >>>>>>>> --- a/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml > >>>>>>>> +++ b/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml > >>>>>>>> @@ -33,6 +33,7 @@ properties: > >>>>>>>> - amlogic,meson8b-uart > >>>>>>>> - amlogic,meson-gx-uart > >>>>>>>> - amlogic,meson-s4-uart > >>>>>>>> + - amlogic,meson-t7-uart > >>>>>>>> - const: amlogic,meson-ao-uart > >>>>>>>> - description: Always-on power domain UART controller on G12A SoCs > >>>>>>>> items: > >>>>>>>> @@ -46,6 +47,7 @@ properties: > >>>>>>>> - amlogic,meson8b-uart > >>>>>>>> - amlogic,meson-gx-uart > >>>>>>>> - amlogic,meson-s4-uart > >>>>>>>> + - amlogic,meson-t7-uart > >>>>>>> > >>>>>>> It does not look like you tested the DTS against bindings. Please run > >>>>>>> `make dtbs_check` (see > >>>>>>> Documentation/devicetree/bindings/writing-schema.rst or > >>>>>>> https://www.linaro.org/blog/tips-and-tricks-for-validating-devicetree-sources-with-the-devicetree-schema/ > >>>>>>> for instructions). > >>>>>> > >>>>>> Check back on the previous version, I should've posted an untested > >>>>>> version of what you need to add. > >>>>> I saw that, but adding a S4 doesn't make sense to me. And you didn't > >>>>> show the entire change, so I can't understand what you want there. > >>>> > >>>> For sure you need something which does not trigger errors. If you claim > >>>> adding S4 as fallback does not make sense, then why did you use it? > >>>> Sending a code which is clearly incorrect does not make sense. > >>>> > >>> Sorry, I think we are talking about different things. It does not make > >>> sense to me to add an S4 line in the documentation when it is already > >>> there. So I could not understand or make sense of the patch Conor sent > >>> in reply to my V2. > >> > >> That is just how it works. You need to spell out exactly which > >> combinations are permitted. The current entry for s4 says that s4 is > >> only permitted in isolation. > >> Since you are adding "amlogic,meson-t7-uart", "amlogic,meson-s4-uart" > >> you need to explicitly allow that combination. You'll notice if you look > >> at the file that the gx uart appears more than once. > >> > >> Given the g12a was the most recently added compatible, it might make > >> sense to follow the pattern that it had set, given the thing your > >> original patch copied the match data from was the g12a. That change to > >> the dt-binding would look like: > >> diff --git a/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml b/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml > >> index 01ec45b3b406..eae11e87b88a 100644 > >> --- a/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml > >> +++ b/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml > >> @@ -50,6 +50,13 @@ properties: > >> items: > >> - const: amlogic,meson-g12a-uart > >> - const: amlogic,meson-gx-uart > >> + - description: > >> + Everything-Else power domain UART controller on G12A compatible SoCs > >> + items: > >> + - enum: > >> + - amlogic,meson-t7-uart > >> + - const: amlogic,meson-g12a-uart > >> + - const: amlogic,meson-gx-uart > >> > >> reg: > >> maxItems: 1 > >> > >> /I/ don't really care whether you do that, or do the s4 version of it, > >> but following the most recent pattern might make more sense. When I > >> suggested s4, it was because I only looked at the driver patch rather > >> than the code itself. > >> > >>> Krzysztof, I will check again with dtbs_check and re-send. > >> > >> Cheers, > >> Conor. > > I am struggling to understand this. Everything I try fails the check. > > I just applied Conor's change on top of v6.4-rc1 and ran: > make dt_binding_check DT_SCHEMA_FILES=Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml > > and the check was successful. > > Neil > > I am sending v4 in a few minutes
diff --git a/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml b/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml index 01ec45b3b406..860ab58d87b0 100644 --- a/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml +++ b/Documentation/devicetree/bindings/serial/amlogic,meson-uart.yaml @@ -33,6 +33,7 @@ properties: - amlogic,meson8b-uart - amlogic,meson-gx-uart - amlogic,meson-s4-uart + - amlogic,meson-t7-uart - const: amlogic,meson-ao-uart - description: Always-on power domain UART controller on G12A SoCs items: @@ -46,6 +47,7 @@ properties: - amlogic,meson8b-uart - amlogic,meson-gx-uart - amlogic,meson-s4-uart + - amlogic,meson-t7-uart - description: Everything-Else power domain UART controller on G12A SoCs items: - const: amlogic,meson-g12a-uart