From: ben.dooks@codethink.co.uk (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] MXS: Set I2C timing registers for mxs-i2c
Date: Mon, 28 May 2012 11:55:56 +0100 [thread overview]
Message-ID: <4FC359BC.8080606@codethink.co.uk> (raw)
In-Reply-To: <1338084656-11961-1-git-send-email-marex@denx.de>
On 27/05/12 03:10, Marek Vasut wrote:
> This patch configures the I2C bus timing registers according
> to information passed via DT. Currently, 100kHz and 400kHz
> modes are supported.
>
> Signed-off-by: Marek Vasut<marex@denx.de>
> Cc: Detlev Zundel<dzu@denx.de>
> CC: Dong Aisheng<b29396@freescale.com>
> CC: Fabio Estevam<fabio.estevam@freescale.com>
> Cc: Linux ARM kernel<linux-arm-kernel@lists.infradead.org>
> Cc: linux-i2c at vger.kernel.org
> CC: Sascha Hauer<s.hauer@pengutronix.de>
> CC: Shawn Guo<shawn.guo@linaro.org>
> Cc: Stefano Babic<sbabic@denx.de>
> CC: Uwe Kleine-K?nig<u.kleine-koenig@pengutronix.de>
> Cc: Wolfgang Denk<wd@denx.de>
> Cc: Wolfram Sang<w.sang@pengutronix.de>
> ---
> Documentation/devicetree/bindings/i2c/i2c-mxs.txt | 1 +
> arch/arm/boot/dts/imx28.dtsi | 2 +
> drivers/i2c/busses/i2c-mxs.c | 64 +++++++++++++++++++++
> 3 files changed, 67 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/i2c/i2c-mxs.txt b/Documentation/devicetree/bindings/i2c/i2c-mxs.txt
> index 1bfc02d..790b5c6 100644
> --- a/Documentation/devicetree/bindings/i2c/i2c-mxs.txt
> +++ b/Documentation/devicetree/bindings/i2c/i2c-mxs.txt
> @@ -4,6 +4,7 @@ Required properties:
> - compatible: Should be "fsl,<chip>-i2c"
> - reg: Should contain registers location and length
> - interrupts: Should contain ERROR and DMA interrupts
> +- speed: Speed of the bus in kHz (400 or 100 are supported)
>
> Examples:
>
> diff --git a/arch/arm/boot/dts/imx28.dtsi b/arch/arm/boot/dts/imx28.dtsi
> index 4634cb8..d927155 100644
> --- a/arch/arm/boot/dts/imx28.dtsi
> +++ b/arch/arm/boot/dts/imx28.dtsi
> @@ -381,6 +381,7 @@
> compatible = "fsl,imx28-i2c";
> reg =<0x80058000 2000>;
> interrupts =<111 68>;
> + fsl,speed =<400>;
> status = "disabled";
> };
>
> @@ -390,6 +391,7 @@
> compatible = "fsl,imx28-i2c";
> reg =<0x8005a000 2000>;
> interrupts =<110 69>;
> + fsl,speed =<400>;
> status = "disabled";
> };
Is there not a standard speed setting in the i2c binding?
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
next prev parent reply other threads:[~2012-05-28 10:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-27 2:10 [PATCH 1/2] MXS: Set I2C timing registers for mxs-i2c Marek Vasut
2012-05-27 2:10 ` [PATCH 2/2] MXS: Implement DMA support into mxs-i2c Marek Vasut
2012-06-06 3:47 ` Shawn Guo
2012-05-28 10:55 ` Ben Dooks [this message]
2012-05-29 6:46 ` [PATCH 1/2] MXS: Set I2C timing registers for mxs-i2c Marek Vasut
2012-06-02 6:48 ` Wolfram Sang
2012-06-06 2:53 ` Shawn Guo
-- strict thread matches above, loose matches on Subject: below --
2012-06-29 8:24 Marek Vasut
2012-06-29 9:06 ` Dong Aisheng
2012-06-29 9:33 ` Marek Vasut
2012-06-29 9:39 ` Dong Aisheng
2012-06-29 10:03 ` Marek Vasut
2012-06-29 11:47 ` Shawn Guo
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=4FC359BC.8080606@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).