From mboxrd@z Thu Jan 1 00:00:00 1970 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 0691AC19F29 for ; Thu, 28 Jul 2022 16:32:01 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232022AbiG1Qb7 (ORCPT ); Thu, 28 Jul 2022 12:31:59 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45658 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233473AbiG1Qbn (ORCPT ); Thu, 28 Jul 2022 12:31:43 -0400 Received: from mail-lf1-x136.google.com (mail-lf1-x136.google.com [IPv6:2a00:1450:4864:20::136]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BD9171901E for ; Thu, 28 Jul 2022 09:31:36 -0700 (PDT) Received: by mail-lf1-x136.google.com with SMTP id m12so3613429lfj.4 for ; Thu, 28 Jul 2022 09:31:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=message-id:date:mime-version:user-agent:subject:content-language:to :cc:references:from:in-reply-to:content-transfer-encoding; bh=0Qrp1aC7ii4l+FdZJbsIzM1JU8ekTQaZIFWORS0YhME=; b=yOYlyKgvos/05p6jY1ecXbckNmfg3Mp8u9eEL/FG5WoJQlIVSW4Wt15soFBSdg3DbK MZKnX4UD8Mrs67cU8Lh7LWrVM7dFQJROTOP9oHyGKP3Q9U53B+VMZAKpJzu1rYwfKjqI cuOfm0wia1rOHbe/CP6zk9qP1t6tcSsnPs4COz/C0QMizLpFO5kJpces4fvL1wXgQktW gnlRfSt4JWCEjGkra3Xd+enNrD1CDHOSwCKFpUIz6E7X8TGhlY4fT6wgX8esaFHClmcV /4TMxl2WogYqSfHjIYuzIS8IpJF1HtlLixOkRKWIAtuGxYunJODuyk6XquNYDzZeqpcP cQSQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=0Qrp1aC7ii4l+FdZJbsIzM1JU8ekTQaZIFWORS0YhME=; b=ihNKz8PUzjgTdGVNLggEXO0yFBnsbvE/CDHhRFCiwpuv78FmS1h6mtPLWiY49BX3XE p4754shdLr/hKTmZUOF1lrX38ryki/2Ss9XZ1+1n7oM/eiNpEocBEArXVr3usK41ewJm aooKeXVCeD6M5owZy6cK6J5V9NCHEckzg2uD5eKnWEQw7ZpYz4F2buEB1HsNUHD5qxIP sh66RVH6TY6e6ZqUJhfIx4fb/fwCJl68bTnuzEwWghr/XGk81t2M0cSmQ2bdLNqEGS2G weuvvmv0XMNmkaJanOxz6NbBaivWCYf770fpX9G5fpnBBgAe9hB5Kq/tC39Nfdo+lmBN JBLQ== X-Gm-Message-State: AJIora/4su+EIIhxaYs6irc7kEkwFwJijwI/lscg0E6MahWJbs0IXtPE zP1ikajncMyPPvLmDiF05JBwrA== X-Google-Smtp-Source: AGRyM1vQbNnKAzNUxSU0neBQyxzQa6mDwQFmjvcMDN7uctQh6GF1gf3S5rEkvDVrNvEcqXGUIUiupw== X-Received: by 2002:a19:e007:0:b0:481:c74:37b7 with SMTP id x7-20020a19e007000000b004810c7437b7mr10138465lfg.439.1659025894853; Thu, 28 Jul 2022 09:31:34 -0700 (PDT) Received: from [192.168.3.197] (78-26-46-173.network.trollfjord.no. [78.26.46.173]) by smtp.gmail.com with ESMTPSA id m8-20020a195208000000b004894b6df9e2sm264175lfb.114.2022.07.28.09.31.33 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 28 Jul 2022 09:31:34 -0700 (PDT) Message-ID: Date: Thu, 28 Jul 2022 18:31:32 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.12.0 Subject: Re: [PATCH 1/2] dt-bindings: nfc: use spi-peripheral-props.yaml Content-Language: en-US To: Rob Herring Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org, =?UTF-8?B?SsOpcsO0bWUgUG91aWxsZXI=?= , Jakub Kicinski , Paolo Abeni , Ajay Singh , linux-wireless@vger.kernel.org, devicetree@vger.kernel.org, "David S. Miller" , Rob Herring , Tony Lindgren , Kalle Valo , Eric Dumazet , Adham Abozaeid , Mark Greer References: <20220727164130.385411-1-krzysztof.kozlowski@linaro.org> <20220728151802.GA900320-robh@kernel.org> From: Krzysztof Kozlowski In-Reply-To: <20220728151802.GA900320-robh@kernel.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On 28/07/2022 17:18, Rob Herring wrote: > On Wed, 27 Jul 2022 18:41:29 +0200, Krzysztof Kozlowski wrote: >> Instead of listing directly properties typical for SPI peripherals, >> reference the spi-peripheral-props.yaml schema. This allows using all >> properties typical for SPI-connected devices, even these which device >> bindings author did not tried yet. >> >> Remove the spi-* properties which now come via spi-peripheral-props.yaml >> schema, except for the cases when device schema adds some constraints >> like maximum frequency. >> >> While changing additionalProperties->unevaluatedProperties, put it in >> typical place, just before example DTS. >> >> Signed-off-by: Krzysztof Kozlowski >> >> --- >> >> Technically, this depends on [1] merged to SPI tree, if we want to >> preserve existing behavior of not allowing SPI CPHA and CPOL in each of >> schemas in this patch. >> >> If this patch comes independently via different tree, the SPI CPHA and >> CPOL will be allowed for brief period of time, before [1] is merged. >> This will not have negative impact, just DT schema checks will be >> loosened for that period. > > I don't think these need to go via the same tree. Yeah, I wanted to express it that almost no impact is expected if it goes independently. I could be more explicit here. Best regards, Krzysztof