From: ben.dooks@codethink.co.uk (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] i2c:dw: Add APM X-Gene ACPI I2C device support
Date: Mon, 4 Jan 2016 09:09:37 +0000 [thread overview]
Message-ID: <568A36D1.8070808@codethink.co.uk> (raw)
In-Reply-To: <1450863241.7740.30.camel@kxue-X58A-UD3R>
On 23/12/15 09:34, Ken Xue wrote:
> On Tue, 2015-12-15 at 16:59 +0200, Mika Westerberg wrote:
>> On Tue, Dec 15, 2015 at 08:52:19AM -0600, Suravee Suthikulpanit wrote:
> During test, I2C bus should run in different "ConnectionSpeed" of
> device.
>
> That means windows driver can modify I2C bus speed to match the
> "ConnectionSpeed" of device on-the-fly. Static value from SSCN and FMCN
> can not work for WITT test cases.
>
> It sounds like odd that multi-speed can be applied over one I2C bus, But
> everything goes well.
> Does this behavior(multi-speed) violate the I2C spec?
I can't remember if the spec says it, but I would say the bus should
run at the speed of the slowest attached peripheral as they all have
to listen for the address-byte being sent at the start of each i2c
transaction.
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
next prev parent reply other threads:[~2016-01-04 9:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 21:19 [PATCH v2 0/2] i2c:dw: Add APM X-Gene ACPI I2C device support Loc Ho
2015-12-10 21:19 ` [PATCH v2 1/2] acpi:apd: " Loc Ho
2015-12-11 1:13 ` Ken Xue
2015-12-10 21:19 ` [PATCH v2 2/2] i2c:dw: " Loc Ho
2015-12-15 0:53 ` [PATCH v2 0/2] " Suravee Suthikulanit
2015-12-15 13:27 ` Mika Westerberg
2015-12-15 14:52 ` Suravee Suthikulpanit
2015-12-15 14:59 ` Mika Westerberg
2015-12-15 19:20 ` Loc Ho
2015-12-16 9:04 ` Mika Westerberg
2015-12-16 12:53 ` Jarkko Nikula
2015-12-23 9:34 ` Ken Xue
2015-12-23 9:52 ` Mika Westerberg
2015-12-23 9:59 ` Ken Xue
2015-12-23 10:17 ` Mika Westerberg
2015-12-23 10:02 ` Zheng, Ivan
2015-12-23 10:09 ` Mika Westerberg
2015-12-23 11:24 ` Zheng, Ivan
2015-12-23 11:40 ` Mika Westerberg
2016-01-04 9:09 ` Ben Dooks [this message]
2016-01-03 0:54 ` Rafael J. Wysocki
2016-01-04 6:23 ` Loc Ho
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=568A36D1.8070808@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=linux-arm-kernel@lists.infradead.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 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).