From: jason77.wang@gmail.com (jason)
To: linux-arm-kernel@lists.infradead.org
Subject: [V3 3/7] mx51/iomux: fix some pad names and make some cleanups
Date: Sat, 05 Jun 2010 08:54:47 +0800 [thread overview]
Message-ID: <4C09A057.4090201@gmail.com> (raw)
In-Reply-To: <20100604151307.GD2982@matterhorn.lan>
Amit Kucheria wrote:
> On 10 Jun 04, Jason Wang wrote:
>
>> Fix some pad names according to the naming convention and make some
>> cleanups for vertical lineup.
>>
>> Signed-off-by: Jason Wang <jason77.wang@gmail.com>
>> ---
>> arch/arm/plat-mxc/include/mach/iomux-mx51.h | 507 ++++++++++++--------------
>> 1 files changed, 234 insertions(+), 273 deletions(-)
>>
>> diff --git a/arch/arm/plat-mxc/include/mach/iomux-mx51.h b/arch/arm/plat-mxc/include/mach/iomux-mx51.h
>> index ab0f95d..df9ecdf 100644
>> --- a/arch/arm/plat-mxc/include/mach/iomux-mx51.h
>> +++ b/arch/arm/plat-mxc/include/mach/iomux-mx51.h
>> @@ -57,278 +57,239 @@ typedef enum iomux_config {
>>
>> /* PAD MUX ALT INPSE PATH PADCTRL */
>>
>> -#define MX51_PAD_GPIO_2_0__EIM_D16 IOMUX_PAD(0x3f0, 0x05c, 1, 0x0, 0, NO_PAD_CTRL)
>> -#define MX51_PAD_GPIO_2_1__EIM_D17 IOMUX_PAD(0x3f4, 0x060, 1, 0x0, 0, NO_PAD_CTRL)
>>
> <snip>
>
> Did you try compiling this? It fails to compile both babbage and 3ds boards.
>
> This breaks the babbage board because a pad name was changed here. (An
> underscore between GPIO and 1)
>
> arch/arm/mach-mx5/board-mx51_babbage.c:81: error:
> 'MX51_PAD_GPIO_1_7__GPIO1_7' undeclared here (not in a function)
> arch/arm/mach-mx5/board-mx51_babbage.c: In function 'initialize_otg_port':
>
> For 3ds, the errors are:
> arch/arm/mach-mx5/board-mx51_3ds.c:44: error: 'MX51_PAD_UART3_RXD__UART3_RXD'
> undeclared here (not in a function)
> arch/arm/mach-mx5/board-mx51_3ds.c:45: error: 'MX51_PAD_UART3_TXD__UART3_TXD'
> undeclared here (not in a function)
> arch/arm/mach-mx5/board-mx51_3ds.c:50: error: 'MX51_PAD_GPIO_1_6__GPIO1_6'
> undeclared here (not in a function)
>
> Perhaps you should wait till Sascha pulls in either of our patches to fixup
> the padnames first.
>
>
Sorry, this is because just before i send V3, i make some changes for
iomux-mx51.h in a hurry
and didn't make building test after change this part.
Take your advice.
Thanks,
Jason.
> Cheers,
> Amit
>
next prev parent reply other threads:[~2010-06-05 0:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 14:09 [V3 0/7]Add i.MX51 3-stack board support Jason Wang
2010-06-04 14:09 ` [V3 1/7] mxc: add common debug board for 3-stack platforms Jason Wang
2010-06-04 14:09 ` [V3 2/7] mxc/iomux: add GPIO bank offset for iomux v3 platforms Jason Wang
2010-06-04 14:09 ` [V3 3/7] mx51/iomux: fix some pad names and make some cleanups Jason Wang
2010-06-04 14:09 ` [V3 4/7] mx51/iomux: add pad definition for mx51_3ds Jason Wang
2010-06-04 14:09 ` [V3 5/7] mxc/mx51: Add support for the imx51 3-stack board Jason Wang
2010-06-04 14:09 ` [V3 6/7] mx51/keypad: add keypad support for i.MX51 platforms Jason Wang
2010-06-04 14:09 ` [V3 7/7] mx31_3ds: revert cpld debug board relate code Jason Wang
2010-06-04 15:13 ` [V3 3/7] mx51/iomux: fix some pad names and make some cleanups Amit Kucheria
2010-06-05 0:54 ` jason [this message]
2010-06-04 14:48 ` [V3 0/7]Add i.MX51 3-stack board support Amit Kucheria
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=4C09A057.4090201@gmail.com \
--to=jason77.wang@gmail.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).