From mboxrd@z Thu Jan  1 00:00:00 1970
From: Marek Vasut <marex@denx.de>
Date: Fri, 3 May 2013 04:34:11 +0200
Subject: [U-Boot] [PATCH v3 1/7] mx23: Fix pad voltage selection bit
In-Reply-To: <CAP9ODKpkJ3+O-1MFKyvVWDx1X7UvC3YOw=per3vgyG3TG13S5A@mail.gmail.com>
References: <1367534661-13502-1-git-send-email-festevam@gmail.com>
	<201305030424.10150.marex@denx.de>
	<CAP9ODKpkJ3+O-1MFKyvVWDx1X7UvC3YOw=per3vgyG3TG13S5A@mail.gmail.com>
Message-ID: <201305030434.11447.marex@denx.de>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Dear Otavio Salvador,

> On Thu, May 2, 2013 at 11:24 PM, Marek Vasut <marex@denx.de> wrote:
> > Dear Fabio Estevam,
> > 
> >> From: Fabio Estevam <fabio.estevam@freescale.com>
> >> 
> >> On mx23 the pad voltage selection bit needs to be always '0', since '1'
> >> is a reserved value.
> >> 
> >> For example:
> >> 
> >> Pin 108, EMI_A06 pin voltage selection:
> >> 0= 1.8V (mDDR) or 2.5V (DDR1);
> >> 1= reserved.
> >> 
> >> Fix the pad voltage definitions for the mx23 case.
> >> 
> >> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
> > 
> > Acked-by: Marek Vasut <marex@denx.de>
> > 
> > but then, should we not just undefine this PAD_3V3 for MX23 altogether so
> > noone is tempted to use it?
> 
> I think for code readability it'd be good to have it in place. It
> makes it more obvious for people looking at code.

I can already see the people wondering why that piece has no effect ...

Best regards,
Marek Vasut