<feed xmlns='http://www.w3.org/2005/Atom'>
<title>u-boot.git/board/freescale/mx6qsabrelite/mx6qsabrelite.c, branch master</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/'/>
<entry>
<title>mx6qsabrelite: Remove mx6qsabrelite code in favor of nitrogen6x</title>
<updated>2013-07-26T14:44:29+00:00</updated>
<author>
<name>Fabio Estevam</name>
<email>fabio.estevam@freescale.com</email>
</author>
<published>2013-07-26T14:37:17+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=f8b1e86d4707718e52cf6466845e463c358627ee'/>
<id>f8b1e86d4707718e52cf6466845e463c358627ee</id>
<content type='text'>
mx6qsabrelite and nitrogen6q boards are hardware compatible, so let's avoid the
code duplication and only use the nitrogen6x source code to make board code
maintainance easier.

Tested booting a mainline device tree kernel on a mx6qsabrelite board.

Signed-off-by: Fabio Estevam &lt;fabio.estevam@freescale.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
mx6qsabrelite and nitrogen6q boards are hardware compatible, so let's avoid the
code duplication and only use the nitrogen6x source code to make board code
maintainance easier.

Tested booting a mainline device tree kernel on a mx6qsabrelite board.

Signed-off-by: Fabio Estevam &lt;fabio.estevam@freescale.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>mx6: mx6qsabrelite/nitrogen6x: Remove incorrect setting of gpio CS signal</title>
<updated>2013-06-03T11:25:46+00:00</updated>
<author>
<name>Andrew Gabbasov</name>
<email>andrew_gabbasov@mentor.com</email>
</author>
<published>2013-05-30T04:47:38+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=0c54f4b7c81dc0234ec4a96d0986b7f5321a7680'/>
<id>0c54f4b7c81dc0234ec4a96d0986b7f5321a7680</id>
<content type='text'>
The number of gpio signal is packed inside CONFIG_SF_DEFAULT_CS macro
(shifted and or'ed with chip select), so it's incorrect to pass
that macro directly as an argument to gpio_direction_output() call.

Also, SPI driver sets the direction and initial value of a gpio,
used as a chip select signal, before any actual activity happens
on the bus.

So, it is safe to just remove the gpio_direction_output call,
that works incorrectly, thus making no effect, anyway.

Signed-off-by: Andrew Gabbasov &lt;andrew_gabbasov@mentor.com&gt;
Tested-by: Robert Winkler &lt;robert.winkler@boundarydevices.com&gt;
Acked-by: Dirk Behme &lt;dirk.behme@de.bosch.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The number of gpio signal is packed inside CONFIG_SF_DEFAULT_CS macro
(shifted and or'ed with chip select), so it's incorrect to pass
that macro directly as an argument to gpio_direction_output() call.

Also, SPI driver sets the direction and initial value of a gpio,
used as a chip select signal, before any actual activity happens
on the bus.

So, it is safe to just remove the gpio_direction_output call,
that works incorrectly, thus making no effect, anyway.

Signed-off-by: Andrew Gabbasov &lt;andrew_gabbasov@mentor.com&gt;
Tested-by: Robert Winkler &lt;robert.winkler@boundarydevices.com&gt;
Acked-by: Dirk Behme &lt;dirk.behme@de.bosch.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>imx: iomux-v3: Include PKE and PUE to pad control pull definitions</title>
<updated>2013-04-28T09:15:07+00:00</updated>
<author>
<name>Benoît Thébaudeau</name>
<email>benoit.thebaudeau@advansee.com</email>
</author>
<published>2013-04-26T01:34:47+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=7e2173cf82d0bc235b695460c56d46927febdf36'/>
<id>7e2173cf82d0bc235b695460c56d46927febdf36</id>
<content type='text'>
PUE requires PKE to mean something, as do pull values with PUE, so do not
compell users to explicitly use PKE and PUE everywhere. This is also what is
done on Linux and what has already been done for i.MX51.

By the way, remove some unused pad control definitions.

There is no change of behavior.

Note that SPI_PAD_CTRL was defined by several boards with a pull value, but
without PKE or PUE, which means that no pull was actually enabled in the pad.
This might be a bug in those boards, but this patch does not change the
behavior, so it just removes the meaningless pull value from those definitions.

Signed-off-by: Benoît Thébaudeau &lt;benoit.thebaudeau@advansee.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
PUE requires PKE to mean something, as do pull values with PUE, so do not
compell users to explicitly use PKE and PUE everywhere. This is also what is
done on Linux and what has already been done for i.MX51.

By the way, remove some unused pad control definitions.

There is no change of behavior.

Note that SPI_PAD_CTRL was defined by several boards with a pull value, but
without PKE or PUE, which means that no pull was actually enabled in the pad.
This might be a bug in those boards, but this patch does not change the
behavior, so it just removes the meaningless pull value from those definitions.

Signed-off-by: Benoît Thébaudeau &lt;benoit.thebaudeau@advansee.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>mx6: Fix get_board_rev() for the mx6 solo case</title>
<updated>2013-04-03T09:36:34+00:00</updated>
<author>
<name>Fabio Estevam</name>
<email>fabio.estevam@freescale.com</email>
</author>
<published>2013-03-27T07:36:55+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=38e70077253a6ac55cee276be72fb4e6844042cd'/>
<id>38e70077253a6ac55cee276be72fb4e6844042cd</id>
<content type='text'>
When booting a Freescale kernel 3.0.35 on a Wandboard solo, the get_board_rev()
returns 0x62xxx, which is not a value understood by the VPU
(Video Processing Unit) library in the kernel and causes the video playback to
fail.

The expected values for get_board_rev are:
0x63xxx: For mx6quad/dual
0x61xxx: For mx6dual-lite/solo

So adjust get_board_rev() accordingly and make it as weak function, so that we
do not need to define it in every mx6 board file.

Signed-off-by: Fabio Estevam &lt;fabio.estevam@freescale.com&gt;
Acked-by: Dirk Behme &lt;dirk.behme@de.bosch.com&gt;
Acked-by: Eric Nelson &lt;eric.nelson@boundarydevices.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
When booting a Freescale kernel 3.0.35 on a Wandboard solo, the get_board_rev()
returns 0x62xxx, which is not a value understood by the VPU
(Video Processing Unit) library in the kernel and causes the video playback to
fail.

The expected values for get_board_rev are:
0x63xxx: For mx6quad/dual
0x61xxx: For mx6dual-lite/solo

So adjust get_board_rev() accordingly and make it as weak function, so that we
do not need to define it in every mx6 board file.

Signed-off-by: Fabio Estevam &lt;fabio.estevam@freescale.com&gt;
Acked-by: Dirk Behme &lt;dirk.behme@de.bosch.com&gt;
Acked-by: Eric Nelson &lt;eric.nelson@boundarydevices.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>mmc: i.MX6: fsl_esdhc: Define maximum bus width supported by a board</title>
<updated>2013-04-03T09:26:28+00:00</updated>
<author>
<name>Abbas Raza</name>
<email>Abbas_Raza@mentor.com</email>
</author>
<published>2013-03-25T09:13:34+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=aad4659a2fde4b69e8124d6fe8b57bf28d3c747d'/>
<id>aad4659a2fde4b69e8124d6fe8b57bf28d3c747d</id>
<content type='text'>
Maximum bus width supported by some i.MX6 boards is not 8bit like
others. In case where both host controller and card support 8bit transfers,
they agree to communicate on 8bit interface while some boards support only 4bit interface.
Due to this reason the mmc 8bit default mode fails on these boards. To rectify this,
define maximum bus width supported by these boards (4bit). If max_bus_width is not
defined, it is 0 by default and 8bit width support will be enabled in host
capabilities otherwise host capabilities are modified accordingly.

It is tested with a MMCplus card.

Signed-off-by: Abbas Raza &lt;Abbas_Raza@mentor.com&gt;
cc: stefano Babic &lt;sbabic@denx.de&gt;
cc: Andy Fleming &lt;afleming@gmail.com&gt;
Acked-by: Dirk Behme &lt;dirk.behme@de.bosch.com&gt;
Acked-by: Andrew Gabbasov &lt;andrew_gabbasov@mentor.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Maximum bus width supported by some i.MX6 boards is not 8bit like
others. In case where both host controller and card support 8bit transfers,
they agree to communicate on 8bit interface while some boards support only 4bit interface.
Due to this reason the mmc 8bit default mode fails on these boards. To rectify this,
define maximum bus width supported by these boards (4bit). If max_bus_width is not
defined, it is 0 by default and 8bit width support will be enabled in host
capabilities otherwise host capabilities are modified accordingly.

It is tested with a MMCplus card.

Signed-off-by: Abbas Raza &lt;Abbas_Raza@mentor.com&gt;
cc: stefano Babic &lt;sbabic@denx.de&gt;
cc: Andy Fleming &lt;afleming@gmail.com&gt;
Acked-by: Dirk Behme &lt;dirk.behme@de.bosch.com&gt;
Acked-by: Andrew Gabbasov &lt;andrew_gabbasov@mentor.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>mx6: Provide a structure for accessing HDMI registers</title>
<updated>2013-03-07T17:03:44+00:00</updated>
<author>
<name>Fabio Estevam</name>
<email>fabio.estevam@freescale.com</email>
</author>
<published>2013-02-28T14:35:02+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=1b097cff51a6781ce3a0036b7f0a9e53864c9727'/>
<id>1b097cff51a6781ce3a0036b7f0a9e53864c9727</id>
<content type='text'>
Provide a structure for accessing HDMI registers, so that we can use proper
read/write accessors.

Signed-off-by: Fabio Estevam &lt;fabio.estevam@freescale.com&gt;
Tested-by: Eric Nelson &lt;eric.nelson@boundarydevices.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Provide a structure for accessing HDMI registers, so that we can use proper
read/write accessors.

Signed-off-by: Fabio Estevam &lt;fabio.estevam@freescale.com&gt;
Tested-by: Eric Nelson &lt;eric.nelson@boundarydevices.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>i.MX6: consolidate pad names for multi-CPU boards</title>
<updated>2013-03-07T15:43:46+00:00</updated>
<author>
<name>Eric Nelson</name>
<email>eric.nelson@boundarydevices.com</email>
</author>
<published>2013-02-19T10:07:01+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=cfb8b9d3351ebb519f9c27e0aeba814e7c81ee85'/>
<id>cfb8b9d3351ebb519f9c27e0aeba814e7c81ee85</id>
<content type='text'>
Rename all i.MX6 pad declarations to MX6_PAD_x, so a board
may support either i.MX6Quad/Dual (MX6Q) or i.MX6Dual-Lite/Solo
(MX6DL) by including the proper header.

Boards mx6qarm2, mx6qsabreauto, mx6qsabrelite, and mx6qsabresd
only support MX6Q, so they include mx6q_pins.h.

Signed-off-by: Eric Nelson &lt;eric.nelson@boundarydevices.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Rename all i.MX6 pad declarations to MX6_PAD_x, so a board
may support either i.MX6Quad/Dual (MX6Q) or i.MX6Dual-Lite/Solo
(MX6DL) by including the proper header.

Boards mx6qarm2, mx6qsabreauto, mx6qsabrelite, and mx6qsabresd
only support MX6Q, so they include mx6q_pins.h.

Signed-off-by: Eric Nelson &lt;eric.nelson@boundarydevices.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>i.MX6: mx6qsabrelite: indent with tabs</title>
<updated>2013-03-07T15:43:46+00:00</updated>
<author>
<name>Eric Nelson</name>
<email>eric.nelson@boundarydevices.com</email>
</author>
<published>2013-02-19T10:07:00+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=74cf809972658eae18c33e078c05a7cc9c9460c9'/>
<id>74cf809972658eae18c33e078c05a7cc9c9460c9</id>
<content type='text'>
This patch has no functional changes and simply replaces
leading spaces with tabs.

Signed-off-by: Eric Nelson &lt;eric.nelson@boundarydevices.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This patch has no functional changes and simply replaces
leading spaces with tabs.

Signed-off-by: Eric Nelson &lt;eric.nelson@boundarydevices.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>mx6qsabrelite: search mii phy address 4-7</title>
<updated>2013-01-28T05:57:51+00:00</updated>
<author>
<name>Troy Kisky</name>
<email>troy.kisky@boundarydevices.com</email>
</author>
<published>2012-10-22T16:40:47+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=323692196825bb22a170c26190f5436452ecadfb'/>
<id>323692196825bb22a170c26190f5436452ecadfb</id>
<content type='text'>
Signed-off-by: Troy Kisky &lt;troy.kisky@boundarydevices.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Signed-off-by: Troy Kisky &lt;troy.kisky@boundarydevices.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>i.MX6: mx6qsabrelite: Add splash screen support</title>
<updated>2012-10-16T10:35:12+00:00</updated>
<author>
<name>Eric Nelson</name>
<email>eric.nelson@boundarydevices.com</email>
</author>
<published>2012-10-03T07:28:43+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=e58010b554500eab87603cb1ff9c546b46d8fd60'/>
<id>e58010b554500eab87603cb1ff9c546b46d8fd60</id>
<content type='text'>
Adds support for HDMI, two LVDS panels and one RGB panel to
the SABRE-Lite board.

Displays supported:
         HDMI		- 1024 x 768 for maximum compatibility
         Hannstar-XGA   - 1024 x 768 LVDS (Freescale part number MCIMX-LVDS1)
         wsvga-lvds     - 1024 x 600 LVDS (Boundary p/n Nit6X_1024x600)
         wvga-rgb       - 800 x 480 RGB (Boundary p/n Nit6X_800x480)

Since the ipuv3_fb display driver currently supports only a single display,
this code auto-detects panel by probing the HDMI Phy for Hot Plug Detect
or the I2C touch controller of the LVDS and RGB displays in the priority
listed above.

Setting 'panel' environment variable to one of the names above will
override auto-detection.

Signed-off-by: Eric Nelson &lt;eric.nelson@boundarydevices.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Adds support for HDMI, two LVDS panels and one RGB panel to
the SABRE-Lite board.

Displays supported:
         HDMI		- 1024 x 768 for maximum compatibility
         Hannstar-XGA   - 1024 x 768 LVDS (Freescale part number MCIMX-LVDS1)
         wsvga-lvds     - 1024 x 600 LVDS (Boundary p/n Nit6X_1024x600)
         wvga-rgb       - 800 x 480 RGB (Boundary p/n Nit6X_800x480)

Since the ipuv3_fb display driver currently supports only a single display,
this code auto-detects panel by probing the HDMI Phy for Hot Plug Detect
or the I2C touch controller of the LVDS and RGB displays in the priority
listed above.

Setting 'panel' environment variable to one of the names above will
override auto-detection.

Signed-off-by: Eric Nelson &lt;eric.nelson@boundarydevices.com&gt;
</pre>
</div>
</content>
</entry>
</feed>
