From: Shinya Kuribayashi <skuribay-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
To: mika.westerberg-VuQAYsv1563Yd54FQh9/CA@public.gmane.org
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org,
christian.ruppert-ux6zf3SgZrrQT0dZR+AlfA@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2 1/2] i2c-designware: make HCNT/LCNT values configurable
Date: Mon, 19 Aug 2013 21:40:40 +0900 [thread overview]
Message-ID: <52121248.2090000@pobox.com> (raw)
In-Reply-To: <1376914074-31103-1-git-send-email-mika.westerberg-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
On 8/19/13 9:07 PM, Mika Westerberg wrote:
> The DesignWare I2C controller has high count (HCNT) and low count (LCNT)
> registers for each of the I2C speed modes (standard and fast). These
> registers are programmed based on the input clock speed in the driver.
>
> The current code calculates these values based on the input clock speed and
> tries hard to meet the I2C bus timing requirements. This could result
> non-optimal values with regarding to the bus speed. For example on Intel
> BayTrail we get bus speed of 315.41kHz which is ~20% slower than we would
> expect (400kHz) in fast mode (even though the timing requirements are met).
>
> This patch makes it possible for the platform code to pass more optimal
> HCNT/LCNT values to the core driver if they are known beforehand. If these
> are not set we use the calculated and more conservative values.
>
> Signed-off-by: Mika Westerberg <mika.westerberg-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Looks good, thanks.
Acked-by: Shinya Kuribayashi <skuribay-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
WARNING: multiple messages have this Message-ID (diff)
From: Shinya Kuribayashi <skuribay@pobox.com>
To: mika.westerberg@linux.intel.com
Cc: linux-kernel@vger.kernel.org, wsa@the-dreams.de,
christian.ruppert@abilis.com, linux-i2c@vger.kernel.org
Subject: Re: [PATCH v2 1/2] i2c-designware: make HCNT/LCNT values configurable
Date: Mon, 19 Aug 2013 21:40:40 +0900 [thread overview]
Message-ID: <52121248.2090000@pobox.com> (raw)
In-Reply-To: <1376914074-31103-1-git-send-email-mika.westerberg@linux.intel.com>
On 8/19/13 9:07 PM, Mika Westerberg wrote:
> The DesignWare I2C controller has high count (HCNT) and low count (LCNT)
> registers for each of the I2C speed modes (standard and fast). These
> registers are programmed based on the input clock speed in the driver.
>
> The current code calculates these values based on the input clock speed and
> tries hard to meet the I2C bus timing requirements. This could result
> non-optimal values with regarding to the bus speed. For example on Intel
> BayTrail we get bus speed of 315.41kHz which is ~20% slower than we would
> expect (400kHz) in fast mode (even though the timing requirements are met).
>
> This patch makes it possible for the platform code to pass more optimal
> HCNT/LCNT values to the core driver if they are known beforehand. If these
> are not set we use the calculated and more conservative values.
>
> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Looks good, thanks.
Acked-by: Shinya Kuribayashi <skuribay@pobox.com>
next prev parent reply other threads:[~2013-08-19 12:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 12:07 [PATCH v2 1/2] i2c-designware: make HCNT/LCNT values configurable Mika Westerberg
2013-08-19 12:07 ` Mika Westerberg
2013-08-19 12:07 ` [PATCH v2 2/2] i2c-designware: get SDA hold time, HCNT and LCNT configuration from ACPI Mika Westerberg
[not found] ` <1376914074-31103-2-git-send-email-mika.westerberg-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2013-08-28 9:10 ` Wolfram Sang
2013-08-28 9:10 ` Wolfram Sang
[not found] ` <1376914074-31103-1-git-send-email-mika.westerberg-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2013-08-19 12:40 ` Shinya Kuribayashi [this message]
2013-08-19 12:40 ` [PATCH v2 1/2] i2c-designware: make HCNT/LCNT values configurable Shinya Kuribayashi
2013-08-28 9:10 ` Wolfram Sang
2013-08-28 9:10 ` Wolfram Sang
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=52121248.2090000@pobox.com \
--to=skuribay-e+axbwqsrlaavxtiumwx3w@public.gmane.org \
--cc=christian.ruppert-ux6zf3SgZrrQT0dZR+AlfA@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mika.westerberg-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
--cc=wsa-z923LK4zBo2bacvFa/9K2g@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.