From: "Mark A. Greer" <mgreer@mvista.com>
To: LM Sensors <sensors@stimpy.netroedge.com>,
LKML <linux-kernel@vger.kernel.org>
Cc: Greg KH <greg@kroah.com>
Subject: Re: [PATCH][I2C] Marvell mv64xxx i2c driver
Date: Wed, 26 Jan 2005 13:33:14 -0700 [thread overview]
Message-ID: <41F7FE8A.2070508@mvista.com> (raw)
In-Reply-To: <20050126205619.4c0b41fa.khali@linux-fr.org>
Jean Delvare wrote:
>Hi Mark,
>
Thanks for the commenting, Jean.
><snip>
>
>
>
>>+config I2C_MV64XXX
>>+ tristate "Marvell mv64xxx I2C Controller"
>>+ depends on I2C && MV64X60
>>
>>
>
>&& EXPERIMENTAL?
>
Yes, I guess that's the correct thing to do. I'll add that.
>>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?
>
Absolutely. I was unaware of the other uses.
>
>
>>-#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.
>
>
Oops. I'll fix that too and repost later today.
Mark
next prev parent reply other threads:[~2005-01-27 1:23 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
2005-01-26 20:33 ` Mark A. Greer [this message]
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=41F7FE8A.2070508@mvista.com \
--to=mgreer@mvista.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--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