From: w.sang@pengutronix.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] I2C: Set I2C timing registers for mxs-i2c
Date: Mon, 30 Apr 2012 23:02:22 +0200 [thread overview]
Message-ID: <20120430210222.GF28226@pengutronix.de> (raw)
In-Reply-To: <201204302247.17242.marex@denx.de>
> Indeed. Default to 100kHz might be a good idea too, in case user entered some
> weird value. Eventually, it'd be nice if we could calculate the timing values
> for all possible frequencies, but I didn't got to deriving such formula ...
> dunno if it's worth it either, doubt so.
Would be awesome to have it; but we can leave it for later when it is
actually needed.
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120430/904f919e/attachment.sig>
prev parent reply other threads:[~2012-04-30 21:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-29 22:36 [PATCH 1/2] I2C: Set I2C timing registers for mxs-i2c Marek Vasut
2012-04-29 22:36 ` [PATCH 2/2] I2C: Implement DMA support into mxs-i2c Marek Vasut
2012-04-30 6:05 ` Wolfram Sang
2012-04-30 12:10 ` Marek Vasut
2012-04-30 19:52 ` Wolfram Sang
2012-04-30 20:07 ` Marek Vasut
2012-04-30 20:30 ` Wolfram Sang
2012-04-30 20:45 ` Marek Vasut
2012-04-30 21:01 ` Wolfram Sang
2012-04-30 21:19 ` Marek Vasut
2012-05-01 13:58 ` Shawn Guo
2012-05-01 14:02 ` Marek Vasut
2012-05-01 14:09 ` Shawn Guo
2012-05-01 14:14 ` Marek Vasut
2012-05-01 14:37 ` Russell King - ARM Linux
2012-04-30 5:58 ` [PATCH 1/2] I2C: Set I2C timing registers for mxs-i2c Wolfram Sang
2012-04-30 12:05 ` Marek Vasut
2012-04-30 19:43 ` Wolfram Sang
2012-04-30 20:09 ` Marek Vasut
2012-04-30 20:27 ` Wolfram Sang
2012-04-30 20:47 ` Marek Vasut
2012-04-30 21:02 ` Wolfram Sang [this message]
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=20120430210222.GF28226@pengutronix.de \
--to=w.sang@pengutronix.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).