From: "Amaury Decrême" <amaury.decreme@gmail.com>
To: khali@linux-fr.org, ben-linux@fluff.org, w.sang@pengutronix.de,
rob@landley.net
Cc: amalysh@web.de, mhoffman@lightlink.com, ralf@linux-mips.org,
manuel.lauss@googlemail.com, axel.lin@gmail.com, olof@lixom.net,
rusty@rustcorp.com.au, linux-i2c@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
"Amaury Decrême" <amaury.decreme@gmail.com>
Subject: [PATCH 0/2] I2C: SIS630: Add SIS964 support
Date: Mon, 6 Aug 2012 00:11:52 +0200 [thread overview]
Message-ID: <1344204714-16513-1-git-send-email-amaury.decreme@gmail.com> (raw)
In-Reply-To: <20120805140454.3e7a9606@endymion.delvare>
This series of patches add SIS964 support to i2c-sis630.
The SIS964 is very similar to SIS630 for the SMBus.
+------------------------+--------------------+-------------------+
| | SIS630/730 | SIS964 |
+------------------------+--------------------+-------------------+
| Clock | 14kHz/56kHz | 55.56kHz/27.78kHz |
| SMBus registers offset | 0x80 | 0xE0 |
| SMB_CNT | Bit 1 = Slave Busy | Bit 1 = Bus probe |
| SMB_COUNT | 4:0 bits | 5:0 bits |
+------------------------+--------------------+-------------------+
The other differences doesn't affect the functions provided by the original
driver.
The SIS964 name is ambiguous as this chip isn't part of the SIS96X family and
behaves differently.
Done with SiS 630 and 964 datasheets.
Amaury Decrême (2):
I2C: SIS630: Add SiS964 support
I2C: SIS630: Cosmetics
Documentation/i2c/busses/i2c-sis630 | 17 +-
drivers/i2c/busses/Kconfig | 4 +-
drivers/i2c/busses/i2c-sis630.c | 445 +++++++++++++++++++++--------------
3 files changed, 278 insertions(+), 188 deletions(-)
--
1.7.8.6
next prev parent reply other threads:[~2012-08-05 22:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 15:35 [PATCH v2 0/2] I2C: SIS964: Bus driver Amaury Decrême
2012-08-03 15:35 ` [PATCH v2 1/2] I2C: SIS964: Bus driver - Driver Amaury Decrême
2012-08-03 15:35 ` [PATCH v2 2/2] I2C: SIS964: Bus driver - other files Amaury Decrême
[not found] ` <1344008145-14579-1-git-send-email-amaury.decreme-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-08-03 16:07 ` [PATCH v2 0/2] I2C: SIS964: Bus driver Jean Delvare
2012-08-03 16:36 ` Amaury Decrême
2012-08-03 17:07 ` Jean Delvare
2012-08-04 0:38 ` Amaury Decrême
2012-08-05 12:04 ` Jean Delvare
[not found] ` <20120805140454.3e7a9606-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2012-08-05 22:03 ` Amaury Decrême
2012-08-05 22:11 ` Amaury Decrême [this message]
2012-08-05 22:11 ` [PATCH 1/2] I2C: SIS630: Add SiS964 support Amaury Decrême
[not found] ` <1344204714-16513-1-git-send-email-amaury.decreme-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-08-05 22:11 ` [PATCH 2/2] I2C: SIS630: Cosmetics Amaury Decrême
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=1344204714-16513-1-git-send-email-amaury.decreme@gmail.com \
--to=amaury.decreme@gmail.com \
--cc=amalysh@web.de \
--cc=axel.lin@gmail.com \
--cc=ben-linux@fluff.org \
--cc=khali@linux-fr.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manuel.lauss@googlemail.com \
--cc=mhoffman@lightlink.com \
--cc=olof@lixom.net \
--cc=ralf@linux-mips.org \
--cc=rob@landley.net \
--cc=rusty@rustcorp.com.au \
--cc=w.sang@pengutronix.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 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).