From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mx6: Make pad name macro consistent with the datasheet
Date: Sat, 16 Jun 2012 00:22:20 +0200 [thread overview]
Message-ID: <201206160022.20700.marex@denx.de> (raw)
In-Reply-To: <4FDB3D49.4030302@gmail.com>
Dear Ashok,
> Use the same name as defined in the datasheet.
> DSP_CLK -> DISP_CLK
>
> Signed-off-by: Ashok Kumar Reddy Kourla <ashokkourla2000@gmail.com>
Acked-by: Marek Vasut <marex@denx.de>
> ---
> arch/arm/include/asm/arch-mx6/mx6x_pins.h | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/include/asm/arch-mx6/mx6x_pins.h
> b/arch/arm/include/asm/arch-mx6/mx6x_pins.h index afaa068..377d97f 100644
> --- a/arch/arm/include/asm/arch-mx6/mx6x_pins.h
> +++ b/arch/arm/include/asm/arch-mx6/mx6x_pins.h
> @@ -530,8 +530,8 @@ enum {
> MX6Q_PAD_EIM_BCLK__IPU1_DI1_PIN16 = IOMUX_PAD(0x046C, 0x0158, 1,
0x0000,
> 0, 0), MX6Q_PAD_EIM_BCLK__GPIO_6_31 = IOMUX_PAD(0x046C, 0x0158, 5,
> 0x0000, 0, 0), MX6Q_PAD_EIM_BCLK__TPSMP_HDATA_31 = IOMUX_PAD(0x046C,
> 0x0158, 6, 0x0000, 0, 0), - MX6Q_PAD_DI0_DISP_CLK__IPU1_DI0_DSP_CLK =
> IOMUX_PAD(0x0470, 0x015C, 0, 0x0000, 0, 0),
> - MX6Q_PAD_DI0_DISP_CLK__IPU2_DI0_DSP_CLK = IOMUX_PAD(0x0470, 0x015C, 1,
> 0x0000, 0, 0), + MX6Q_PAD_DI0_DISP_CLK__IPU1_DI0_DISP_CLK =
> IOMUX_PAD(0x0470, 0x015C, 0, 0x0000, 0, 0),
> + MX6Q_PAD_DI0_DISP_CLK__IPU2_DI0_DISP_CLK = IOMUX_PAD(0x0470, 0x015C, 1,
> 0x0000, 0, 0), MX6Q_PAD_DI0_DISP_CLK__MIPI_CR_DPY_OT28 = IOMUX_PAD(0x0470,
> 0x015C, 3, 0x0000, 0, 0), MX6Q_PAD_DI0_DISP_CLK__SDMA_DBG_CR_STA0 =
> IOMUX_PAD(0x0470, 0x015C, 4, 0x0000, 0, 0),
> MX6Q_PAD_DI0_DISP_CLK__GPIO_4_16 = IOMUX_PAD(0x0470, 0x015C, 5, 0x0000,
0,
> 0),
Best regards,
Marek Vasut
next prev parent reply other threads:[~2012-06-15 22:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 13:48 [U-Boot] [PATCH] mx6: Make pad name macro consistent with the datasheet Ashok
2012-06-15 22:22 ` Marek Vasut [this message]
2012-07-07 16:54 ` Stefano Babic
2012-07-11 6:39 ` Dirk Behme
2012-07-18 5:23 ` Stefano Babic
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=201206160022.20700.marex@denx.de \
--to=marex@denx.de \
--cc=u-boot@lists.denx.de \
/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