From: Rob Herring <robh@kernel.org>
To: Michael Grzeschik <m.grzeschik@pengutronix.de>
Cc: Tristram.Ha@microchip.com, kernel@pengutronix.de,
UNGLinuxDriver@microchip.com, netdev@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [RFC 3/3] dt-bindings: net: dsa: document additional Microchip KSZ8863 family switches
Date: Thu, 13 Jun 2019 14:09:35 -0600 [thread overview]
Message-ID: <20190613200935.GA16851@bogus> (raw)
In-Reply-To: <20190508211330.19328-4-m.grzeschik@pengutronix.de>
On Wed, May 08, 2019 at 11:13:30PM +0200, Michael Grzeschik wrote:
> Document additional Microchip KSZ8863 family switches.
>
> Show how KSZ8863 switch should be configured as the host port is port 3.
>
> Cc: devicetree@vger.kernel.org
> Signed-off-by: Michael Grzeschik <m.grzeschik@pengutronix.de>
> ---
> .../devicetree/bindings/net/dsa/ksz.txt | 44 +++++++++++++++++++
> 1 file changed, 44 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/net/dsa/ksz.txt b/Documentation/devicetree/bindings/net/dsa/ksz.txt
> index e7db7268fd0fd..4ac576e1cc34e 100644
> --- a/Documentation/devicetree/bindings/net/dsa/ksz.txt
> +++ b/Documentation/devicetree/bindings/net/dsa/ksz.txt
> @@ -5,6 +5,8 @@ Required properties:
>
> - compatible: For external switch chips, compatible string must be exactly one
> of the following:
> + - "microchip,ksz8863"
> + - "microchip,ksz8873"
> - "microchip,ksz9477"
> - "microchip,ksz9897"
> - "microchip,ksz9896"
> @@ -31,6 +33,48 @@ Ethernet switch connected via SPI to the host, CPU port wired to eth0:
> };
> };
>
> + mdio0: mdio-gpio {
Does this example show something new? Examples don't need to instantiate
every possible option.
> + pinctrl-names = "default";
> + pinctrl-0 = <&pinctrl_mdio_1>;
> + compatible = "virtual,mdio-gpio";
> + #address-cells = <1>;
> + #size-cells = <0>;
> + gpios = <&gpio1 31 0 &gpio1 22 0>;
> +
> + ksz8863@3 {
> + compatible = "microchip,ksz8863";
> + interrupt-parrent = <&gpio3>;
> + interrupt = <30 IRQ_TYPE_LEVEL_HIGH>;
> + reg = <0>;
> +
> + ports {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + ports@0 {
> + reg = <0>;
> + label = "lan1";
> + };
> +
> + ports@1 {
> + reg = <1>;
> + label = "lan2";
> + };
> +
> + ports@2 {
> + reg = <2>;
> + label = "cpu";
> + ethernet = <ð0>;
> +
> + fixed-link {
> + speed = <100>;
> + full-duplex;
> + };
> + };
> + };
> + };
> + };
> +
> spi1: spi@f8008000 {
> pinctrl-0 = <&pinctrl_spi_ksz>;
> cs-gpios = <&pioC 25 0>;
> --
> 2.20.1
>
prev parent reply other threads:[~2019-06-13 20:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 21:13 [RFC 0/3] microchip: add support for ksz8863 driver family Michael Grzeschik
2019-05-08 21:13 ` [RFC 1/3] mdio-bitbang: add SMI0 mode support Michael Grzeschik
2019-05-09 14:29 ` Andrew Lunn
2019-05-10 7:32 ` Michael Grzeschik
2019-05-10 12:36 ` Andrew Lunn
2019-05-08 21:13 ` [RFC 2/3] ksz: Add Microchip KSZ8873 SMI-DSA driver Michael Grzeschik
2019-05-09 14:48 ` Andrew Lunn
2019-05-10 7:37 ` Michael Grzeschik
2019-05-08 21:13 ` [RFC 3/3] dt-bindings: net: dsa: document additional Microchip KSZ8863 family switches Michael Grzeschik
2019-06-13 20:09 ` Rob Herring [this message]
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=20190613200935.GA16851@bogus \
--to=robh@kernel.org \
--cc=Tristram.Ha@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=m.grzeschik@pengutronix.de \
--cc=netdev@vger.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).