From: Randy Dunlap <rdunlap@infradead.org>
To: Don Bollinger <don@thebollingers.org>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Cc: brandon_chuang@edge-core.com, wally_wang@accton.com,
roy_lee@edge-core.com, rick_burchett@edge-core.com,
quentin.chang@quantatw.com, jeffrey.townsend@bitswitch.com,
scotte@cumulusnetworks.com, roopa@cumulusnetworks.com,
David Ahern <dsa@cumulusnetworks.com>,
luke.williams@canonical.com, Guohan Lu <gulv@microsoft.com>,
Xin Liu <xinxliu@microsoft.com>,
steve.joiner@finisar.com
Subject: Re: [PATCH] optoe: driver to read/write SFP/QSFP EEPROMs
Date: Sun, 10 Jun 2018 21:56:00 -0700 [thread overview]
Message-ID: <37dfd504-5921-54f2-b90e-a26595fc0a5e@infradead.org> (raw)
In-Reply-To: <20180611042515.ml6zbcmz6dlvjmrp@thebollingers.org>
Hi,
On 06/10/2018 09:25 PM, Don Bollinger wrote:
> diff --git a/drivers/misc/eeprom/Kconfig b/drivers/misc/eeprom/Kconfig
> index 68a1ac929917..9a08e12756ee 100644
> --- a/drivers/misc/eeprom/Kconfig
> +++ b/drivers/misc/eeprom/Kconfig
> @@ -111,4 +111,22 @@ config EEPROM_IDT_89HPESX
> This driver can also be built as a module. If so, the module
> will be called idt_89hpesx.
>
> +config EEPROM_OPTOE
> + tristate "read/write access to SFP* & QSFP* EEPROMs"
> + depends on I2C && SYSFS
> + help
> + If you say yes here you get support for read and write access to
> + the EEPROM of SFP and QSFP type optical and copper transceivers.
> + Includes all devices which conform to the sff-8436 and sff-8472
This includes
and then please s/sff/SFF/ (2 places).
> + spec including SFP, SFP+, SFP28, SFP-DWDM, QSFP, QSFP+, QSFP28
> + or later. These devices are usually found in network switches.
> +
> + This driver only manages read/write access to the EEPROM, all
> + other features should be accessed via i2c-dev.
> +
> + This driver can also be built as a module. If so, the module
> + will be called optoe.
> +
> + If unsure, say N.
> +
> endmenu
thanks,
--
~Randy
next prev parent reply other threads:[~2018-06-11 4:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 4:25 Don Bollinger
2018-06-11 4:56 ` Randy Dunlap [this message]
2018-06-11 18:31 ` Don Bollinger
2018-06-11 13:43 ` Arnd Bergmann
2018-06-14 0:40 ` Don Bollinger
2018-06-14 7:46 ` Arnd Bergmann
2018-06-15 2:41 ` Don Bollinger
2018-06-11 18:33 ` Tom Lendacky
2018-06-11 21:01 ` Don Bollinger
2018-06-12 18:11 ` Andrew Lunn
2018-06-15 2:26 ` Don Bollinger
2018-06-15 3:24 ` Florian Fainelli
2018-06-18 19:13 ` Don Bollinger
2018-06-15 7:54 ` Andrew Lunn
2018-06-18 19:41 ` Don Bollinger
2018-06-19 15:15 ` Andrew Lunn
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=37dfd504-5921-54f2-b90e-a26595fc0a5e@infradead.org \
--to=rdunlap@infradead.org \
--cc=arnd@arndb.de \
--cc=brandon_chuang@edge-core.com \
--cc=don@thebollingers.org \
--cc=dsa@cumulusnetworks.com \
--cc=gregkh@linuxfoundation.org \
--cc=gulv@microsoft.com \
--cc=jeffrey.townsend@bitswitch.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luke.williams@canonical.com \
--cc=quentin.chang@quantatw.com \
--cc=rick_burchett@edge-core.com \
--cc=roopa@cumulusnetworks.com \
--cc=roy_lee@edge-core.com \
--cc=scotte@cumulusnetworks.com \
--cc=steve.joiner@finisar.com \
--cc=wally_wang@accton.com \
--cc=xinxliu@microsoft.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
all inboxes | Powered by JetHome®