From: Jan Glauber <jglauber@cavium.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org,
David Daney <ddaney@caviumnetworks.com>,
Steven.Hill@caviumnetworks.com, Jan Glauber <jglauber@cavium.com>
Subject: [PATCH v10 0/8] i2c-octeon and i2c-thunderx driver
Date: Wed, 15 Jun 2016 15:51:26 +0200 [thread overview]
Message-ID: <cover.1465997603.git.jglauber@cavium.com> (raw)
Hi Wolfram,
I'm reposting the rebased ThunderX i2c driver series.
Patches are on-top of 4.7-rc3.
Changes to v9:
- rebased on top of upstreamed octeon i2c fixes
- reduced default sclk to 700Mhz
Changes to v8:
- Use device property for clock-frequency setting in thunderx,
get rid of of_find_node_by_name
- Simplify adap.name by using device name
- SMBUS ACPI handling
- Re-phrase SMBUS error/not-specified message
Thanks,
Jan
-------------------------------------------------
Jan Glauber (8):
i2c: octeon: Rename driver to prepare for split
i2c: octeon: Split the driver into two parts
i2c: thunderx: Add i2c driver for ThunderX SOC
i2c: thunderx: Add SMBUS alert support
i2c: octeon,thunderx: Move register offsets to struct
i2c: octeon: Sort include files alphabetically
i2c: cavium: Use booleon values for booleon variables
i2c: octeon: thunderx: Add MAINTAINERS entry
MAINTAINERS | 25 +-
drivers/i2c/busses/Kconfig | 10 +
drivers/i2c/busses/Makefile | 3 +
drivers/i2c/busses/{i2c-octeon.c => i2c-cavium.c} | 1039 ++++++---------------
drivers/i2c/busses/i2c-cavium.h | 214 +++++
drivers/i2c/busses/i2c-octeon-core.c | 288 ++++++
drivers/i2c/busses/i2c-thunderx-core.c | 305 ++++++
7 files changed, 1134 insertions(+), 750 deletions(-)
rename drivers/i2c/busses/{i2c-octeon.c => i2c-cavium.c} (57%)
create mode 100644 drivers/i2c/busses/i2c-cavium.h
create mode 100644 drivers/i2c/busses/i2c-octeon-core.c
create mode 100644 drivers/i2c/busses/i2c-thunderx-core.c
--
1.9.1
next reply other threads:[~2016-06-15 13:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 13:51 Jan Glauber [this message]
2016-06-15 13:51 ` [PATCH v10 1/8] i2c: octeon: Rename driver to prepare for split Jan Glauber
2016-06-15 13:51 ` [PATCH v10 2/8] i2c: octeon: Split the driver into two parts Jan Glauber
2016-06-15 13:51 ` [PATCH v10 3/8] i2c: thunderx: Add i2c driver for ThunderX SOC Jan Glauber
2016-08-23 20:36 ` Wolfram Sang
2016-08-23 20:39 ` Wolfram Sang
2016-08-23 21:09 ` Jan Glauber
2016-08-23 21:09 ` Jan Glauber
2016-08-23 21:22 ` Jan Glauber
2016-08-23 21:22 ` Jan Glauber
2016-06-15 13:51 ` [PATCH v10 4/8] i2c: thunderx: Add SMBUS alert support Jan Glauber
2016-08-23 20:57 ` Wolfram Sang
2016-08-23 21:28 ` Jan Glauber
2016-08-23 21:28 ` Jan Glauber
2016-08-23 21:39 ` Wolfram Sang
2016-08-23 21:52 ` Jan Glauber
2016-08-23 21:52 ` Jan Glauber
2016-06-15 13:51 ` [PATCH v10 5/8] i2c: octeon,thunderx: Move register offsets to struct Jan Glauber
2016-06-15 13:51 ` [PATCH v10 6/8] i2c: octeon: Sort include files alphabetically Jan Glauber
2016-06-15 13:51 ` [PATCH v10 7/8] i2c: cavium: Use booleon values for booleon variables Jan Glauber
2016-06-15 13:51 ` [PATCH v10 8/8] i2c: octeon: thunderx: Add MAINTAINERS entry Jan Glauber
2016-08-23 21:00 ` Wolfram Sang
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=cover.1465997603.git.jglauber@cavium.com \
--to=jglauber@cavium.com \
--cc=Steven.Hill@caviumnetworks.com \
--cc=ddaney@caviumnetworks.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa@the-dreams.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.