Re: Watchdog driver issue on OMAP3

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Iqbal,
Iqbal mentioned the following on 1/7/2008 3:50 AM:
Kevin's unlock flash device patch(commit: a34c2f3) switches the NOR flash into write or programming mode. Due to this, watchdog reset is causing the kernel to freeze. Basically the u-boot sitting on the NOR flash is not read/executed because it is unlocked.

We can have a workaround by locking the device back on the completion of jffs2 booting or otherwise Kevin can suggest something else.
Here is my 2 cents: Lock/unlock for a NOR flash has effect only for writing to the flash -> not reading. I think ur real issue is that flash was in the middle of a write operation to the partition (maybe it was doing a jffs2 garbage collection or something), when wdt triggered a reset. Relocking the device only hides your problem by forcing it to be a read only partition. You should be able to hit the problem yet again by doing a flash_unlock to the partition and then running ur wdt trigger case. I guess it'd be a bit hard to reset exactly when jffs2 is in the middle of a write.. but I guess u'd have already looked at it.

What is the correct solution for this issue? I think maybe hardware should assert reset line to NOR device on a warm reset.

Regards,
Nishanth Menon
-
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux