Hi all,
on kernel 3.16.3 running on an i.MX6 with an eMMC card formatting a
partition won't work, it hangs. With an added -v the last thing it
spit out is Discarding device blocks: 4096/196608.
When I run mkfs with -E nodiscard, formatting booting works.
Noteworthy: when the eMMC device was
Hi Arnd,
Are you sure that it's not just taking very long?
Hmm, after one or two minutes I lost my patience. Also, hitting Ctrl-C
didn't abort the application. Suspending it with Ctrl-Z doesn't work
either. I did an strace, and the last few lines look like this:
stat64(/dev/mmcblk0p1,
Hi,
I noticed in a kernel 4.0.7 that I loose CAN packets when an incoming
rsync transfer changes my eMMC or SD-Card image. I used CONFIG_FRACE
to find why this is the case, and came to this trace:
# tracer: preemptoff
#
# preemptoff latency trace v1.1.5 on 4.0.7
#
Can you also fix the driver to NOT use mdelay(1) while in spinlock irqsafe?
A driver with such a design should have gotten a NAK in the first place ...
--
To unsubscribe from this list: send the line unsubscribe linux-mmc in
the body of a message to majord...@vger.kernel.org
More majordomo info
Currently this function is used inside the mmc test driver. But it is also
usable in the (upcoming) firmware update patch. So move this function out
of mmc_test.c into core.c.
Signed-off-by: Holger Schurig <holgerschu...@gmail.com>
---
drivers/mmc/card/mmc_test.
There have been some attempts to add FFU (field firmware update). The last
AFAIK in Nov 2014, http://www.spinics.net/lists/linux-mmc/msg29324.html
But it seems that the committers weren't persistent enought.
I took the liberty to take Avi's patch and make it hopefully
maintainer-review
multiple write operations
- support of both EXT_CSD_MODE_OPERATION_CODES modes
Almost completely taken from Avi Shchislowsk/Alex Lemberg patch
"[PATCH 3/3]mmc: Support-FFU-for-eMMC-v5.0".
Signed-off-by: Holger Schurig <holgerschu...@gmail.com>
---
drivers/mmc/card/Kconfig | 1
. This is helpful to
the source in printk.
Signed-off-by: Holger Schurig <holgerschu...@gmail.com>
---
drivers/mmc/card/mmc_test.c | 109 +++-
drivers/mmc/core/core.c | 28
include/linux/mmc/core.h| 8
3 files chang
Currently this function is used inside the mmc test driver. But it is also
usable in the (upcoming) firmware update patch. So move this function out
of mmc_test.c into core.c.
Signed-off-by: Holger Schurig <holgerschu...@gmail.com>
---
drivers/mmc/card/mmc_test.
This function can be used to send ext_csd data towards the chip, which is
needed in the (upcoming) firmware update patch.
Signed-off-by: Holger Schurig <holgerschu...@gmail.com>
---
drivers/mmc/core/mmc_ops.c | 4 ++--
include/linux/mmc/core.h | 3 +++
2 files changed, 5 insertions
Currently this function is used inside the mmc test driver. But it is also
usable in the (upcoming) firmware update patch. So move this function out
of mmc_test.c into core.c.
Signed-off-by: Holger Schurig <holgerschu...@gmail.com>
---
drivers/mmc/card/mmc_test.
Wow, at last some reaction. And I thought nobody cares ...
BTW, removing CONFIG_MMC_CLKGATE helped a bit, because the pointless
clock-off-clock-on while the device is booting (or accessing multiple
sectors within a short time) isn't going to happen anymore.
But really, a mdelay(1) in a driver
Hi,
I have an i.MX6Q based system that cannot provide 1.8V voltage towards
the eMMC. But Linux 4.4-rc4 reports 1.8V for the eMMC, but this is
impossible. Neither my hardware allows this, nor does the DT say it.
root@imx6q:/sys/kernel/debug# cat mmc1/ios
clock: 5200 Hz
actual clock:
> Sorry for the delay.
No problem, I was busy with many other projects as well.
> My advise right now is to try this out via the mmc ioctl in userspace,
> yes. Although, if you encounter any issues with that approach that it
> might not be reliable, I am open to look into the in-kernel solution
> The no-1-8-v is a somewhat broken DT binding. I advise people to not
> use any more.
> Depending on the sdhci variant it have different meanings.
>
> I guess you are using the sdhci-esdhc-imx variant, which means
> no-1-8-v will disable UHS modes for SD-cards (those requiring 1.8V
> signal
15 matches
Mail list logo