linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: Fabio Estevam <fabio.estevam-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org,
	ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org,
	kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org,
	w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org,
	shawn.guo-KZfg59tc24xl57MIdRCFDg@public.gmane.org
Subject: Re: [PATCH v2] i2c: mxs: Let i2c-mxs be built for MX23
Date: Fri, 21 Oct 2011 20:48:22 +0200	[thread overview]
Message-ID: <20111021184822.GJ15299@pengutronix.de> (raw)
In-Reply-To: <1319221664-3018-1-git-send-email-fabio.estevam-KZfg59tc24xl57MIdRCFDg@public.gmane.org>

On Fri, Oct 21, 2011 at 04:27:44PM -0200, Fabio Estevam wrote:
> MX23 and MX28 share the same I2C block, so let i2c-mxs be built for MX23 too.
> 
> Signed-off-by: Fabio Estevam <fabio.estevam-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
arch/arm/mach-mxs/devices/platform-mxs-i2c.c doesn't support i.MX23 yet,
but still I think the change is correct.

Acked-by: Uwe Kleine-König <u.kleine-koenig-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>

> ---
> Changes since v1:
> - Remove unneeded parenthesis
> 
>  drivers/i2c/busses/Kconfig |    6 +++---
>  1 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig
> index 646068e..08748db 100644
> --- a/drivers/i2c/busses/Kconfig
> +++ b/drivers/i2c/busses/Kconfig
> @@ -456,11 +456,11 @@ config I2C_MV64XXX
>  	  will be called i2c-mv64xxx.
>  
>  config I2C_MXS
> -	tristate "Freescale i.MX28 I2C interface"
> -	depends on SOC_IMX28
> +	tristate "Freescale i.MXS I2C interface"
> +	depends on SOC_IMX28 || SOC_IMX23
>  	help
>  	  Say Y here if you want to use the I2C bus controller on
> -	  the Freescale i.MX28 processors.
> +	  the Freescale i.MXS processors.
>  
>  	  This driver can also be built as a module.  If so, the module
>  	  will be called i2c-mxs.
> -- 
> 1.7.1
> 
> 
> 

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

  parent reply	other threads:[~2011-10-21 18:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-21 18:27 [PATCH v2] i2c: mxs: Let i2c-mxs be built for MX23 Fabio Estevam
     [not found] ` <1319221664-3018-1-git-send-email-fabio.estevam-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2011-10-21 18:48   ` Uwe Kleine-König [this message]
     [not found]     ` <20111021184822.GJ15299-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2011-10-21 18:59       ` Fabio Estevam
     [not found]         ` <4EA1C128.106-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2011-10-22 14:57           ` 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=20111021184822.GJ15299@pengutronix.de \
    --to=u.kleine-koenig-bicnvbalz9megne8c9+irq@public.gmane.org \
    --cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
    --cc=fabio.estevam-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
    --cc=kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
    --cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=shawn.guo-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
    --cc=w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.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).