Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 45AA3C636D3 for ; Mon, 30 Jan 2023 22:43:09 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230158AbjA3WnH (ORCPT ); Mon, 30 Jan 2023 17:43:07 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46954 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229460AbjA3WnF (ORCPT ); Mon, 30 Jan 2023 17:43:05 -0500 Received: from mail-yw1-x1135.google.com (mail-yw1-x1135.google.com [IPv6:2607:f8b0:4864:20::1135]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 286641814B for ; Mon, 30 Jan 2023 14:43:03 -0800 (PST) Received: by mail-yw1-x1135.google.com with SMTP id 00721157ae682-50660e2d2ffso180832207b3.1 for ; Mon, 30 Jan 2023 14:43:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=+TZHpce+LkRMQa6vx6q9obcgDlv0XoFb3aljOsKv7qU=; b=nCBrIiE+L+vdLXic+BhlJTEfwEv/ysg8qF3ePyjPsY/A6pPFUyJ9yxWfviS5IS9XZ+ aTkrqx4WuQWd2ry/CmUYytg0ONmjJ++XzlyAcGDLyhrZ4/IX03EskCTili/5UQq5yKge +e1rwxjmS0vI2LeI41+8f4VGz+I/dUip0S2eGn72UYX+dBh2W8CPEuyvYqHBwUzQTY52 5vUM6PPZirJQEM/wFGgVbRt8dqUJz0ZaVONsNu44LnLGVX5dLOGLew5RenS7kd33ruoM AeG1hFJb4M2UAk+s92c6xRoPBpxkWpcN0CqUVNQ0xsATgHZATATevhE+7nH+bY+9BJXI PhRw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=+TZHpce+LkRMQa6vx6q9obcgDlv0XoFb3aljOsKv7qU=; b=qiaTlpC1ynAcLJAdVsiaL3iyRjxlRdx0Scqkg5ct5iBndH8OzbjmAp31xM1M0mmJ+o 2awLksQSEV8I7yCqktqkCo3GRp6SeD7pIKL9rLEb483qj5bviYzEP6KDpUJ0Q96m2zzn JeWioJM02Q/q6APlNDbqRvL27gHB1rXuedQ3SsuRlWPIN4sLLHVBohDaYocrFbEmBMPE i31Ud4T1caZWtw4A3WQMYD0giGJydhzaVZ3seTgtuOLOskzH4jP6izPFDVkDjEHDHszZ jmwSFPTVFgdA0v/yfRg9c9f99DnIrVu4olXBJcv4pYEi/j6Ewo7kaqcEXjem7CdEF9ST Spxg== X-Gm-Message-State: AFqh2koxf+qLHUx78cVVsZCYdfpNSJJgkeC+tUGzEh4znoHaygzzYFFV a5Ij3p6AYgSHIV3PAYQVwX8T1vSfQjU7Zxim6pxf5Q== X-Google-Smtp-Source: AMrXdXtQIx/gOYQWR7Z9y8qC4zSuzlnGWFfiiT/LekYqnnNUbvQG32KG8P3YQVm2xu2If9pxmW9DcUUds+3TfNO/91s= X-Received: by 2002:a05:690c:39b:b0:4f3:8d0e:edce with SMTP id bh27-20020a05690c039b00b004f38d0eedcemr4580998ywb.185.1675118582401; Mon, 30 Jan 2023 14:43:02 -0800 (PST) MIME-Version: 1.0 References: <20230127093217.60818-1-krzysztof.kozlowski@linaro.org> <20230127093217.60818-4-krzysztof.kozlowski@linaro.org> <755d4a78-0b23-a381-c422-d12b0063f06f@linaro.org> In-Reply-To: <755d4a78-0b23-a381-c422-d12b0063f06f@linaro.org> From: Linus Walleij Date: Mon, 30 Jan 2023 23:42:51 +0100 Message-ID: Subject: Re: [PATCH v2 3/3] dt-bindings: serial: restrict possible child node names To: Krzysztof Kozlowski Cc: Damien Le Moal , Rob Herring , Krzysztof Kozlowski , Linus Walleij , Imre Kaloz , Krzysztof Halasa , Miquel Raynal , Richard Weinberger , Vignesh Raghavendra , Greg Kroah-Hartman , Wim Van Sebroeck , Guenter Roeck , Marek Vasut , Lubomir Rintel , - , Marc Zyngier , linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mtd@lists.infradead.org, linux-serial@vger.kernel.org, linux-watchdog@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Jan 29, 2023 at 4:48 PM Krzysztof Kozlowski wrote: > On 27/01/2023 14:29, Linus Walleij wrote: > > On Fri, Jan 27, 2023 at 10:32 AM Krzysztof Kozlowski > > wrote: > > > >> The re-usable serial.yaml schema matches every property with ".*" > >> pattern, thus any other schema referencing it will not report unknown > >> (unevaluated) properties. This hides several wrong properties. It is > >> a limitation of dtschema, thus provide a simple workaround: expect > >> children to be only of few names matching upstream usage (Bluetooth, > >> GNSS, GPS and MCU). > >> > >> Signed-off-by: Krzysztof Kozlowski > > > > Fair enough, > > Acked-by: Linus Walleij > > > > However I think V.35 WAN devices (high speed serial network links) > > should actually be using this? They are just some fancy serial port > > after all. Cf > > Documentation/devicetree/bindings/net/intel,ixp4xx-hss.yaml > > > > No big deal I guess since they are mostly an anarchronism and not > > on the table right now. > > intel,ixp4xx-hss is not part of the expansion bus node. True, my point is that WAN V.35 devices in general should be, so that the pattern properties should include wan. But we can add it later if a user appears. Yours, Linus Walleij