linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: S3C64XX: Hook up carrier class modules on Cragganmore
Date: Mon, 14 May 2012 18:20:41 +0100	[thread overview]
Message-ID: <1337016041-16096-2-git-send-email-broonie@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1337016041-16096-1-git-send-email-broonie@opensource.wolfsonmicro.com>

We now have an additional classs of modules which are enumerated at I2C
address 0x22. Add hookup for these modules.

Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
---
 arch/arm/mach-s3c64xx/mach-crag6410.c |    1 +
 1 file changed, 1 insertion(+)

diff --git a/arch/arm/mach-s3c64xx/mach-crag6410.c b/arch/arm/mach-s3c64xx/mach-crag6410.c
index 0787b91..48eb76f 100644
--- a/arch/arm/mach-s3c64xx/mach-crag6410.c
+++ b/arch/arm/mach-s3c64xx/mach-crag6410.c
@@ -674,6 +674,7 @@ static struct i2c_board_info i2c_devs1[] __initdata = {
 	  .platform_data = &glenfarclas_pmic_pdata },
 
 	{ I2C_BOARD_INFO("wlf-gf-module", 0x20) },
+	{ I2C_BOARD_INFO("wlf-gf-module", 0x22) },
 	{ I2C_BOARD_INFO("wlf-gf-module", 0x24) },
 	{ I2C_BOARD_INFO("wlf-gf-module", 0x25) },
 	{ I2C_BOARD_INFO("wlf-gf-module", 0x26) },
-- 
1.7.10

  reply	other threads:[~2012-05-14 17:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-14 17:20 [PATCH 1/2] ARM: S3C64XX: Initial hookup for Bells module on Cragganmore Mark Brown
2012-05-14 17:20 ` Mark Brown [this message]
2012-05-15  8:58   ` [PATCH 2/2] ARM: S3C64XX: Hook up carrier class modules " Kukjin Kim
2012-05-15 17:37     ` Mark Brown
2012-05-16  6:21       ` Kukjin Kim
2012-05-15  8:58 ` [PATCH 1/2] ARM: S3C64XX: Initial hookup for Bells module " Kukjin Kim

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=1337016041-16096-2-git-send-email-broonie@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --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).