From: Adrian Yanes <devel@ayanes.com>
To: linux-arm-kernel@lists.infradead.org
Cc: linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org
Subject: Re: AW: [PATCH v10 3/4] drivers/i2c/busses/i2c-at91.c: add new driver
Date: Wed, 09 May 2012 22:07:51 +0300 [thread overview]
Message-ID: <4FAAC087.7030304@ayanes.com> (raw)
In-Reply-To: <D99582E5322435468A77E74BB0039E7B1D2293684D@SRV02.hamburg.garz-fricke.de>
>> Yes, our ECO920 uses the RM9200, but we support it with an very old kernel
>> (2.6.21). I remember there were many problems with I2C.
I really doubt this, as I indicated in a previous email[1], the RM9200
has a hardware "bug". So either you performed the testing with less than
2 bytes of data and in a really low frequency (<50kHz) or we are missing
something.
Can you provide more details about which kind of testing you performed?
Thanks
1 - http://article.gmane.org/gmane.linux.kernel/1287445/match=
WARNING: multiple messages have this Message-ID (diff)
From: devel@ayanes.com (Adrian Yanes)
To: linux-arm-kernel@lists.infradead.org
Subject: AW: [PATCH v10 3/4] drivers/i2c/busses/i2c-at91.c: add new driver
Date: Wed, 09 May 2012 22:07:51 +0300 [thread overview]
Message-ID: <4FAAC087.7030304@ayanes.com> (raw)
In-Reply-To: <D99582E5322435468A77E74BB0039E7B1D2293684D@SRV02.hamburg.garz-fricke.de>
>> Yes, our ECO920 uses the RM9200, but we support it with an very old kernel
>> (2.6.21). I remember there were many problems with I2C.
I really doubt this, as I indicated in a previous email[1], the RM9200
has a hardware "bug". So either you performed the testing with less than
2 bytes of data and in a really low frequency (<50kHz) or we are missing
something.
Can you provide more details about which kind of testing you performed?
Thanks
1 - http://article.gmane.org/gmane.linux.kernel/1287445/match=
next prev parent reply other threads:[~2012-05-09 19:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <D99582E5322435468A77E74BB0039E7B1D22784CF0@SRV02.hamburg.garz-fricke.de>
[not found] ` <D99582E5322435468A77E74BB0039E7B1D22784CF0-6hi2BFpdtA3X4XV0xjfKZxOngtiEHj0sqGK+G5UkneY@public.gmane.org>
2012-04-26 11:01 ` [PATCH v10 3/4] drivers/i2c/busses/i2c-at91.c: add new driver Nikolaus Voss
2012-04-26 11:01 ` Nikolaus Voss
[not found] ` <D99582E5322435468A77E74BB0039E7B1D22784E8B@SRV02.hamburg.garz-fricke.de>
2012-04-27 8:04 ` Voss, Nikolaus
2012-04-27 8:04 ` Voss, Nikolaus
2012-04-27 8:36 ` AW: " Carsten Behling
2012-04-27 8:36 ` Carsten Behling
2012-04-27 8:36 ` Carsten Behling
2012-05-09 19:07 ` Adrian Yanes [this message]
2012-05-09 19:07 ` Adrian Yanes
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=4FAAC087.7030304@ayanes.com \
--to=devel@ayanes.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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.