From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2 V3] MXS: Set I2C timing registers for mxs-i2c
Date: Sun, 10 Jun 2012 13:53:05 +0200 [thread overview]
Message-ID: <201206101353.06018.marex@denx.de> (raw)
In-Reply-To: <1339242351-8797-1-git-send-email-marex@denx.de>
Dear Marek Vasut,
> This patch configures the I2C bus timing registers according
> to information passed via DT. Currently, 100kHz and 400kHz
> modes are supported.
[...]
> +struct mxs_i2c_speed_config {
> + uint32_t timing0;
> + uint32_t timing1;
> + uint32_t timing2;
> +};
> +
> +/* Timing values for the default 24MHz clock supplied into the i2c block.
Thinking about these further -- does anyone have any idea how these numbers were
derived? And possibly even formula for that?
And maybe we should somehow make sure the source runs on 24MHz (how?).
> */ +const struct mxs_i2c_speed_config mxs_i2c_95kHz_config = {
> + .timing0 = 0x00780030,
> + .timing1 = 0x00800030,
> + .timing2 = 0x0015000d,
> +};
> +
> +const struct mxs_i2c_speed_config mxs_i2c_400kHz_config = {
> + .timing0 = 0x000f0007,
> + .timing1 = 0x001f000f,
> + .timing2 = 0x0015000d,
> +};
[...]
Best regards,
Marek Vasut
next prev parent reply other threads:[~2012-06-10 11:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-09 11:45 [PATCH 1/2 V3] MXS: Set I2C timing registers for mxs-i2c Marek Vasut
2012-06-09 11:45 ` [PATCH 2/2 V2] MXS: Implement DMA support into mxs-i2c Marek Vasut
2012-06-10 11:53 ` Marek Vasut [this message]
2012-06-11 7:30 ` [PATCH 1/2 V3] MXS: Set I2C timing registers for mxs-i2c Shawn Guo
2012-06-11 10:53 ` Marek Vasut
2012-06-11 14:42 ` Shawn Guo
2012-06-23 18:19 ` Marek Vasut
2012-06-11 6:39 ` Shawn Guo
2012-06-11 10:54 ` Marek Vasut
2012-06-27 1:30 ` Marek Vasut
2012-06-27 2:13 ` Shawn Guo
2012-06-27 2:34 ` Marek Vasut
2012-06-23 18:47 ` Marek Vasut
2012-06-25 15:43 ` Shawn Guo
2012-06-25 16:02 ` Marek Vasut
2012-06-27 1:15 ` Marek Vasut
-- strict thread matches above, loose matches on Subject: below --
2012-07-09 16:22 Marek Vasut
2012-07-13 8:07 ` 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=201206101353.06018.marex@denx.de \
--to=marex@denx.de \
--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).