From: Jean Delvare <khali@linux-fr.org>
To: "Mark A. Greer" <mgreer@mvista.com>
Cc: Greg KH <greg@kroah.com>,
LM Sensors <sensors@stimpy.netroedge.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][I2C] Marvell mv64xxx i2c driver
Date: Wed, 26 Jan 2005 20:56:19 +0100 [thread overview]
Message-ID: <20050126205619.4c0b41fa.khali@linux-fr.org> (raw)
In-Reply-To: <41F6F1D5.90601@mvista.com>
Hi Mark,
> Marvell makes a line of host bridge for PPC and MIPS systems. On
> those bridges is an i2c controller. This patch adds the driver for
> that i2c controller.
>
> Please let me know if you see any problems with this patch.
I do not feel qualified for a full review of this code. However, I
noticed the following minor issues:
> +config I2C_MV64XXX
> + tristate "Marvell mv64xxx I2C Controller"
> + depends on I2C && MV64X60
&& EXPERIMENTAL?
> diff -Nru a/include/linux/i2c-id.h b/include/linux/i2c-id.h
> --- a/include/linux/i2c-id.h 2005-01-25 18:15:24 -07:00
> +++ b/include/linux/i2c-id.h 2005-01-25 18:15:24 -07:00
> @@ -200,6 +200,7 @@
>
> #define I2C_ALGO_SIBYTE 0x150000 /* Broadcom SiByte SOCs */
> #define I2C_ALGO_SGI 0x160000 /* SGI algorithm */
> +#define I2C_ALGO_MV64XXX 0x170000 /* Marvell mv64xxx i2c ctlr */
0x170000 is reserved within the legacy i2c project for an USB algorithm,
and 0x180000 for virtual busses. Could you please use 0x190000 instead,
so as to avoid future collisions?
> -#define MV64340_I2C_SLAVE_ADDR 0xc000
> -#define MV64340_I2C_EXTENDED_SLAVE_ADDR 0xc010
> -#define MV64340_I2C_DATA 0xc004
> -#define MV64340_I2C_CONTROL 0xc008
> -#define MV64340_I2C_STATUS_BAUDE_RATE 0xc00C
> -#define MV64340_I2C_SOFT_RESET 0xc01c
> +#define MV64XXX_I2C_CTLR_NAME "mv64xxx i2c"
> +#define MV64XXX_I2C_OFFSET 0xc000
> +#define MV64XXX_I2C_REG_BLOCK_SIZE 0x0020
You have a tab instead of space before MV64XXX_I2C_CTLR_NAME, it seems.
Also, you want to align the numerical values using only tabs, no space.
Thanks,
--
Jean Delvare
http://khali.linux-fr.org/
next prev parent reply other threads:[~2005-01-26 23:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 1:26 [PATCH][I2C] Marvell mv64xxx i2c driver Mark A. Greer
2005-01-26 19:56 ` Jean Delvare [this message]
2005-01-26 20:33 ` Mark A. Greer
2005-01-26 21:56 ` Mark A. Greer
2005-01-26 22:42 ` Greg KH
2005-01-26 23:59 ` Mark A. Greer
2005-01-31 18:25 ` Greg KH
2005-01-31 18:41 ` Mark A. Greer
2005-02-01 0:46 ` Greg KH
2005-02-01 17:54 ` Mark A. Greer
[not found] <200502020315.14281.adobriyan@mail.ru>
2005-02-02 1:27 ` Greg KH
2005-02-02 17:26 ` Mark A. Greer
[not found] ` <200502031556.59319.adobriyan@mail.ru>
2005-02-03 19:12 ` Mark A. Greer
2005-02-04 0:38 ` Alexey Dobriyan
2005-02-04 0:04 ` Mark A. Greer
2005-02-04 9:45 ` Jean Delvare
2005-02-06 14:36 ` Jean Delvare
-- strict thread matches above, loose matches on Subject: below --
2005-02-08 23:27 Mark A. Greer
2005-02-09 0:01 ` Bartlomiej Zolnierkiewicz
2005-02-09 0:32 ` Mark A. Greer
2005-02-09 1:24 ` Bartlomiej Zolnierkiewicz
2005-02-09 21:33 ` Mark A. Greer
2005-02-17 22:25 ` Greg KH
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=20050126205619.4c0b41fa.khali@linux-fr.org \
--to=khali@linux-fr.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgreer@mvista.com \
--cc=sensors@stimpy.netroedge.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