linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Eric Miao <eric.y.miao@gmail.com>
Cc: Amit Kucheria <amit.kucheria@canonical.com>,
	List Linux Kernel <linux-kernel@vger.kernel.org>,
	linux@arm.linux.org.uk, Dinh.Nguyen@freescale.com,
	grant.likely@secretlab.ca, r.herring@freescale.com,
	linux-arm-kernel@lists.infradead.org, daniel@caiaq.de,
	bryan.wu@canonical.com, valentin.longchamp@epfl.ch
Subject: Re: [PATCHv2 03/11] mxc: Fix Drive Strength Field in the IOMUX controller
Date: Wed, 3 Feb 2010 10:40:16 +0100	[thread overview]
Message-ID: <20100203094016.GL6130@pengutronix.de> (raw)
In-Reply-To: <f17812d71002022229g4daef16fhe398c7bd76bad8e2@mail.gmail.com>

On Tue, Feb 02, 2010 at 10:29:50PM -0800, Eric Miao wrote:
> On Tue, Feb 2, 2010 at 9:16 PM, Amit Kucheria
> <amit.kucheria@canonical.com> wrote:
> > i.MX51 defines 4 values:
> >
> > 00: Low Drive Strength
> > 01: Medium Drive Strength
> > 10: High Drive Strength
> > 11: Max Drive Strength
> >
> > Signed-off-by: Amit Kucheria <amit.kucheria@canonical.com>
> > ---
> >  arch/arm/plat-mxc/include/mach/iomux-v3.h |    8 +++++---
> >  1 files changed, 5 insertions(+), 3 deletions(-)
> >
> > diff --git a/arch/arm/plat-mxc/include/mach/iomux-v3.h b/arch/arm/plat-mxc/include/mach/iomux-v3.h
> > index 1deda01..f2f73d3 100644
> > --- a/arch/arm/plat-mxc/include/mach/iomux-v3.h
> > +++ b/arch/arm/plat-mxc/include/mach/iomux-v3.h
> > @@ -81,11 +81,13 @@ struct pad_desc {
> >
> >  #define PAD_CTL_ODE                    (1 << 3)
> >
> > -#define PAD_CTL_DSE_STANDARD           (0 << 1)
> > -#define PAD_CTL_DSE_HIGH               (1 << 1)
> > -#define PAD_CTL_DSE_MAX                        (2 << 1)
> > +#define PAD_CTL_DSE_LOW                        (0 << 1)
> > +#define PAD_CTL_DSE_MED                        (1 << 1)
> > +#define PAD_CTL_DSE_HIGH               (2 << 1)
> > +#define PAD_CTL_DSE_MAX                        (3 << 1)
> >
> 
> I'm seeing some changes in recent kernel with introduction of PAD_CTL_DRV_*,
> which also affects mx3, think it's a tough problem to keep backward
> compatibility
> now, one way out is to introduce maybe PAD_CTL_DRV_EXTREME specifically
> for imx51.

Given that the values are the same on i.MX3 and i.MX51 we could also
do a

#define PAD_CTL_DSE(x)	((x) << 1)

and add a comment for allowed values 0..2 for i.MX3 and 0..3 for i.MX51.

Sascha


-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2010-02-03  9:40 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-03  5:16 [PATCHv2 00/11] Base support for Freescale i.MX51 SoC platform Amit Kucheria
     [not found] ` <cover.1265173480.git.amit.kucheria@canonical.com>
2010-02-03  5:16   ` [PATCHv2 01/11] arm: mxc: TrustZone interrupt controller (TZIC) for i.MX5 family Amit Kucheria
2010-02-03  6:23     ` Eric Miao
2010-02-03  9:45       ` Sascha Hauer
2010-02-03 13:24       ` Amit Kucheria
2010-02-03 15:09         ` Eric Miao
2010-02-04  0:54           ` Eric Miao
2010-02-04 17:09         ` Nguyen Dinh-R00091
2010-02-03  5:16   ` [PATCHv2 02/11] mxc timer: refactor timer code to use timer versions Amit Kucheria
2010-02-03 16:23     ` Grant Likely
2010-02-03  5:16   ` [PATCHv2 03/11] mxc: Fix Drive Strength Field in the IOMUX controller Amit Kucheria
2010-02-03  6:29     ` Eric Miao
2010-02-03  9:40       ` Sascha Hauer [this message]
2010-02-03 16:27     ` Grant Likely
2010-02-04  0:25       ` Amit Kucheria
2010-02-03  5:16   ` [PATCHv2 04/11] mxc: changes to common plat-mxc code to add support for i.MX5 Amit Kucheria
2010-02-03  6:43     ` Eric Miao
2010-02-03  9:49       ` Sascha Hauer
2010-02-03 13:38         ` Amit Kucheria
2010-02-03 15:16           ` Eric Miao
2010-02-03 16:35     ` Grant Likely
2010-02-03  5:16   ` [PATCHv2 05/11] mxc: Core support for i.MX5 series of processors from Freescale Amit Kucheria
2010-02-03  7:03     ` Eric Miao
2010-02-03 14:20       ` Amit Kucheria
2010-02-03  9:24     ` Russell King - ARM Linux
2010-02-03 11:04     ` Sascha Hauer
2010-02-03 20:07       ` Amit Kucheria
2010-02-03 16:08     ` Rabin Vincent
2010-02-03  5:16   ` [PATCHv2 06/11] mxc: enable support for Freescale i.MX5 series of processors Amit Kucheria
2010-02-03  5:16   ` [PATCHv2 07/11] mxc: Add support for the Babbage board Amit Kucheria
2010-02-03 11:10     ` Sascha Hauer
2010-02-03  5:16   ` [PATCHv2 08/11] fec: fix uninitialized rx buffer usage Amit Kucheria
2010-02-03 16:46     ` Grant Likely
2010-02-03 18:33       ` Amit Kucheria
2010-02-03 18:38         ` Grant Likely
2010-02-03 20:23           ` Grant Likely
2010-02-03  5:16   ` [PATCHv2 09/11] fec: Add LAN8700 phy support Amit Kucheria
2010-02-03  5:16   ` [PATCHv2 10/11] fec: Add ARCH_MX5 as a dependency Amit Kucheria
2010-02-03  5:16   ` [PATCHv2 11/11] mxc: Add imx51_defconfig Amit Kucheria
2010-02-05  6:48     ` Sascha Hauer

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=20100203094016.GL6130@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=Dinh.Nguyen@freescale.com \
    --cc=amit.kucheria@canonical.com \
    --cc=bryan.wu@canonical.com \
    --cc=daniel@caiaq.de \
    --cc=eric.y.miao@gmail.com \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=r.herring@freescale.com \
    --cc=valentin.longchamp@epfl.ch \
    /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).