From: Vikram Narayanan <vikram186@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Add initial support for mx6slevk board
Date: Tue, 02 Apr 2013 08:40:54 +0530 [thread overview]
Message-ID: <515A4C3E.8000401@gmail.com> (raw)
In-Reply-To: <CAOMZO5Bg4--ow4e_p+kSQv-JzJQ1mPZAa33TV+cNPjsgsigH+g@mail.gmail.com>
On 4/2/2013 3:45 AM, Fabio Estevam wrote:
> On Mon, Apr 1, 2013 at 2:44 PM, Fabio Estevam <festevam@gmail.com> wrote:
>> On Mon, Apr 1, 2013 at 2:26 PM, Vikram Narayanan <vikram186@gmail.com> wrote:
>>
>>> Is the above same for all the variants of i.Mx?
>>> Can we put this into a common header file?
>>
>> Ok, I can try to put this into a common location.
>>
>>>> +#define IOMUX_CONFIG_SION 0x10
>>>> +#define NO_MUX_I 0
>>>> +#define NO_PAD_I 0
>>>> +enum {
>>>> + MX6_PAD_AUD_MCLK__AUDMUX_AUDIO_CLK_OUT =
>>>> IOMUX_PAD(0x02A4, 0x004C, 0, 0x0000, 0, 0),
>>>> + MX6_PAD_AUD_MCLK__PWM4_PWMO =
>>>> IOMUX_PAD(0x02A4, 0x004C, 1, 0x0000, 0, 0),
>>>> + MX6_PAD_AUD_MCLK__ECSPI3_RDY =
>>>> IOMUX_PAD(0x02A4, 0x004C, 2, 0x06B4, 0, 0),
>>>> + MX6_PAD_AUD_MCLK__FEC_MDC =
>>>> IOMUX_PAD(0x02A4, 0x004C, 3, 0x0000, 0, 0),
>>>
>>>
>>> Is the mx6slevk using all the pins defined here?
>>
>> No, I put all pins for completion.
>
> I meant completeness, here.
>
>>> If not please take off the unused IOMUX pins so that we don't add dead code.
>>
>> I thought it was common practice to provide the complete IOMUX pin file.
>
> Looking at mx6q_pins.h I see that the IOMUX table is complete, but
> mx6dl_pins.h is not, so just want to get a confirmation first before
> doing v2.
Please refer the mx6dl discussion here.
http://www.mail-archive.com/u-boot at lists.denx.de/msg94194.html
It was Troy's idea, to include only the necessary pins.
Regards,
Vikram
prev parent reply other threads:[~2013-04-02 3:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-30 21:08 [U-Boot] [PATCH] Add initial support for mx6slevk board Fabio Estevam
2013-03-31 6:39 ` Dirk Behme
2013-03-31 22:38 ` Fabio Estevam
2013-04-01 17:26 ` Vikram Narayanan
2013-04-01 17:44 ` Fabio Estevam
2013-04-01 22:15 ` Fabio Estevam
2013-04-02 3:10 ` Vikram Narayanan [this message]
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=515A4C3E.8000401@gmail.com \
--to=vikram186@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.