From: Troy Kisky <troy.kisky@boundarydevices.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] nitrogen6x: Fix the PAD settings for the ECSPI chipselect
Date: Sun, 13 Apr 2014 15:08:12 -0700 [thread overview]
Message-ID: <534B0ACC.2060509@boundarydevices.com> (raw)
In-Reply-To: <5349C429.8030805@boundarydevices.com>
On 4/12/2014 3:54 PM, Eric Nelson wrote:
> Hi Fabio,
>
> On 04/11/2014 01:43 PM, Fabio Estevam wrote:
>> From: Fabio Estevam <fabio.estevam@freescale.com>
>>
>> ECSPI chipselect (MX6_PAD_EIM_D19__GPIO3_IO19) is used with GPIO functionality,
>> so it does not make sense to set its pad as SPI pin.
>>
>> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
>> ---
>> Eric,
>>
>> This is untested.
>>
>> board/boundary/nitrogen6x/nitrogen6x.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/board/boundary/nitrogen6x/nitrogen6x.c b/board/boundary/nitrogen6x/nitrogen6x.c
>> index d9c05b0..f2492e4 100644
>> --- a/board/boundary/nitrogen6x/nitrogen6x.c
>> +++ b/board/boundary/nitrogen6x/nitrogen6x.c
>> @@ -331,7 +331,7 @@ int board_mmc_init(bd_t *bis)
>> #ifdef CONFIG_MXC_SPI
>> iomux_v3_cfg_t const ecspi1_pads[] = {
>> /* SS1 */
>> - MX6_PAD_EIM_D19__GPIO3_IO19 | MUX_PAD_CTRL(SPI_PAD_CTRL),
>> + MX6_PAD_EIM_D19__GPIO3_IO19 | MUX_PAD_CTRL(NO_PAD_CTRL),
>> MX6_PAD_EIM_D17__ECSPI1_MISO | MUX_PAD_CTRL(SPI_PAD_CTRL),
>> MX6_PAD_EIM_D18__ECSPI1_MOSI | MUX_PAD_CTRL(SPI_PAD_CTRL),
>> MX6_PAD_EIM_D16__ECSPI1_SCLK | MUX_PAD_CTRL(SPI_PAD_CTRL),
>>
>
> Tested-by: Eric Nelson <eric.nelson@boundarydevices.com>
> Acked-by: Eric Nelson <eric.nelson@boundarydevices.com>
NAK. Please don't use NO_PAD_CTRL. What is wrong with
SPI_PAD_CTRL. Your commit message doesn't say.
It is an SPI pin (even if used as a GPIO,) so
why doesn't it make sense.
I think your fixing a problem that doesn't exist.
Troy
next prev parent reply other threads:[~2014-04-13 22:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-11 20:43 [U-Boot] [PATCH] nitrogen6x: Fix the PAD settings for the ECSPI chipselect Fabio Estevam
2014-04-12 15:04 ` Eric Nelson
2014-04-12 15:32 ` Fabio Estevam
2014-04-12 22:54 ` Eric Nelson
2014-04-13 22:08 ` Troy Kisky [this message]
2014-04-13 23:01 ` Fabio Estevam
2014-04-13 23:21 ` Troy Kisky
2014-04-28 12:04 ` 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=534B0ACC.2060509@boundarydevices.com \
--to=troy.kisky@boundarydevices.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox