From: "Richard Röjfors" <richard.rojfors-l7gf1WXxx3uGw+nKnLezzg@public.gmane.org>
To: Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org
Subject: Re: [PATCH] i2c: Add support for Xilinx XPS IIC Bus Interface
Date: Wed, 23 Sep 2009 11:08:45 +0200 [thread overview]
Message-ID: <4AB9E59D.3070503@mocean-labs.com> (raw)
In-Reply-To: <20090923004158.GD24720-SMNkleLxa3Z6Wcw2j4pizdi2O/JbrIOy@public.gmane.org>
Ben Dooks wrote:
> On Mon, Sep 21, 2009 at 03:56:11PM +0200, Richard Röjfors wrote:
>> This patch adds support for the Xilinx XPS IIC Bus Interface.
>>
>> The driver uses the dynamic mode, supporting to put several
>> I2C messages in the FIFO to reduce the number of interrupts.
>>
>> It has the same feature as ocores, it can be passed a list
>> of devices that will be added when the bus is probed.
>>
>> Signed-off-by: Richard Röjfors <richard.rojfors-l7gf1WXxx3uGw+nKnLezzg@public.gmane.org>
>> ---
>> diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig
>> index 8206442..6b291e8 100644
>> --- a/drivers/i2c/busses/Kconfig
>> +++ b/drivers/i2c/busses/Kconfig
>> @@ -433,6 +433,16 @@ config I2C_OCORES
>> This driver can also be built as a module. If so, the module
>> will be called i2c-ocores.
>>
>> +config I2C_XILINX
>> + tristate "Xilinx I2C Controller"
>> + depends on EXPERIMENTAL && HAS_IOMEM
>> + help
>> + If you say yes to this option, support will be included for the
>> + Xilinx I2C controller.
>> +
>> + This driver can also be built as a module. If so, the module
>> + will be called xilinx_i2c.
>> +
>> config I2C_OMAP
>> tristate "OMAP I2C adapter"
>> depends on ARCH_OMAP
>> diff --git a/drivers/i2c/busses/Makefile b/drivers/i2c/busses/Makefile
>> index e654263..a2ce5b8 100644
>> --- a/drivers/i2c/busses/Makefile
>> +++ b/drivers/i2c/busses/Makefile
>> @@ -40,6 +40,7 @@ obj-$(CONFIG_I2C_IXP2000) += i2c-ixp2000.o
>> obj-$(CONFIG_I2C_MPC) += i2c-mpc.o
>> obj-$(CONFIG_I2C_MV64XXX) += i2c-mv64xxx.o
>> obj-$(CONFIG_I2C_OCORES) += i2c-ocores.o
>> +obj-$(CONFIG_I2C_XILINX) += i2c-xiic.o
>> obj-$(CONFIG_I2C_OMAP) += i2c-omap.o
>> obj-$(CONFIG_I2C_PASEMI) += i2c-pasemi.o
>> obj-$(CONFIG_I2C_PNX) += i2c-pnx.o
>> diff --git a/drivers/i2c/busses/i2c-xiic.c b/drivers/i2c/busses/i2c-xiic.c
>> new file mode 100644
>> index 0000000..7b1e618
>> --- /dev/null
>> +++ b/drivers/i2c/busses/i2c-xiic.c
>> @@ -0,0 +1,800 @@
>> +/*
>> + * i2c-xiic.c
>> + * Copyright (c) 2009 Intel Corporation
>
> is this the right copyirhgt entity?
Thanks for your feedback. Yes it is the right copyright, it's for Intel.
I agree with the rest of your comments and will come up with an updated patch.
Thanks
--Richard
prev parent reply other threads:[~2009-09-23 9:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-21 13:56 [PATCH] i2c: Add support for Xilinx XPS IIC Bus Interface Richard Röjfors
[not found] ` <4AB785FB.4020806-l7gf1WXxx3uGw+nKnLezzg@public.gmane.org>
2009-09-23 0:41 ` Ben Dooks
[not found] ` <20090923004158.GD24720-SMNkleLxa3Z6Wcw2j4pizdi2O/JbrIOy@public.gmane.org>
2009-09-23 9:08 ` Richard Röjfors [this message]
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=4AB9E59D.3070503@mocean-labs.com \
--to=richard.rojfors-l7gf1wxxx3ugw+nknlezzg@public.gmane.org \
--cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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.