Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp3040299pxb; Mon, 18 Oct 2021 07:07:34 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzISque9wvlibh408gcbeMaxw5jQwXF5ACsJXa6UDeQIYye+ijXZC7Dfg+b0Dmb2TvyMXN6 X-Received: by 2002:a62:1d14:0:b0:44d:3b0b:d027 with SMTP id d20-20020a621d14000000b0044d3b0bd027mr28840051pfd.60.1634566054356; Mon, 18 Oct 2021 07:07:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1634566054; cv=none; d=google.com; s=arc-20160816; b=Gte3gY3PU0L81St+/vCM3BYRHqsSPC2tKRjmzjTudpxlFvm0wAt/tQo/+lvkmwTqdI G0aSW2/HEO4k++1JrwpgX2Qx9W7IfP/PXOxbiGIDgH/54nBZG6dgMMhGoymJqG/8mJrX EjUGBZ5d30Iv3Y7JUupQkNPRi1mixMVlwi7G5m7IQwigBmvrPN8p1889P58tMiOLt/X9 f4v6mJqQT8mUHO6dxFciXVCMQf/IQqh3+/9o7rxJDm3pWiSaC33toQqBSvaKmNAIWlpN w7F8E+J/ODM0jnuJZQlCaLwGfez9kqrX78/fzxLkOH2tkVAB1zj3sARCHDquR4bECiSq gu2w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=zfHUTqiEZNcwoTUEA15pyh36vmYEdz3Eki/UQj7YGCI=; b=IovGR04alEVLgqHdENbTfwvvSdH/V8kkvtGggev6LNGccGs6D5N9PGmYiESpNCBeF6 JiaW6A/9kCadd9KiuqaYYvBFNgosLiwWuQuDy43Wwz6MfBpWTsz8CTcWinVeVaCCd0LQ 74AODT6xd6u6om8A/GgP52ZyTgFt72XwaI7e2BJCrLbLfZFnL7SFEQ6hGlqBiPDWVG/J FbYiLcEhlNzhWxdmzTLrETSGTBV4izkaQxV5QTKcj/nVmrQv8HVvra7A98RULgLfMKsH u7iKY0t7GUkBEI+ieaa2ZXMpilmE1vkHaK8JYHQf/vpQru/S+1Uz2M3Hnn3HE76A7Y67 5Tkg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=gicUw8LV; 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=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id v12si23400677pfu.224.2021.10.18.07.07.09; Mon, 18 Oct 2021 07:07:34 -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; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=gicUw8LV; 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=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233452AbhJROFk (ORCPT + 99 others); Mon, 18 Oct 2021 10:05:40 -0400 Received: from mail.kernel.org ([198.145.29.99]:40798 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234072AbhJROBz (ORCPT ); Mon, 18 Oct 2021 10:01:55 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 12FEE61A7E; Mon, 18 Oct 2021 13:42:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1634564571; bh=zfHUTqiEZNcwoTUEA15pyh36vmYEdz3Eki/UQj7YGCI=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=gicUw8LVEDCj9LJBhuB3HeBeyCGAZy5KwtvZM4oxTFEBeAvRPRrxbcLh1/AXi6hoG l/HhOTaHtQFVX+oGrCq4/XMSFdmpFrLveJRawy1qeiMWyzBgdj6RmBNkZqdE42jTnW kLv5oO+8/c3lDDGaqMvE2y73xeuZV4FCLcGmC3Kl+0n4VPqt/Xz0df5FSaXJXk0eXX R6gNc4Lc6LkFMr6vqcL+7KsWvr8SJkYdwymFFc0p9XGlGx7WK4Q9Wy7XD8hDPqyIuP kM9Ev3+rGT9lQYtQipEpDa0ieEr15tnvk12AUdQCmpdH0UG880E1j6PTmwCyzdWpq6 k38ta733bQ/HQ== Received: by mail-ed1-f42.google.com with SMTP id r18so71544804edv.12; Mon, 18 Oct 2021 06:42:50 -0700 (PDT) X-Gm-Message-State: AOAM531Oi3J/Gxwmnu51qQ8fXZ1PqBAbwc/QkwE2jni+aldXWfbixDT5 AAJMdUzAB2MvMn5WIcfx/RYY4ZCZKWw0no8wdQ== X-Received: by 2002:a05:6402:1778:: with SMTP id da24mr43699821edb.318.1634564462043; Mon, 18 Oct 2021 06:41:02 -0700 (PDT) MIME-Version: 1.0 References: <20211013222313.3767605-1-vladimir.oltean@nxp.com> <20211013222313.3767605-6-vladimir.oltean@nxp.com> <1634221864.138006.3295871.nullmailer@robh.at.kernel.org> <20211015125527.28445238@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> <20211015224825.wyjg63uzyuaguewx@skbuf> In-Reply-To: <20211015224825.wyjg63uzyuaguewx@skbuf> From: Rob Herring Date: Mon, 18 Oct 2021 08:40:50 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH net-next 5/6] dt-bindings: net: dsa: sja1105: add {rx,tx}-internal-delay-ps To: Vladimir Oltean Cc: Jakub Kicinski , Prasanna Vengateshan , "devicetree@vger.kernel.org" , Russell King , Ansuel Smith , Heiner Kallweit , "linux-arm-kernel@lists.infradead.org" , Florian Fainelli , "netdev@vger.kernel.org" , Vivien Didelot , Andrew Lunn , Shawn Guo , Vladimir Oltean , "David S . Miller" , =?UTF-8?Q?Alvin_=C5=A0ipraga?= , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Oct 15, 2021 at 5:48 PM Vladimir Oltean wrote: > > On Fri, Oct 15, 2021 at 12:55:27PM -0700, Jakub Kicinski wrote: > > On Thu, 14 Oct 2021 09:31:04 -0500 Rob Herring wrote: > > > On Thu, 14 Oct 2021 01:23:12 +0300, Vladimir Oltean wrote: > > > > Add a schema validator to nxp,sja1105.yaml and to dsa.yaml for explicit > > > > MAC-level RGMII delays. These properties must be per port and must be > > > > present only for a phy-mode that represents RGMII. > > > > > > > > We tell dsa.yaml that these port properties might be present, we also > > > > define their valid values for SJA1105. We create a common definition for > > > > the RX and TX valid range, since it's quite a mouthful. > > > > > > > > We also modify the example to include the explicit RGMII delay properties. > > > > On the fixed-link ports (in the example, port 4), having these explicit > > > > delays is actually mandatory, since with the new behavior, the driver > > > > shouts that it is interpreting what delays to apply based on phy-mode. > > > > > > > > Signed-off-by: Vladimir Oltean > > > > > > My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check' > > > on your patch (DT_CHECKER_FLAGS is new in v5.13): > > > > FWIW I dropped the set from pw based on Rob's report, I see a mention > > of possible issues with fsl-lx2160a-bluebox3.dts, but it's not clear > > to me which DT is disagreeing with the schema.. or is the schema itself > > not 100? > > I am only saying that I am introducing a new DT binding scheme and > warning all users of the old one. That's also why I am updating the > device trees, to silence the newly introduced warnings. I would like > this series to go through net-next, but fsl-lx2160a-bluebox3.dts isn't > in net-next. .dts changes should go in via the sub-arch's tree, not a subsystem tree. Rob