Chris Zhong | 22 Sep 09:24 2014

[PATCH] i2c-rk3x: move setup to the earlier subsys initcall

Some device using this bus, such as regulators, they should register
as early as possible, so the I2C bus master needs to be loaded early.
Therefore initialize via subsys_initcall() is better.

Signed-off-by: Chris Zhong <zyw@...>


 drivers/i2c/busses/i2c-rk3x.c |   13 ++++++++++++-
 1 file changed, 12 insertions(+), 1 deletion(-)

diff --git a/drivers/i2c/busses/i2c-rk3x.c b/drivers/i2c/busses/i2c-rk3x.c
index e637c32..5b91901 100644
--- a/drivers/i2c/busses/i2c-rk3x.c
+++ b/drivers/i2c/busses/i2c-rk3x.c
 <at>  <at>  -760,7 +760,18  <at>  <at>  static struct platform_driver rk3x_i2c_driver = {

+static int __init rk3x_i2c_init_driver(void)
+	return platform_driver_register(&rk3x_i2c_driver);
+static void __exit rk3x_i2c_exit_driver(void)
+	platform_driver_unregister(&rk3x_i2c_driver);
(Continue reading)

Benjamin Siaka | 22 Sep 03:14 2014


Hello my Dear,

I will greatly appreciate my correspondence meets you in good health condition.

My name is Mr. Benjamin Siaka. I am seeking for your co-operation for investment partnership in your
Country. I shall provide the FUND for the investment. When you acknowledged the receipt of this
correspondence, thereafter I will give you the Full Details of my investment proposal.

I await your response in earliest.

My regards,
Mr. Benjamin Siaka.
Maria Caballero | 18 Sep 16:15 2014


Loan Offer contact us for  more details (gibonline11@...<mailto:gibonline11@...>)
All Details should be forward to this E-mail address for fast respond: gibonline11@...<mailto:gibonline11@...>
Jean Delvare | 18 Sep 14:17 2014

i2c-core.ko renamed to i2ccore.ko

Hi guys,

Sorry for jumping in a bit late, but given that I did not get involved
in the discussions that led to this decision, better late than never.

I almost had an heart attack when noticing that module i2c-core.ko has
suddenly been renamed to i2ccore.ko without an hyphen.

Renaming kernel modules is almost always wrong, in particular subsystem
core modules. Such renames have an impact at various levels. We just had
to change a configuration file in the openSUSE Factory kernel to adjust
that change, and this is how I noticed it. But there can be several
other issues, including mkinitrd or equivalent tools, as well as
documentation. The extra work and confusion is a high price to pay, and
it can easily be avoided.

So I am kindly asking that you revert this name change before kernel
v3.17 final. Rename source files if you really have to, git makes it
easy. Or merge the i2c-acpi.c code into i2c-core.c with ifdefs. Or
whatever. Just don't rename i2c-core.ko, please.


Jean Delvare
SUSE L3 Support

Mika Westerberg | 18 Sep 11:26 2014

[PATCH 1/2] i2c: designware: Rework probe() to get clock a bit later

In order to be able to create missing clock for AMD (and in future possibly
others) we move getting clock for the device a bit later. Also make ACPI/DT
configuration in the same place depending on from where the device was
enumerated from.

Signed-off-by: Mika Westerberg <mika.westerberg@...>
 drivers/i2c/busses/i2c-designware-platdrv.c | 54 ++++++++++++++---------------
 1 file changed, 26 insertions(+), 28 deletions(-)

diff --git a/drivers/i2c/busses/i2c-designware-platdrv.c b/drivers/i2c/busses/i2c-designware-platdrv.c
index bc8773333155..7087b6ee97e2 100644
--- a/drivers/i2c/busses/i2c-designware-platdrv.c
+++ b/drivers/i2c/busses/i2c-designware-platdrv.c
 <at>  <at>  -81,9 +81,6  <at>  <at>  static int dw_i2c_acpi_configure(struct platform_device *pdev)
 	struct dw_i2c_dev *dev = platform_get_drvdata(pdev);
 	bool fs_mode = dev->master_cfg & DW_IC_CON_SPEED_FAST;

-	if (!ACPI_HANDLE(&pdev->dev))
-		return -ENODEV;
 	dev-> = -1;
 	dev->tx_fifo_depth = 32;
 	dev->rx_fifo_depth = 32;
 <at>  <at>  -123,6 +120,7  <at>  <at>  static int dw_i2c_probe(struct platform_device *pdev)
 	struct i2c_adapter *adap;
 	struct resource *mem;
 	int irq, r;
+	u32 ht = 0;

(Continue reading)

addy ke | 18 Sep 03:26 2014

Re: About RK3288 i2c scl duty cycle

Add public list

On 2014/9/17 23:17, Doug Anderson wrote:
> Addy,
> On Tue, Sep 16, 2014 at 6:30 PM,
> <> wrote:
>> hi, all
> Any reason why you didn't add some public lists?  It seems like this
> is a perfect discussion for linux-i2c.
>> According to i2c-bus specification(version2.1, page 32, Table5, FAST-MODE):
>> The minimum LOW period of the scl clock is <1.3us>, and the minimum HIGH
>> period of the scl clock is <0.6us>.
>> T(min_low) : T(min_high)  ~= 2 : 1
>> If <DIVH = DIVL> in fast mode(scl rate = 400Khz)
>> 1)Under ideal conditions, T(scl_low) = T(scl_high) = <1.25us>
>> 2)Our measurement, T(scl_low) = <1.3us>, T(scl_high) = <1.25us>
>> The low period of the scl clock is critical.
>> Do we need set <DIVL:DIVH = 1 : 2>  to increase T(scl_low)?   // T(scl_low )
>> : T(scl_High) = 2 : 1
> I can't say I've ever looked at that pat of the i2c spec before, but
> what you say seems reasonable to me.  ...well for 400kHz, at least.
> At 100kHz you shouldn't use the same 2:1 ratio.
(Continue reading)


Spoštovani uporabnik spletne pošte.

Zaradi zastojev na vse uporabnike Webmail vam predstavlja
morali posodobiti svoj ​​račun z našo novo F-Secure Internet sprosti
Safety 2014 Nova različica najboljših značilnosti spam in virusi.

Da bi posodobili svoj ​​nabiralnik prosimo, izpolnite podatke spodaj, da
vam omogočajo, da posodobite
vaš e-poštni račun takoj.

Uporabniško ime:
Potrdi geslo:
Mobilna številka:

Neuspeh ponovno preveri vaš račun obdeluje začasno
blokirana ali začasno našega omrežja, in morda ne boste mogli pošiljati ali
prejemanje e-pošte, dokler ne boste ponovno potrditi svoj nabiralnik.

Webmail Uporabniki © 2014 Vse pravice pridržane.

Carl Peng | 17 Sep 07:14 2014

[PATCH v4] i2c: designware: Add support for AMD i2c controller

AMD i2c bus controller is ACPI device, its ACPI ID
is "AMD0010". This patch is used to add support for
AMD i2c bus controller in the Designware platform

Signed-off-by: Carl Peng <carlpeng008@...>
Cc: Huang Rui <ray.huang@...>
 drivers/i2c/busses/i2c-designware-platdrv.c | 53 +++++++++++++++++++++++------
 1 file changed, 43 insertions(+), 10 deletions(-)

diff --git a/drivers/i2c/busses/i2c-designware-platdrv.c b/drivers/i2c/busses/i2c-designware-platdrv.c
index bc87733..20015e6 100644
--- a/drivers/i2c/busses/i2c-designware-platdrv.c
+++ b/drivers/i2c/busses/i2c-designware-platdrv.c
 <at>  <at>  -43,14 +43,18  <at>  <at> 
 #include <linux/acpi.h>
 #include "i2c-designware-core.h"

+struct dw_i2c_config {
+	u32 clk_rate_khz;
 static struct i2c_algorithm i2c_dw_algo = {
 	.master_xfer	= i2c_dw_xfer,
 	.functionality	= i2c_dw_func,
-static u32 i2c_dw_get_clk_rate_khz(struct dw_i2c_dev *dev)
-	return clk_get_rate(dev->clk)/1000;
(Continue reading)

Corey Minyard | 17 Sep 02:30 2014

I2c modifications for IPMI operations at panic time

I've been carrying along modifications to the I2C subsystem to allow an
IPMI interface over SMBus (per the IPMI standard).  I have these
modification because the IPMI driver has functions that it performs at
panic/shutdown time, like handling poiwer, extending the watchdog on a
panic, and storing panic information in the IPMI event log.

I haven't really cared much about the SMBus IPMI driver because very few
systems have one of these.  I've been keeping it up to date and testing
it periodically, but that's about it.  However, it looks like more
systems are going to be using this interface, so I need to do something.

The changes I have are fairly large, but they mainly move code around to
allow the I2C core to be event driven or polled without duplicating a
lot of code.  They create an event-driven interface on top of and
underneath the driver.  You can use the polled interface into the top of
the driver and talk to a polled or event-driven driver, the I2C core
takes care of the translation from a polled user to an event-driven
driver.  You have to have an event-driven driver to use the event-driven

The code is in git://
openipmi-linux-ipmi in the ipmi-i2c branch.  It needs a little work at
this point, but nothing big.  It has modifications to the i801 and piix4
drivers to make them event-driven, too.

Would such changes be acceptable?  I"m not sure anything else has a use
for this.  Maybe a driver to store panic information in an I2C EEPROM,
or anything that would need to get to I2C at panic time.

I'd prefer to have the full function of the IPMI driver, of course, and
(Continue reading)

Fan Du | 16 Sep 11:21 2014

[PATCH 0/2] Small fix with i2c-ismt driver


This patcheset fix two issue with i2c ismt driver:

Patch1: Use only 2 descriptor for transfer and receive
Patch2: Only copy valid data when transfer

Fan Du (2):
  i2c-ismt: Use minimum descriptor size
  i2c-ismt: use correct length when copy buffer

 drivers/i2c/busses/i2c-ismt.c |    6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)



Carl Peng | 16 Sep 08:20 2014

[PATCH v3] i2c: designware: Add support for AMD i2c controller

AMD i2c bus controller is ACPI device, its ACPI ID
is "AMD0010". This patch is used to add support for
AMD i2c bus controller in the Designware platform

Signed-off-by: Carl Peng <carlpeng008@...>
Cc: Huang Rui <ray.huang@...>
 drivers/i2c/busses/i2c-designware-core.h    |  1 +
 drivers/i2c/busses/i2c-designware-platdrv.c | 46 +++++++++++++++++++++++++----
 2 files changed, 41 insertions(+), 6 deletions(-)

diff --git a/drivers/i2c/busses/i2c-designware-core.h b/drivers/i2c/busses/i2c-designware-core.h
index d66b6cb..c67d4ac 100644
--- a/drivers/i2c/busses/i2c-designware-core.h
+++ b/drivers/i2c/busses/i2c-designware-core.h
 <at>  <at>  -105,6 +105,7  <at>  <at>  struct dw_i2c_dev {
 	u16			ss_lcnt;
 	u16			fs_hcnt;
 	u16			fs_lcnt;
+	struct	dw_i2c_pdata	*pdata;

 #define ACCESS_SWAP		0x00000001
diff --git a/drivers/i2c/busses/i2c-designware-platdrv.c b/drivers/i2c/busses/i2c-designware-platdrv.c
index bc87733..8a96e69 100644
--- a/drivers/i2c/busses/i2c-designware-platdrv.c
+++ b/drivers/i2c/busses/i2c-designware-platdrv.c
 <at>  <at>  -43,15 +43,31  <at>  <at> 
 #include <linux/acpi.h>
(Continue reading)