All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikolay Dimitrov <picmaster@mail.bg>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V6] ARM: mx6: Add support for Kosagi Novena
Date: Sat, 11 Oct 2014 09:39:48 +0300	[thread overview]
Message-ID: <5438D0B4.3070505@mail.bg> (raw)
In-Reply-To: <201410110324.24757.marex@denx.de>

Hi Marek,

On 10/11/2014 04:24 AM, Marek Vasut wrote:
> On Friday, October 10, 2014 at 03:39:08 AM, Nikolay Dimitrov wrote:
>> Hi Marek,
>>
>> The usual stuff follows :D.
>>
>> On 10/10/2014 02:22 AM, Marek Vasut wrote:
>>> +#define NOVENA_BUTTON_GPIO	IMX_GPIO_NR(4, 14)
>>> +#define NOVENA_SD_WP		IMX_GPIO_NR(1, 2)
>>> +#define NOVENA_SD_CD		IMX_GPIO_NR(1, 4)
>>
>> NOVENA_BUTTON_GPIO is initialized as input in this source file, but the
>> NOVENA_SD_WP and NOVENA_SD_CD are not. They're initialized only in
>> novena_spl.c, and if you change the SPL configuration, they won't be
>> explicitly initialized.
>>
>> While by pure luck the iomuxc reset values are those of the GPIO pins, I
>> would vote for explicit initialization of WP & CD.
>>
>> And btw, it's cool that you added the WP pin, I totally missed this out
>> last time I was staring at the schematic.
>
> I disagree that doing the initialization of pinmux twice is necessary,
> the SPL will always run before the rest of the software, so it will do
> the pinmux init. If you mean GPIO direction, then that's done in V7.

I also agree that there's no need to pinmux twice. And yes, what I meant 
was to set the WP/CD GPIOs pin directions, so thanks for fixing that.

Regards,
Nikolay

      reply	other threads:[~2014-10-11  6:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-09 23:22 [U-Boot] [PATCH V6] ARM: mx6: Add support for Kosagi Novena Marek Vasut
2014-10-10  1:39 ` Nikolay Dimitrov
2014-10-11  1:24   ` Marek Vasut
2014-10-11  6:39     ` Nikolay Dimitrov [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=5438D0B4.3070505@mail.bg \
    --to=picmaster@mail.bg \
    --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.