From: Peng Fan <van.freenix@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/3] mmc: fsl: introduce wp_enable
Date: Wed, 15 Jun 2016 09:17:13 +0800 [thread overview]
Message-ID: <20160615011710.GA768@linux-7smt.suse> (raw)
In-Reply-To: <CAOMZO5BC8Udc9AjS+Vu0LHJyyh+h_8VrEqMj+73r4JGgA7Z7mw@mail.gmail.com>
Hi Fabio,
On Tue, Jun 14, 2016 at 08:23:27PM -0300, Fabio Estevam wrote:
>Hi Peng,
>
>On Tue, Jun 14, 2016 at 8:01 PM, Fabio Estevam <festevam@gmail.com> wrote:
>
>> Just saw this issue on a mx6ul pico board: after adding I2C support
>> then the eMMC could not longer be written:
>>
>> => saveenv
>> Saving Environment to MMC...
>> Writing to MMC(0)...
>> The SD card is locked. Can not write to a locked card.
>>
>> mmc write failed
>> failed
>>
>> Your patch allows me to write to the eMMC succesfully:
>>
>> Tested-by: Fabio Estevam <fabio.estevam@nxp.com>
Thanks. This patch set was posted some time ago.
>
>Looks like this is an issue with the MX6UL IOMUXC, not the esdhc
>driver itself, so maybe we should not do this change for all other
>SoCs.
>
>If I manually do:
>=> mw.l 20E066C 2
>Then 'saveenv' works fine.
>
>Shouldn't we fix this in the MX6UL IOMUXC code instead?
No. We can not avoid such issue for now. You changed register 20e066c'value to 2
2 means "CSI_DATA04_ALT8 ? Selecting Pad: CSI_DATA04 for Mode: ALT8"
Look at "Figure 31-3. Daisy chain illustration" of i.MX6UL RM, if changed to 2,
that means you let CSI_DATA04 pad goes into usdhc1_wp.
select input can not be closed or disabled, which will cause issues like what
you met. Even worse, some one may need to redesign their board to avoid pin
conflict.
Regards,
Peng.
next prev parent reply other threads:[~2016-06-15 1:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 6:54 [U-Boot] [PATCH 1/3] mmc: fsl: reset to normal boot mode when eMMC fast boot Peng Fan
2016-04-26 6:54 ` [U-Boot] [PATCH 2/3] fsl_esdhc: Update clock enable bits for USDHC Peng Fan
2016-04-26 6:54 ` [U-Boot] [PATCH 3/3] mmc: fsl: introduce wp_enable Peng Fan
2016-06-14 23:01 ` Fabio Estevam
2016-06-14 23:23 ` Fabio Estevam
2016-06-15 1:17 ` Peng Fan [this message]
2016-06-15 1:35 ` Fabio Estevam
2016-06-15 4:04 ` york sun
2016-06-15 1:46 ` Fabio Estevam
2016-06-15 2:28 ` Peng Fan
2016-08-04 5:32 ` [U-Boot] [U-Boot, 1/3] mmc: fsl: reset to normal boot mode when eMMC fast boot Jaehoon Chung
2016-08-08 4:31 ` Peng Fan
2016-08-08 7:02 ` Jaehoon Chung
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=20160615011710.GA768@linux-7smt.suse \
--to=van.freenix@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox