From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>,
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Cc: Ioana Ciornei <ioana.ciornei@nxp.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"kuba@kernel.org" <kuba@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH net-next] dt-bindings: net: convert sff,sfp to dtschema
Date: Wed, 30 Mar 2022 18:44:42 +0200 [thread overview]
Message-ID: <064271f4-d775-279c-0aa2-c9e23194bc61@linaro.org> (raw)
In-Reply-To: <YkR9NKec1YR7VGOy@shell.armlinux.org.uk>
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
next prev parent reply other threads:[~2022-03-30 16:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 12:33 [PATCH net-next] dt-bindings: net: convert sff,sfp to dtschema Ioana Ciornei
2022-03-15 18:21 ` Krzysztof Kozlowski
2022-03-15 19:07 ` Ioana Ciornei
2022-03-16 8:23 ` Krzysztof Kozlowski
2022-03-16 10:18 ` Ioana Ciornei
2022-03-16 12:04 ` Krzysztof Kozlowski
2022-03-30 15:54 ` Russell King (Oracle)
2022-03-30 15:56 ` Russell King (Oracle)
2022-03-30 16:44 ` Krzysztof Kozlowski [this message]
2022-03-30 15:52 ` Russell King (Oracle)
2022-03-30 16:09 ` Rob Herring
2022-03-30 16:35 ` Russell King (Oracle)
2022-03-30 15:40 ` Russell King (Oracle)
2022-03-30 16:51 ` Krzysztof Kozlowski
2022-03-30 16:59 ` Krzysztof Kozlowski
2022-03-31 20:45 ` Krzysztof Kozlowski
2022-06-10 22:31 ` Rob Herring
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=064271f4-d775-279c-0aa2-c9e23194bc61@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=ioana.ciornei@nxp.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).