netdev - Device tree binding for Managed Switch

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Thu, 9 Jan 2014 14:12:24 +0800 (SGT)
From:	Tama <pkm_munot@...oo.co.in>
To:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Device tree binding for Managed Switch



Hi All,

I am new to this mailing this. I am using IMX28 based custom designed board, based on TQ Components TQMA28 module. In our board we are using KSZ8863 and KSZ8895 managed switches instead of standard phy device. How to add support for managed switch in device tree.

I am new to device tree configuration. At present I have got
        mac0: ethernet@...f0000 {
            compatible = "fsl,imx28-fec";
            reg = <0x800f0000 0x4000>;
            interrupts = <101>;
            status = "disabled";
        };

        mac1: ethernet@...f4000 {
            compatible = "fsl,imx28-fec";
            reg = <0x800f4000 0x4000>;
            interrupts = <102>;
            status = "disabled";
        };

In my device tree imx28.dtsi and in imx28-mba28.dts I have got 

        /* FCC1 management to switch */
        eth0: ethernet@...f0000 {
            device_type = "network";
            compatible = "micrel,ksz8895";
            reg = <0x800f0000 0x4000>;
            local-mac-address = [ 00 01 02 03 04 07 ];
            interrupts = <101>;
            fixed-link = <1 1 1000 0 0>;
            phy-handle = <&phy0>;           
            phy0: phy@0 {
              fixed-link;
              full-duplex;
              speed = <1000>;
            };
        };       

        /* FCC1 management to switch */
        eth1: ethernet@...f4000 {
            device_type = "network";
            compatible = "micrel, ksz8895";
            reg = <0x800f0000 0x4000>;
            local-mac-address = [ 00 01 02 03 04 08 ];
            interrupts = <102>;
            fixed-link = <1 1 1000 0 0>;
            phy-handle = <&phy1>;
            phy1: phy@1 {
              fixed-link;
              full-duplex;
              speed = <1000>;
            };           
        };


I read threads on this mailing list and modified the device tree for managed switch. I am not 100% sure if my configuration is correct. When the kernel is booting it is scanning for phy devices and as it doesnt get a phy device id it doesnt register any device.

Can some one please share information on how to configure the device tree for device and not a phy.

Thanks
Pritam
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html