u-boot.git, branch v2014.07 Unnamed repository; edit this file 'description' to name the repository. Prepare v2014.07 2014-07-14T17:16:45+00:00 Tom Rini trini@ti.com 2014-07-14T17:16:45+00:00 524123a70761110c5cf3ccc5f52f6d4da071b959 Signed-off-by: Tom Rini <trini@ti.com> 
Signed-off-by: Tom Rini <trini@ti.com>
socfpga: timer actually counts down 2014-07-14T15:21:35+00:00 Pavel Machek pavel@denx.de 2014-07-13T11:10:45+00:00 2cc0ea72ef98eba3b6dbf65cff39f08e31e137d1 Timer on cyclone5 actually counts down. It took me a while to figure out, as timer counting in wrong direction actually _can_ be used, it just appears to tick at extremely high frequency in u-boot. The bug was introduced in commit 23ab7ee0ffa9d5efd0b4ad830befba306d24a327. Signed-off-by: Pavel Machek <pavel@denx.de> Acked-by: Marek Vasut <marex@denx.de> 
Timer on cyclone5 actually counts down. It took me a while to figure
out, as timer counting in wrong direction actually _can_ be used, it
just appears to tick at extremely high frequency in u-boot.

The bug was introduced in commit
23ab7ee0ffa9d5efd0b4ad830befba306d24a327.

Signed-off-by: Pavel Machek <pavel@denx.de>
Acked-by: Marek Vasut <marex@denx.de>
ARM: DRA7xx: Update the board_name env variable 2014-07-14T15:16:38+00:00 Lokesh Vutla lokeshvutla@ti.com 2014-07-14T14:27:58+00:00 4ec3f6e5104034e113f6ea8ab356f78ff4ad00b8 Update the board_name env variable and accordingly populate the dtb file. Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com> 
Update the board_name env variable and accordingly
populate the dtb file.

Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
boards.cfg: change "<none>" in the board field to "-" 2014-07-14T14:55:58+00:00 Masahiro Yamada yamada.m@jp.panasonic.com 2014-07-11T07:31:47+00:00 75e6cd2799f0d6bf994a1154107cb950b232aa59 In the previous commit, all the board fields were filled. Now we can use "-" in the board field for a different meaning. Going forward, "-" stands for no board directory as in cpu, soc, vendor fields. Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com> 
In the previous commit, all the board fields were filled.

Now we can use "-" in the board field for a different meaning.

Going forward, "-" stands for no board directory
as in cpu, soc, vendor fields.

Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
boards.cfg: keep it sorted filling the board field 2014-07-14T14:55:56+00:00 Masahiro Yamada yamada.m@jp.panasonic.com 2014-07-11T07:31:46+00:00 5b0421e67cc688766cc81829ffcede4ef0de36b0 The boards.cfg file has allowed to use "-" for the board (= 6th) field if the board name is the same as the 7th field. But I notice one problem. Because tools/reformat.py sorts the lines in the simple alphabetical order (= the order of character code), some entries for the same board are not lined up together. For example, "bf527-ezkit" and "bf527-ezkit-v2" share the same board. But they are located separately because "bf527-ezkit" fills the board field with "-" whereas "bf527-ezkit-v2" specifies it explicitely. The similar things can be seen: - between "trizepsive" and "polaris" - between "RRvision" and "RRvision_LCD" - between "korat" and "korat_perm" - between "lwmon5" and "lcd4_lwmon5" This commit was generated by the following command: awk '$6 == "-" { $6 = $7 } { print }' boards.cfg \ | tools/reformat.py -i -d '-' -s 8 > boards0.cfg; \ mv boards0.cfg boards.cfg Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com> 
The boards.cfg file has allowed to use "-" for the board (= 6th) field
if the board name is the same as the 7th field.

But I notice one problem.
Because tools/reformat.py sorts the lines in the simple alphabetical
order (= the order of character code), some entries for the same board
are not lined up together.

For example, "bf527-ezkit" and "bf527-ezkit-v2" share the same board.
But they are located separately because "bf527-ezkit" fills the board
field with "-" whereas "bf527-ezkit-v2" specifies it explicitely.

The similar things can be seen:
 - between "trizepsive" and "polaris"
 - between "RRvision" and "RRvision_LCD"
 - between "korat" and "korat_perm"
 - between "lwmon5" and "lcd4_lwmon5"

This commit was generated by the following command:

awk '$6 == "-" { $6 = $7 } { print }' boards.cfg \
  | tools/reformat.py -i -d '-' -s 8  > boards0.cfg; \
  mv boards0.cfg boards.cfg

Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
Merge branch 'master' of git://www.denx.de/git/u-boot-imx 2014-07-11T18:54:48+00:00 Tom Rini trini@ti.com 2014-07-11T18:54:48+00:00 84f24ac8278d287581e5a559a7299e1dc2b53481 






i.MX6DL/S: add drive-strength back to pads DISP0_DAT2/DAT10
2014-07-10T13:23:56+00:00

Eric Nelson
eric.nelson@boundarydevices.com

2014-07-09T19:27:29+00:00

e153333eeb50021fb3a730a3216c1968e7710999

The pad settings for DISP0_DATA02 and DISP0_DAT10 were not
set in the same way as DISP0_DAT00-23, causing much flicker
in parallel RGB displays on Dual-Lite and Solo processors.

These settings now match the i.MX6 Dual and Quad core versions.

Note that this fixes a regression in commit b47abc3 and that
this is the second time we've had a regression on these two
pads (See commit e654ddf).

Signed-off-by: Eric Nelson <eric.nelson@boundarydevices.com>
Acked-by: Otavio Salvador <otavio@ossystems.com.br>





The pad settings for DISP0_DATA02 and DISP0_DAT10 were not
set in the same way as DISP0_DAT00-23, causing much flicker
in parallel RGB displays on Dual-Lite and Solo processors.

These settings now match the i.MX6 Dual and Quad core versions.

Note that this fixes a regression in commit b47abc3 and that
this is the second time we've had a regression on these two
pads (See commit e654ddf).

Signed-off-by: Eric Nelson <eric.nelson@boundarydevices.com>
Acked-by: Otavio Salvador <otavio@ossystems.com.br>







usb: phy: omap_usb_phy: implement usb_phy_power() for AM437x
2014-07-09T20:11:51+00:00

Felipe Balbi
balbi@ti.com

2014-06-23T22:18:24+00:00

5ba95541b700d2edecb4d97d4b905f51ed8551b3

Newer AM437x silicon requires us to explicitly power up
the USB2 PHY. By implementing usb_phy_power() we can
achieve that.

Signed-off-by: Felipe Balbi <balbi@ti.com>





Newer AM437x silicon requires us to explicitly power up
the USB2 PHY. By implementing usb_phy_power() we can
achieve that.

Signed-off-by: Felipe Balbi <balbi@ti.com>







usb: host: xhci: make sure to power up PHY
2014-07-09T20:11:51+00:00

Felipe Balbi
balbi@ti.com

2014-06-23T21:25:38+00:00

26707d9e6bb0d2e5e6de706cd68bddcea34e731f

some boards won't work if the PHY isn't explicitly
powered up.

Signed-off-by: Felipe Balbi <balbi@ti.com>





some boards won't work if the PHY isn't explicitly
powered up.

Signed-off-by: Felipe Balbi <balbi@ti.com>







doc: Add zynq fragment to git-mailrc file
2014-07-09T14:45:15+00:00

Michal Simek
michal.simek@xilinx.com

2014-07-09T14:10:49+00:00

bc9a78acd40cf9bc7017639e8d4aec889b66e7ee

This is a MIME GnuPG-signed message.  If you see this text, it means that
your E-mail or Usenet software does not support MIME signed messages.
The Internet standard for MIME PGP messages, RFC 2015, was published in 1996.
To open this message correctly you will need to install E-mail or Usenet
software that supports modern Internet standards.

Signed-off-by: Michal Simek <michal.simek@xilinx.com>





This is a MIME GnuPG-signed message.  If you see this text, it means that
your E-mail or Usenet software does not support MIME signed messages.
The Internet standard for MIME PGP messages, RFC 2015, was published in 1996.
To open this message correctly you will need to install E-mail or Usenet
software that supports modern Internet standards.

Signed-off-by: Michal Simek <michal.simek@xilinx.com>