linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Abraham <thomas.abraham@linaro.org>
To: devicetree-discuss@lists.ozlabs.org
Cc: linux-i2c@vger.kernel.org, grant.likely@secretlab.ca,
	ben-linux@fluff.org, linux-samsung-soc@vger.kernel.org
Subject: [PATCH v2 0/3] Add device tree support for Samsung's I2C driver
Date: Fri, 22 Jul 2011 15:48:35 +0530	[thread overview]
Message-ID: <1311329918-8105-1-git-send-email-thomas.abraham@linaro.org> (raw)

This patchset adds device tree support for Samsung's I2C driver. The
Exynos4 DT enabled machine is updated to support device tree based probe
for I2C instance 0 and 1.

Changes since v1:

- Addressed all comments from Grant Likely
    - s3c24xx_i2c_is2440 function is simpler now.
    - Consolidated all the scatterd dt support code into a single function.
    - but the dependency on i2c pinmux handler function passed from the
      platform data is retained. It would be removed eventually when the
      new pinmux api is finalized and the i2c driver is modified to
      support the pinmux settings using the pinmux api.

Thomas Abraham (3):
  i2c: s3c2410: Keep a copy of platform data and use it.
  i2c: s3c2410: Add device tree support
  arm: dt: Add device tree support for i2c instance 0 and 1 on exynos4 dt machine

 .../devicetree/bindings/i2c/samsung-i2c.txt        |   44 +++++++++++++++
 arch/arm/boot/dts/exynos4-smdkv310.dts             |   45 +++++++++++++++
 arch/arm/mach-exynos4/Kconfig                      |    2 +
 arch/arm/mach-exynos4/mach-exynos4-dt.c            |   23 ++++++++
 drivers/i2c/busses/i2c-s3c2410.c                   |   58 +++++++++++++++++++-
 5 files changed, 169 insertions(+), 3 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/i2c/samsung-i2c.txt

             reply	other threads:[~2011-07-22 10:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-22 10:18 Thomas Abraham [this message]
     [not found] ` <1311329918-8105-1-git-send-email-thomas.abraham-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2011-07-22 10:18   ` [PATCH v2 1/3] i2c: s3c2410: Keep a copy of platform data and use it Thomas Abraham
2011-07-22 10:18     ` [PATCH v2 2/3] i2c: s3c2410: Add device tree support Thomas Abraham
2011-07-22 10:18       ` [PATCH v2 3/3] arm: dt: Add device tree support for i2c instance 0 and 1 on exynos4 dt machine Thomas Abraham
2011-07-31  3:55         ` Grant Likely
     [not found]           ` <20110731035536.GI24334-e0URQFbLeQY2iJbIjFUEsiwD8/FfD2ys@public.gmane.org>
2011-07-31 21:02             ` Thomas Abraham
2011-07-31  3:53       ` [PATCH v2 2/3] i2c: s3c2410: Add device tree support Grant Likely
2011-07-31 20:50         ` Thomas Abraham
2011-07-31  3:51     ` [PATCH v2 1/3] i2c: s3c2410: Keep a copy of platform data and use it Grant Likely
2011-07-31 20:33       ` Thomas Abraham
2011-07-27 22:06 ` [PATCH v2 0/3] Add device tree support for Samsung's I2C driver Ben Dooks

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=1311329918-8105-1-git-send-email-thomas.abraham@linaro.org \
    --to=thomas.abraham@linaro.org \
    --cc=ben-linux@fluff.org \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.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).