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 38963C4332F for ; Wed, 30 Mar 2022 16:44:50 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1348966AbiC3Qqd (ORCPT ); Wed, 30 Mar 2022 12:46:33 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38318 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1348975AbiC3Qqc (ORCPT ); Wed, 30 Mar 2022 12:46:32 -0400 Received: from mail-ej1-x635.google.com (mail-ej1-x635.google.com [IPv6:2a00:1450:4864:20::635]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B458B1E5200 for ; Wed, 30 Mar 2022 09:44:45 -0700 (PDT) Received: by mail-ej1-x635.google.com with SMTP id c10so24290046ejs.13 for ; Wed, 30 Mar 2022 09:44:45 -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=yHBfMl6iM7258r0O2Jco9pafktxB1pt6+1WqgBzk+vg=; b=KLyLdtoSrb3fmaMJiq0IipYP8LMdhy6mILKXf36PQRWK5lDC7m6Tb2FhMsjzrPHtJt UvI8C8XDTcE5qrh1h1bncRLDNRnYOso8de8xGpuuhnsXE13LDOZjgPaVJJNQj84fiGXI 5dQFIk8CLxRRJjk7ngUuZPx13i9vpUcixttW3CzcnvlwrLZRS2SLTXTSfpZKWJ8Cw4vL +9uubnbTntHsZIBPRPNpMmsNbguw6kcswbWpc6KNZ9UmrBXIBJDMgiZFiMWnEgQy5Qx/ pReB7fiyXYmWm6yGOoy1lCCtUJ79qTZd4pwWOL6C0RR29CiKxOYy5Y+Ye3AKycvTbBIN iOJA== 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=yHBfMl6iM7258r0O2Jco9pafktxB1pt6+1WqgBzk+vg=; b=SoAwito0OLHxeHmQanXWchHyUhN9QICHbPvuBoQoC2tcKH/EyWP8RTSnB/zL3lesNS oYlvuBHewC4QmneBRfgDN3z5lAsUvIZd+E6JEpCSKwEk0ruDveU7Q3r6q1ADtBDsiHKt 5aCBrT3pVl6XrAMW8wWxQLiy3pdJyQAFMimmDjhOo/gwTr/1Il0aadq1WUQEAhUnz8B+ PQVeRiS/yU00RZnqyi3/AhwzIUUJfj+GTNwkvk0opdGYgqhv5xk14345CsQ/4pog1TjZ ZTVOA49HomaEIoBCq4cjKjQGBgLf+ojjAQA1gRomzGQLQjXok/Hd0EmHw/wZCM5FFiky Cz4A== X-Gm-Message-State: AOAM532kKoE86ixFeVNSxtlIjUzYxNq0e6LfrgxBNilaJY1cuAMiCWFg PWPfBvGQKIhMnpoImgndIu8Bjg== X-Google-Smtp-Source: ABdhPJywV3uexnsqSnhWXlwW2C6kDd0vY5WPPQ+rsQ3XzeorjnRj1l22TFs3ki+OTaR+h4z7XUNuKw== X-Received: by 2002:a17:906:32d0:b0:6ce:e1cf:3f2e with SMTP id k16-20020a17090632d000b006cee1cf3f2emr449876ejk.214.1648658683796; Wed, 30 Mar 2022 09:44:43 -0700 (PDT) Received: from [192.168.0.164] (xdsl-188-155-201-27.adslplus.ch. [188.155.201.27]) by smtp.gmail.com with ESMTPSA id l2-20020a1709060cc200b006d3d91e88c7sm8492441ejh.214.2022.03.30.09.44.42 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 30 Mar 2022 09:44:43 -0700 (PDT) Message-ID: <064271f4-d775-279c-0aa2-c9e23194bc61@linaro.org> Date: Wed, 30 Mar 2022 18:44:42 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0 Subject: Re: [PATCH net-next] dt-bindings: net: convert sff,sfp to dtschema Content-Language: en-US To: "Russell King (Oracle)" , Krzysztof Kozlowski Cc: Ioana Ciornei , "davem@davemloft.net" , "kuba@kernel.org" , "netdev@vger.kernel.org" , "robh+dt@kernel.org" , "devicetree@vger.kernel.org" References: <20220315123315.233963-1-ioana.ciornei@nxp.com> <6f4f2e6f-3aee-3424-43bc-c60ef7c0218c@canonical.com> <20220315190733.lal7c2xkaez6fz2v@skbuf> <20220316101854.imevzoqk6oashrgg@skbuf> From: Krzysztof Kozlowski In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On 30/03/2022 17:54, Russell King (Oracle) wrote: >> >> These are different. This is an example how to model the input clock to >> the device being described in the bindings. This is not an example how >> to use the clock provider, like you created here. The input clock >> sometimes is defined in Exynos clock controller, sometimes outside. The >> example there shows the second case - when it has to come outside. It's >> not showing the usage of clocks provided by this device, but I agree >> that it also might be trivial and obvious. If you think it is obvious, >> feel free to comment/send a patch. > > Why is whether something is an input or output relevant? One can quite > rightly argue that SFPs are both input and output. :) > I don't mind removing that example. Input - in the case of these bindings - is quite specific. Output is opposite, not specific and can vary, you can enable/disable, change frequency. Discussion was two weeks ago, so all emails will bounce. :) Best regards, Krzysztof