From: Adam Ford <aford173@gmail.com>
To: netdev@vger.kernel.org
Cc: aford@beaconembedded.com, Adam Ford <aford173@gmail.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Rob Herring <robh@kernel.org>,
Sergei Shtylyov <sergei.shtylyov@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH V3 1/5] dt-bindings: net: renesas,etheravb: Add additional clocks
Date: Wed, 24 Feb 2021 05:51:41 -0600 [thread overview]
Message-ID: <20210224115146.9131-1-aford173@gmail.com> (raw)
The AVB driver assumes there is an external crystal, but it could
be clocked by other means. In order to enable a programmable
clock, it needs to be added to the clocks list and enabled in the
driver. Since there currently only one clock, there is no
clock-names list either.
Update bindings to add the additional optional clock, and explicitly
name both of them.
Signed-off-by: Adam Ford <aford173@gmail.com>
Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
Acked-by: Rob Herring <robh@kernel.org>
---
V3: No Change
V2: No Change
diff --git a/Documentation/devicetree/bindings/net/renesas,etheravb.yaml b/Documentation/devicetree/bindings/net/renesas,etheravb.yaml
index de9dd574a2f9..7b32363ad8b4 100644
--- a/Documentation/devicetree/bindings/net/renesas,etheravb.yaml
+++ b/Documentation/devicetree/bindings/net/renesas,etheravb.yaml
@@ -49,7 +49,16 @@ properties:
interrupt-names: true
clocks:
- maxItems: 1
+ minItems: 1
+ maxItems: 2
+ items:
+ - description: AVB functional clock
+ - description: Optional TXC reference clock
+
+ clock-names:
+ items:
+ - const: fck
+ - const: refclk
iommus:
maxItems: 1
--
2.25.1
next reply other threads:[~2021-02-24 11:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 11:51 Adam Ford [this message]
2021-02-24 11:51 ` [PATCH V3 2/5] ARM: dts: renesas: Add fck to etheravb-rcar-gen2 clock-names list Adam Ford
2021-02-24 13:45 ` Andrew Lunn
2021-02-25 7:51 ` Geert Uytterhoeven
2021-02-24 11:51 ` [PATCH V3 3/5] arm64: dts: renesas: Add fck to etheravb-rcar-gen3 " Adam Ford
2021-02-24 13:46 ` Andrew Lunn
2021-04-19 9:38 ` Geert Uytterhoeven
2021-02-24 11:51 ` [PATCH V3 4/5] net: ethernet: ravb: Enable optional refclk Adam Ford
2021-02-24 13:47 ` Andrew Lunn
2021-03-04 8:08 ` Geert Uytterhoeven
2021-03-29 12:45 ` Adam Ford
2021-03-29 13:08 ` Geert Uytterhoeven
2021-02-24 11:51 ` [PATCH V3 5/5] arm64: dts: renesas: beacon kits: Setup AVB refclk Adam Ford
2021-03-04 8:03 ` Geert Uytterhoeven
2021-03-18 12:44 ` Adam Ford
2021-03-18 13:08 ` Geert Uytterhoeven
2021-03-19 8:40 ` Sergei Shtylyov
2021-04-17 13:54 ` Adam Ford
2021-04-19 9:39 ` Geert Uytterhoeven
2021-03-18 20:18 ` [PATCH V3 1/5] dt-bindings: net: renesas,etheravb: Add additional clocks Sergei Shtylyov
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=20210224115146.9131-1-aford173@gmail.com \
--to=aford173@gmail.com \
--cc=aford@beaconembedded.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sergei.shtylyov@gmail.com \
/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).