From: David Daney <ddaney@caviumnetworks.com>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: linux-mips@linux-mips.org, ralf@linux-mips.org,
linux-i2c@vger.kernel.org, ben-linux@fluff.org,
khali@linux-fr.org, rade.bozic.ext@nsn.com
Subject: Re: [PATCH 1/3] MIPS: Octeon: Add I2C platform driver.
Date: Thu, 07 Jan 2010 12:55:19 -0800 [thread overview]
Message-ID: <4B464A37.7020300@caviumnetworks.com> (raw)
In-Reply-To: <4B4645A3.30401@ru.mvista.com>
Sergei Shtylyov wrote:
> Hello.
>
> David Daney wrote:
>
>> Signed-off-by: David Daney <ddaney@caviumnetworks.com>
>> CC: Rade Bozic <rade.bozic.ext@nsn.com>
>>
> [...]
>> diff --git a/arch/mips/cavium-octeon/octeon-platform.c
>> b/arch/mips/cavium-octeon/octeon-platform.c
>> index 20698a6..f2c0602 100644
>> --- a/arch/mips/cavium-octeon/octeon-platform.c
>> +++ b/arch/mips/cavium-octeon/octeon-platform.c
>> @@ -165,6 +165,78 @@ out:
>> }
>> device_initcall(octeon_rng_device_init);
>>
>> +
>> +#define OCTEON_I2C_IO_BASE 0x1180000001000ull
>> +#define OCTEON_I2C_IO_UNIT_OFFSET 0x200
>> +
>> +static struct octeon_i2c_data octeon_i2c_data[2];
>> +
>> +static int __init octeon_i2c_device_init(void)
>> +{
>> + struct platform_device *pd;
>> + int ret = 0;
>> + int port, num_ports;
>> +
>> + struct resource i2c_resources[] = {
>> + {
>> + .flags = IORESOURCE_MEM,
>> + }, {
>> + .flags = IORESOURCE_IRQ,
>> + }
>> + };
>> +
>> + if (OCTEON_IS_MODEL(OCTEON_CN56XX) ||
>> OCTEON_IS_MODEL(OCTEON_CN52XX))
>> + num_ports = 2;
>> + else
>> + num_ports = 1;
>> +
>> + for (port = 0; port < num_ports; port++) {
>> + octeon_i2c_data[port].sys_freq = octeon_get_clock_rate();
>> + /*FIXME: should be examined. At the moment is set for 100Khz */
>> + octeon_i2c_data[port].i2c_freq = 100000;
>> +
>> + pd = platform_device_alloc("i2c-octeon", port);
>> + if (!pd) {
>> + ret = -ENOMEM;
>> + goto out;
>> + }
>> +
>> + pd->dev.platform_data = octeon_i2c_data + port;
>> +
>> + i2c_resources[0].start =
>> + OCTEON_I2C_IO_BASE + (port * OCTEON_I2C_IO_UNIT_OFFSET);
>> + i2c_resources[0].end = i2c_resources[0].start + 0x20;
>>
>
> Not 0x1F?
>
You are correct. I will fix it.
David Daney
next prev parent reply other threads:[~2010-01-07 20:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-07 19:50 [PATCH 0/3] Add I2C support for Octeon SOCs David Daney
2010-01-07 19:54 ` [PATCH 1/3] MIPS: Octeon: Add I2C platform driver David Daney
2010-01-07 20:35 ` Sergei Shtylyov
2010-01-07 20:55 ` David Daney [this message]
2010-01-07 21:23 ` [PATCH 1/3] MIPS: Octeon: Add I2C platform device David Daney
2010-01-07 19:54 ` [PATCH 2/3] I2C: Add driver for Cavium OCTEON I2C ports David Daney
2010-01-24 16:00 ` Ben Dooks
2010-01-25 11:55 ` Michael Lawnick
2010-01-25 15:12 ` Bozic, Rade (EXT-Other - DE/Ulm)
2010-01-25 15:12 ` Bozic, Rade (EXT-Other - DE/Ulm)
2010-01-25 18:19 ` David Daney
2010-01-07 19:54 ` [PATCH 3/3] MIPS: Octeon: Register some devices on the I2C bus David Daney
2010-01-07 19:56 ` [PATCH 0/3] Add I2C support for Octeon SOCs David Daney
2010-01-11 14:44 ` Ralf Baechle
2010-01-11 17:16 ` David Daney
2010-01-11 17:23 ` Jean Delvare
2010-01-13 0:49 ` Markus Gothe
2010-01-13 9:29 ` Jean Delvare
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=4B464A37.7020300@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=ben-linux@fluff.org \
--cc=khali@linux-fr.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=rade.bozic.ext@nsn.com \
--cc=ralf@linux-mips.org \
--cc=sshtylyov@ru.mvista.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).