From: Andrew Lunn <andrew@lunn.ch>
To: Vladimir Vid <vladimir.vid@sartura.hr>
Cc: devicetree@vger.kernel.org, Luka Perkov <luka.perkov@sartura.hr>,
Paul Arola <paul.arola@telus.com>,
Luis Torres <luis.torres@methode.com>,
Scott Roberts <scott.roberts@telus.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: dts: marvell: Add device tree for uDPU board
Date: Fri, 11 Jan 2019 18:44:32 +0100 [thread overview]
Message-ID: <20190111174432.GH20924@lunn.ch> (raw)
In-Reply-To: <20190111172055.30451-1-vladimir.vid@sartura.hr>
> + sfp_eth0: sfp-eth0 {
> + compatible = "sff,sfp";
> + i2c-bus = <&i2c0>;
> + los-gpio = <&gpiosb 2 GPIO_ACTIVE_HIGH>;
> + mod-def0-gpio = <&gpiosb 3 GPIO_ACTIVE_LOW>;
> + tx-disable-gpio = <&gpiosb 4 GPIO_ACTIVE_HIGH>;
> + tx-fault-gpio = <&gpiosb 5 GPIO_ACTIVE_HIGH>;
> + };
> +
> + sfp_eth1: sfp-eth1 {
> + compatible = "sff,sfp";
> + i2c-bus = <&i2c1>;
> + los-gpio = <&gpiosb 7 GPIO_ACTIVE_HIGH>;
> + mod-def0-gpio = <&gpiosb 8 GPIO_ACTIVE_LOW>;
> + tx-disable-gpio = <&gpiosb 9 GPIO_ACTIVE_HIGH>;
> + tx-fault-gpio = <&gpiosb 10 GPIO_ACTIVE_HIGH>;
> + };
> +};
> +&i2c0 {
> + status = "okay";
> + pinctrl-names = "default";
> + pinctrl-0 = <&i2c1_pins>;
> +
> + eeprom@50 {
> + compatible = "atmel,24c04";
> + reg = <0x50>;
> + };
> +};
> +
> +&i2c1 {
> + status = "okay";
> + pinctrl-names = "default";
> + pinctrl-0 = <&i2c2_pins>;
> +
> + eeprom@50 {
> + compatible = "atmel,24c04";
> + reg = <0x50>;
> + };
> +};
The SFP driver will export the 'eeprom' via ethtool --module-info.
Please don't add a standard EEPROM.
Andrew
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-01-11 17:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 17:20 [PATCH] arm64: dts: marvell: Add device tree for uDPU board Vladimir Vid
2019-01-11 17:41 ` Andrew Lunn
2019-01-11 17:44 ` Andrew Lunn [this message]
2019-01-15 12:11 ` [PATCH v2 1/2] " Vladimir Vid
2019-01-15 13:42 ` Andrew Lunn
2019-01-15 14:44 ` [PATCH v3] " Vladimir Vid
2019-01-15 16:16 ` Andrew Lunn
2019-01-15 16:37 ` Gregory CLEMENT
2019-01-15 17:38 ` [PATCH v4] " Vladimir Vid
2019-01-18 15:45 ` Gregory CLEMENT
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=20190111174432.GH20924@lunn.ch \
--to=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=luis.torres@methode.com \
--cc=luka.perkov@sartura.hr \
--cc=paul.arola@telus.com \
--cc=scott.roberts@telus.com \
--cc=vladimir.vid@sartura.hr \
/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).