Re: gpios reset when kernel starts

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

 



>>>>> "Cliff" == Cliff Brake <cliff.brake@xxxxxxxxx> writes:

Hi,

 Cliff> I'm working with the 3.0 kernel on a 3730.  It appears that when
 Cliff> I set a GPIO to output and set it high in the bootloader, this
 Cliff> gets reset when the kernel starts.  Is this expected, and is
 Cliff> there any workaround to have this not happen?  The alternate
 Cliff> functions seem to be sticking when configured in the bootloader.

 Cliff> Its possible that something in the kernel is taking control of
 Cliff> the signal, but it seems ulikely as I've tried two different
 Cliff> unrelated GPIOs with the same result.

It's because the kernel resets (almost) all the internal IP blocks
during boot to get them in a consistent state. I asked about the same
thing recently:

http://thread.gmane.org/gmane.linux.ports.arm.omap/91243/

-- 
Bye, Peter Korsgaard
--
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