netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <Tristram.Ha@microchip.com>
To: Sergio Paracuellos <sergio.paracuellos@gmail.com>,
	Andrew Lunn <andrew@lunn.ch>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Pavel Machek <pavel@ucw.cz>, Marek Vasut <marex@denx.de>,
	Dan Carpenter <dan.carpenter@oracle.com>
Cc: Tristram Ha <Tristram.Ha@microchip.com>,
	<vivien.didelot@savoirfairelinux.com>,
	<UNGLinuxDriver@microchip.com>, <netdev@vger.kernel.org>
Subject: [PATCH RFC net-next] net: dsa: microchip: add KSZ9477 I2C driver
Date: Mon, 17 Dec 2018 17:39:59 -0800	[thread overview]
Message-ID: <1545097200-26493-1-git-send-email-Tristram.Ha@microchip.com> (raw)

From: Tristram Ha <Tristram.Ha@microchip.com>

This patch adds KSZ9477 I2C driver support.

I know a patch for KSZ9477 I2C driver was already submitted.  There is a
minor problem though.  The structure and code of the I2C driver should
match those in the SPI driver.  The only difference is the register
access.

Accordingly the file ksz_i2c.h is created so that some shared I2C
functions can be used by other switch drivers.

Tristram Ha (1):
  net: dsa: microchip: add KSZ9477 I2C driver

 drivers/net/dsa/microchip/Kconfig       |   6 +
 drivers/net/dsa/microchip/Makefile      |   1 +
 drivers/net/dsa/microchip/ksz9477_i2c.c | 194 ++++++++++++++++++++++++++++++++
 drivers/net/dsa/microchip/ksz_i2c.h     |  69 ++++++++++++
 4 files changed, 270 insertions(+)
 create mode 100644 drivers/net/dsa/microchip/ksz9477_i2c.c
 create mode 100644 drivers/net/dsa/microchip/ksz_i2c.h

-- 
1.9.1

             reply	other threads:[~2018-12-18  1:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-18  1:39 Tristram.Ha [this message]
2018-12-18  1:40 ` [PATCH RFC net-next] net: dsa: microchip: add KSZ9477 I2C driver Tristram.Ha
2018-12-18  2:55   ` Woojung.Huh
2018-12-18  4:16   ` Tristram.Ha
2018-12-18  6:30     ` Sergio Paracuellos
2018-12-18  6:24   ` Sergio Paracuellos
2018-12-18 10:01     ` Andrew Lunn
2018-12-18 14:49       ` Marek Vasut
2018-12-18  8:06 ` Dan Carpenter
2018-12-18  8:54   ` Sergio Paracuellos

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=1545097200-26493-1-git-send-email-Tristram.Ha@microchip.com \
    --to=tristram.ha@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=andrew@lunn.ch \
    --cc=dan.carpenter@oracle.com \
    --cc=f.fainelli@gmail.com \
    --cc=marex@denx.de \
    --cc=netdev@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=sergio.paracuellos@gmail.com \
    --cc=vivien.didelot@savoirfairelinux.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).