<feed xmlns='http://www.w3.org/2005/Atom'>
<title>u-boot.git/board/barco, branch v2016.09</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.</subtitle>
<id>http://cgit.235523.xyz/u-boot.git/atom/board/barco?h=v2016.09</id>
<link rel='self' href='http://cgit.235523.xyz/u-boot.git/atom/board/barco?h=v2016.09'/>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/'/>
<updated>2016-09-06T16:22:48Z</updated>
<entry>
<title>mx6: ddr: Allow changing REFSEL and REFR fields</title>
<updated>2016-09-06T16:22:48Z</updated>
<author>
<name>Fabio Estevam</name>
<email>fabio.estevam@nxp.com</email>
</author>
<published>2016-08-29T23:37:15Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=edf0093732225c2fd0791c3864e9a3eef1f92f19'/>
<id>urn:sha1:edf0093732225c2fd0791c3864e9a3eef1f92f19</id>
<content type='text'>
Currently MX6 SPL DDR initialization hardcodes the REF_SEL and
REFR fields of the MDREF register as 1 and 7, respectively for
DDR3 and 0 and 3 for LPDDR2.

Looking at the MDREF initialization done via DCD we see that
boards do need to initialize these fields differently:

$ git grep 0x021b0020 board/
board/bachmann/ot1200/mx6q_4x_mt41j128.cfg:DATA 4 0x021b0020 0x00005800
board/ccv/xpress/imximage.cfg:DATA 4 0x021b0020 0x00000800 /* MMDC0_MDREF */
board/freescale/mx6qarm2/imximage.cfg:DATA 4 0x021b0020 0x7800
board/freescale/mx6qarm2/imximage.cfg:DATA 4 0x021b0020 0x00005800
board/freescale/mx6qarm2/imximage_mx6dl.cfg:DATA 4 0x021b0020 0x00005800
board/freescale/mx6qarm2/imximage_mx6dl.cfg:DATA 4 0x021b0020 0x00005800
board/freescale/mx6qsabreauto/imximage.cfg:DATA 4 0x021b0020 0x00005800
board/freescale/mx6qsabreauto/mx6dl.cfg:DATA 4 0x021b0020 0x00005800
board/freescale/mx6qsabreauto/mx6qp.cfg:DATA 4 0x021b0020 0x00005800
board/freescale/mx6sabresd/mx6dlsabresd.cfg:DATA 4      0x021b0020 0x00005800
board/freescale/mx6sabresd/mx6q_4x_mt41j128.cfg:DATA 4 0x021b0020 0x00005800
board/freescale/mx6slevk/imximage.cfg:DATA 4 0x021b0020 0x00001800
board/freescale/mx6sxsabreauto/imximage.cfg:DATA 4 0x021b0020 0x00000800
board/freescale/mx6sxsabresd/imximage.cfg:DATA 4 0x021b0020 0x00000800
board/warp/imximage.cfg:DATA 4 0x021b0020 0x00001800

So introduce a mechanism for users to be able to configure
REFSEL and REFR fields as needed.

Keep all the mx6 SPL users in their current REF_SEL and REFR values,
so no functional changes for the existing users.

Signed-off-by: Fabio Estevam &lt;fabio.estevam@nxp.com&gt;
Reviewed-by: Eric Nelson &lt;eric@nelint.com&gt;
</content>
</entry>
<entry>
<title>mx6: remove SYS_SOC from board Kconfig</title>
<updated>2015-09-13T08:37:29Z</updated>
<author>
<name>Peng Fan</name>
<email>Peng.Fan@freescale.com</email>
</author>
<published>2015-09-07T06:59:48Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=f20562e4c40adc3a16cfce4d7715e77969eccd0a'/>
<id>urn:sha1:f20562e4c40adc3a16cfce4d7715e77969eccd0a</id>
<content type='text'>
Remove duplicated SYS_SOC Kconfig entry from board Kconfig,
because we have this entry in arch/arm/cpu/armv7/mx6/Kconfig.

Signed-off-by: Peng Fan &lt;Peng.Fan@freescale.com&gt;
Cc: Stefano Babic &lt;sbabic@denx.de&gt;
Cc: Heiko Schocher &lt;hs@denx.de&gt;
Cc: Christian Gmeiner &lt;christian.gmeiner@gmail.com&gt;
Cc: Stefan Roese &lt;sr@denx.de&gt;
Cc: Troy Kisky &lt;troy.kisky@boundarydevices.com&gt;
Cc: Nikita Kiryanov &lt;nikita@compulab.co.il&gt;
Cc: "Eric Bénard" &lt;eric@eukrea.com&gt;
Cc: Fabio Estevam &lt;fabio.estevam@freescale.com&gt;
Cc: Tim Harvey &lt;tharvey@gateworks.com&gt;
Cc: Marek Vasut &lt;marex@denx.de&gt;
Cc: Markus Niebel &lt;Markus.Niebel@tq-group.com&gt;
Cc: Otavio Salvador &lt;otavio@ossystems.com.br&gt;
Acked-by: Stefan Roese &lt;sr@denx.de&gt;
Acked-by: Marek Vasut &lt;marex@denx.de&gt;
Acked-by: Christian Gmeiner &lt;christian.gmeiner@gmail.com&gt;
Acked-by: Markus Niebel &lt;Markus.Niebel@tq-group.com&gt;
Acked-by: Troy Kisky &lt;troy.kisky@boundarydevices.com&gt;
Acked-by: Igor Grinberg &lt;grinberg@compulab.co.il&gt;
</content>
</entry>
<entry>
<title>imx: mx6: ddr init MMDC according to ddr_type</title>
<updated>2015-09-02T13:34:12Z</updated>
<author>
<name>Peng Fan</name>
<email>Peng.Fan@freescale.com</email>
</author>
<published>2015-08-17T08:11:03Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=f2ff834365296151b24bf8617f1f6dd070bdce9e'/>
<id>urn:sha1:f2ff834365296151b24bf8617f1f6dd070bdce9e</id>
<content type='text'>
To i.MX6, DDR3 and LPDDR2 is supported, so rename function mx6_dram_cfg
to mx6_ddr3_cfg and the original mx6_dram_cfg function only is a wrapper.
The new reimplemented function mx6_dram_cfg only invokes mx6_ddr3_cfg
when ddr_type is for DDR3. Later we can use ddr_type to initialize
MMDC for LPDDR2.

Initialize ddr_type for different boards which enable SPL.

Signed-off-by: Peng Fan &lt;Peng.Fan@freescale.com&gt;
Cc: Stefano Babic &lt;sbabic@denx.de&gt;
Cc: Tim Harvey &lt;tharvey@gateworks.com&gt;
Cc: Stefan Roese &lt;sr@denx.de&gt;
Cc: Fabio Estevam &lt;fabio.estevam@freescale.com&gt;
Reviewed-by: Stefan Roese &lt;sr@denx.de&gt;
</content>
</entry>
<entry>
<title>imx: clock support enet2 anatop clock support</title>
<updated>2015-09-02T13:29:14Z</updated>
<author>
<name>Peng Fan</name>
<email>Peng.Fan@freescale.com</email>
</author>
<published>2015-08-12T09:46:50Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=6d97dc10a81062a787fcf5e5df7b88d1ea122a64'/>
<id>urn:sha1:6d97dc10a81062a787fcf5e5df7b88d1ea122a64</id>
<content type='text'>
To i.MX6SX/UL, two ethernet interfaces are supported.
Add ENET2 clock support:
1. Introduce a new input parameter "fec_id", only 0 and 1 are allowed.
   To value 1, only i.MX6SX/UL can pass the check.
2. Modify board code who use this api to follow new api prototype.

Signed-off-by: Peng Fan &lt;Peng.Fan@freescale.com&gt;
Cc: Heiko Schocher &lt;hs@denx.de&gt;
Cc: Fabio Estevam &lt;fabio.estevam@freescale.com&gt;
Cc: Stefan Roese &lt;sr@denx.de&gt;
Cc: Nikolaos Pasaloukos &lt;Nikolaos.Pasaloukos@imgtec.com&gt;
Cc: Stefano Babic &lt;sbabic@denx.de&gt;
Reviewed-by: Stefan Roese &lt;sr@denx.de&gt;
</content>
</entry>
<entry>
<title>mx6: fix warning in platinum board</title>
<updated>2015-01-22T09:59:03Z</updated>
<author>
<name>Stefano Babic</name>
<email>sbabic@denx.de</email>
</author>
<published>2015-01-22T09:09:00Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=5ba49e75afa9c9f6a6de478f519dd5c284f260cc'/>
<id>urn:sha1:5ba49e75afa9c9f6a6de478f519dd5c284f260cc</id>
<content type='text'>
Fix warning due to missing prototype for writel

Signed-off-by: Stefano Babic &lt;sbabic@denx.de&gt;
Acked-by: Stefan Roese &lt;sr@denx.de&gt;
</content>
</entry>
<entry>
<title>arm: mx6: Add Barco platinum-picon and platinum-titanium</title>
<updated>2015-01-19T08:07:31Z</updated>
<author>
<name>Stefan Roese</name>
<email>sr@denx.de</email>
</author>
<published>2014-12-10T09:15:23Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=5d6050fdb8b0aaf3d3c43b3cad68d6b8f5037f9a'/>
<id>urn:sha1:5d6050fdb8b0aaf3d3c43b3cad68d6b8f5037f9a</id>
<content type='text'>
This patch adds the new Barco platinum platform. It currently
includes those two boards:

platinum-titanium
-----------------
This is the same board as the titanium that is already supported in
mainline U-Boot. But its now moved to this new platform to support
multiple "flavors" of imx6 boards in one directory. Its also moved
to support SPL booting. And with this we use the run-time DDR
configuration of this SPL support. The board is equipped with the
Micron MT41J128M16JT-125 DDR chips. We now can remove the DDR
related registers tuples from the imximage.cfg file. As all this
is done in the SPL at run-time.

platinum-picon
--------------
This board is new and based on the MX6DL with 1GiB DDR using the
Micron MT41K256M16HA DDR3 chips. Its also equipped with 2 NAND
chips (each 512MiB).

Signed-off-by: Stefan Roese &lt;sr@denx.de&gt;
Cc: Stefano Babic &lt;sbabic@denx.de&gt;
Cc: Pieter Ronsijn &lt;pieter.ronsijn@barco.com&gt;
</content>
</entry>
<entry>
<title>kconfig: arm: introduce symbol for ARM CPUs</title>
<updated>2014-10-29T13:02:09Z</updated>
<author>
<name>Georges Savoundararadj</name>
<email>savoundg@gmail.com</email>
</author>
<published>2014-10-28T22:16:09Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=2e07c249a67e055db294818ff063d502d15db0f8'/>
<id>urn:sha1:2e07c249a67e055db294818ff063d502d15db0f8</id>
<content type='text'>
This commit introduces a Kconfig symbol for each ARM CPU:
CPU_ARM720T, CPU_ARM920T, CPU_ARM926EJS, CPU_ARM946ES, CPU_ARM1136,
CPU_ARM1176, CPU_V7, CPU_PXA, CPU_SA1100.
Also, it adds the CPU feature Kconfig symbol HAS_VBAR which is selected
for CPU_ARM1176 and CPU_V7.

For each target, the corresponding CPU is selected and the definition of
SYS_CPU in the corresponding Kconfig file is removed.

Also, it removes redundant "string" type in some Kconfig files.

Signed-off-by: Georges Savoundararadj &lt;savoundg@gmail.com&gt;
Acked-by: Albert ARIBAUD &lt;albert.u.boot@aribaud.net&gt;
Cc: Masahiro Yamada &lt;yamada.m@jp.panasonic.com&gt;
</content>
</entry>
<entry>
<title>kconfig: remove redundant "string" type in arch and board Kconfigs</title>
<updated>2014-09-13T20:43:55Z</updated>
<author>
<name>Masahiro Yamada</name>
<email>yamada.m@jp.panasonic.com</email>
</author>
<published>2014-09-13T18:01:49Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=461be2f96e4b87e5065208c6659a47dd0ad9e9f8'/>
<id>urn:sha1:461be2f96e4b87e5065208c6659a47dd0ad9e9f8</id>
<content type='text'>
Now the types of CONFIG_SYS_{ARCH, CPU, SOC, VENDOR, BOARD, CONFIG_NAME}
are specified in arch/Kconfig.

We can delete the ones in arch and board Kconfig files.

This commit can be easily reproduced by the following command:

find . -name Kconfig -a ! -path ./arch/Kconfig | xargs sed -i -e '
/config[[:space:]]SYS_\(ARCH\|CPU\|SOC\|\VENDOR\|BOARD\|CONFIG_NAME\)/ {
    N
    s/\n[[:space:]]*string//
}
'

Signed-off-by: Masahiro Yamada &lt;yamada.m@jp.panasonic.com&gt;
</content>
</entry>
<entry>
<title>Add board MAINTAINERS files</title>
<updated>2014-07-30T12:48:06Z</updated>
<author>
<name>Masahiro Yamada</name>
<email>yamada.m@jp.panasonic.com</email>
</author>
<published>2014-07-30T05:08:18Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=93d4334f7f5bc2f0fb580606f0701b2252c6d8d6'/>
<id>urn:sha1:93d4334f7f5bc2f0fb580606f0701b2252c6d8d6</id>
<content type='text'>
We have switched to Kconfig and the boards.cfg file is going to
be removed. We have to retrieve the board status and maintainers
information from it.

The MAINTAINERS format as in Linux Kernel would be nice
because we can crib the scripts/get_maintainer.pl script.

After some discussion, we chose to put a MAINTAINERS file under each
board directory, not the top-level one because we want to collect
relevant information for a board into a single place.

TODO:
Modify get_maintainer.pl to scan multiple MAINTAINERS files.

Signed-off-by: Masahiro Yamada &lt;yamada.m@jp.panasonic.com&gt;
Suggested-by: Tom Rini &lt;trini@ti.com&gt;
Acked-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>kconfig: add board Kconfig and defconfig files</title>
<updated>2014-07-30T12:48:01Z</updated>
<author>
<name>Masahiro Yamada</name>
<email>yamada.m@jp.panasonic.com</email>
</author>
<published>2014-07-30T05:08:14Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=dd84058d24ff54d6b32818ffe44aeb4bba2cfae6'/>
<id>urn:sha1:dd84058d24ff54d6b32818ffe44aeb4bba2cfae6</id>
<content type='text'>
This commit adds:
 - arch/${ARCH}/Kconfig
    provide a menu to select target boards
 - board/${VENDOR}/${BOARD}/Kconfig or board/${BOARD}/Kconfig
    set CONFIG macros to the appropriate values for each board
 - configs/${TARGET_BOARD}_defconfig
    default setting of each board

(This commit was automatically generated by a conversion script
based on boards.cfg)

In Linux Kernel, defconfig files are located under
arch/${ARCH}/configs/ directory.
It works in Linux Kernel since ARCH is always given from the
command line for cross compile.

But in U-Boot, ARCH is not given from the command line.
Which means we cannot know ARCH until the board configuration is done.
That is why all the "*_defconfig" files should be gathered into a
single directory ./configs/.

Signed-off-by: Masahiro Yamada &lt;yamada.m@jp.panasonic.com&gt;
Acked-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
</feed>
