tiomap-dev team mailing list archive

Thread
Date

[Bug 645167] Re: omap4: u-boot overrides pin-muxing settings from x-loader

To: tiomap-dev@xxxxxxxxxxxxxxxxxxx
From: John Rigby <645167@xxxxxxxxxxxxxxxxxx>
Date: Wed, 05 Jan 2011 00:05:54 -0000
Reply-to: Bug 645167 <645167@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

changing to fix released to match other two instances

** Changed in: u-boot-linaro
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of TI OMAP
Developers, which is a direct subscriber.
https://bugs.launchpad.net/bugs/645167

Title:
  omap4: u-boot overrides pin-muxing settings from x-loader

Status in Linaro U-Boot:
  Fix Released
Status in “u-boot-linaro” package in Ubuntu:
  Fix Released
Status in “u-boot-linaro” source package in Maverick:
  Fix Released

Bug description:
  u-boot is able to define a complete pin-muxing setting.
On OMAP4 today, we rely on x-loader for this purpose.

So we shall either:
1) deactivate pin-muxing setting for omap4, or
2) or use it and ensure we have the latest pin-mux updates integrated

Option 1 was used here: http://dev.omapzoom.org/?p=bootloader/u-boot.git;a=commit;h=cc49b2f4915bb550294b8c74f292e81cfdb11f4d

Today for example, the pin-mux for GPMC_A22 is not properly set in u-boot, resulting in non-functional BT feature.
For this specific BT issue, the correct pin-mux is described in this x-loader patch (included into x-loader-omap4 package):
http://gitorious.org/pandaboard/x-loader/commit/5d05eafab768f4b88aae4f890fc26fd5eb3002ce