<feed xmlns='http://www.w3.org/2005/Atom'>
<title>u-boot.git/arch/arm/include/asm/ti-common, 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/arch/arm/include/asm/ti-common?h=v2016.09</id>
<link rel='self' href='http://cgit.235523.xyz/u-boot.git/atom/arch/arm/include/asm/ti-common?h=v2016.09'/>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/'/>
<updated>2016-06-06T17:39:12Z</updated>
<entry>
<title>Fix to davinci_nand.h to place CEnCFG registers at correct</title>
<updated>2016-06-06T17:39:12Z</updated>
<author>
<name>Peter Howard</name>
<email>pjh@northern-ridge.com.au</email>
</author>
<published>2016-06-02T03:19:26Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=c165994299281957d735f5ec8863dda6243c3456'/>
<id>urn:sha1:c165994299281957d735f5ec8863dda6243c3456</id>
<content type='text'>
Signed-off-by: Peter Howard &lt;phoward@gme.net.au&gt;
</content>
</entry>
<entry>
<title>driver: net: keystone_net: add support for rgmii phy</title>
<updated>2015-10-22T18:22:23Z</updated>
<author>
<name>Vitaly Andrianov</name>
<email>vitalya@ti.com</email>
</author>
<published>2015-09-19T10:56:50Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=4657a2d44ed06272c1fb1d6f5b842e93ceddbbb6'/>
<id>urn:sha1:4657a2d44ed06272c1fb1d6f5b842e93ceddbbb6</id>
<content type='text'>
In K2G, Ethernet doesn't support SGMII instead it support RGMII,
adding support to the driver to connect to RGMII phy.

Signed-off-by: Vitaly Andrianov &lt;vitalya@ti.com&gt;
Signed-off-by: Mugunthan V N &lt;mugunthanvnm@ti.com&gt;
Signed-off-by: Lokesh Vutla &lt;lokeshvutla@ti.com&gt;
</content>
</entry>
<entry>
<title>driver: net: keystone_net: fix phy mode configuration</title>
<updated>2015-10-22T18:22:22Z</updated>
<author>
<name>Mugunthan V N</name>
<email>mugunthanvnm@ti.com</email>
</author>
<published>2015-09-19T10:56:48Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=bf7bd4e725105fc0f6f43df6d01d85c6df3ce4eb'/>
<id>urn:sha1:bf7bd4e725105fc0f6f43df6d01d85c6df3ce4eb</id>
<content type='text'>
Phy mode is a board property and it can be different between
multiple board and ports, so it should not be hardcoded in
driver to one specific mode. So adding a field in eth_priv_t
structure to pass phy mode to driver.

Signed-off-by: Mugunthan V N &lt;mugunthanvnm@ti.com&gt;
Signed-off-by: Lokesh Vutla &lt;lokeshvutla@ti.com&gt;
</content>
</entry>
<entry>
<title>ARM: k2g: Add clock information</title>
<updated>2015-10-22T18:22:16Z</updated>
<author>
<name>Vitaly Andrianov</name>
<email>vitalya@ti.com</email>
</author>
<published>2015-09-19T10:56:41Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=e6d71e1ca5dc40e871e53ad0d14d68676cf92601'/>
<id>urn:sha1:e6d71e1ca5dc40e871e53ad0d14d68676cf92601</id>
<content type='text'>
Add clock information for Galileo

Signed-off-by: Vitaly Andrianov &lt;vitalya@ti.com&gt;
Signed-off-by: Lokesh Vutla &lt;lokeshvutla@ti.com&gt;
Signed-off-by: Mugunthan V N &lt;mugunthanvnm@ti.com&gt;
</content>
</entry>
<entry>
<title>dma: ti-edma3: Add helper function to support edma3 transfer</title>
<updated>2015-08-17T17:59:15Z</updated>
<author>
<name>Vignesh R</name>
<email>vigneshr@ti.com</email>
</author>
<published>2015-08-17T07:59:55Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=664ab2c992d1e06c4381f66c93d2e155fc7722e1'/>
<id>urn:sha1:664ab2c992d1e06c4381f66c93d2e155fc7722e1</id>
<content type='text'>
Signed-off-by: Vignesh R &lt;vigneshr@ti.com&gt;
Reviewed-by: Jagan Teki &lt;jteki@openedev.com&gt;
</content>
</entry>
<entry>
<title>omap-common: Common boot code OMAP3 support and cleanup</title>
<updated>2015-07-27T19:02:03Z</updated>
<author>
<name>Paul Kocialkowski</name>
<email>contact@paulk.fr</email>
</author>
<published>2015-07-15T14:02:19Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=60c7c30aa084588ef974663be3d22a1de7f66cbb'/>
<id>urn:sha1:60c7c30aa084588ef974663be3d22a1de7f66cbb</id>
<content type='text'>
This introduces OMAP3 support for the common omap boot code, as well as a
major cleanup of the common omap boot code.

First, the omap_boot_parameters structure becomes platform-specific, since its
definition differs a bit across omap platforms. The offsets are removed as well
since it is U-Boot's coding style to use structures for mapping such kind of
data (in the sense that it is similar to registers). It is correct to assume
that romcode structure encoding is the same as U-Boot, given the description
of these structures in the TRMs.

The original address provided by the bootrom is passed to the U-Boot binary
instead of a duplicate of the structure stored in global data. This allows to
have only the relevant (boot device and mode) information stored in global data.
It is also expected that the address where the bootrom stores that information
is not overridden by the U-Boot SPL or U-Boot.

The save_omap_boot_params is expected to handle all special cases where the data
provided by the bootrom cannot be used as-is, so that spl_boot_device and
spl_boot_mode only return the data from global data.

All of this is only relevant when the U-Boot SPL is used. In cases it is not,
save_boot_params should fallback to its weak (or board-specific) definition.
save_omap_boot_params should not be called in that context either.

Signed-off-by: Paul Kocialkowski &lt;contact@paulk.fr&gt;
</content>
</entry>
<entry>
<title>dma: ti-edma3: introduce edma3 driver</title>
<updated>2014-10-23T15:27:29Z</updated>
<author>
<name>Khoronzhuk, Ivan</name>
<email>ivan.khoronzhuk@ti.com</email>
</author>
<published>2014-10-22T14:47:56Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=e165b1d34cd91cb42b0614792aa88e0677944ee7'/>
<id>urn:sha1:e165b1d34cd91cb42b0614792aa88e0677944ee7</id>
<content type='text'>
The EDMA3 controller’s primary purpose is to service data transfers
that you program between two memory-mapped slave endpoints on the device.

Typical usage includes, but is not limited to the following:
- Servicing software-driven paging transfers (e.g., transfers from external
  memory, such as SDRAM to internal device memory, such as DSP L2 SRAM)
- Servicing event-driven peripherals, such as a serial port
- Performing sorting or sub-frame extraction of various data structures
- Offloading data transfers from the main device DSP(s)
- See the device-specific data manual for specific peripherals that are
  accessible via the EDMA3 controller

Signed-off-by: Ivan Khoronzhuk &lt;ivan.khoronzhuk@ti.com&gt;
</content>
</entry>
<entry>
<title>net: keystone_net: register eth PHYs on MDIO bus</title>
<updated>2014-10-23T15:27:28Z</updated>
<author>
<name>Khoronzhuk, Ivan</name>
<email>ivan.khoronzhuk@ti.com</email>
</author>
<published>2014-10-17T17:44:35Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=3fe93623cc5f5c5373fe0c0b7fe331f8800f4350'/>
<id>urn:sha1:3fe93623cc5f5c5373fe0c0b7fe331f8800f4350</id>
<content type='text'>
As MDIO bus has been added we can register PHYs with it.
After registration, the PHY driver will be probed according to the
hardware on board.

Startup PHY at the ethernet open.

Use phy_startup() instead of keystone_get_link_status() when eth open,
as it verifies PHY link inside and SGMII link is checked before.

For K2HK evm PHY configuration at init was absent, so don't enable
phy config at init for k2hk evm.

Acked-by: Vitaly Andrianov &lt;vitalya@ti.com&gt;
Signed-off-by: Ivan Khoronzhuk &lt;ivan.khoronzhuk@ti.com&gt;
</content>
</entry>
<entry>
<title>soc: keystone_serdes: generalize to be used by other sub systems</title>
<updated>2014-10-23T15:27:28Z</updated>
<author>
<name>Hao Zhang</name>
<email>hzhang@ti.com</email>
</author>
<published>2014-10-22T14:18:23Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=92a16c81f5c5b43779520dbc7278f3d7cfb24684'/>
<id>urn:sha1:92a16c81f5c5b43779520dbc7278f3d7cfb24684</id>
<content type='text'>
SerDes driver is used by other sub systems like PCI, sRIO etc.
So modify it to be more general. The SerDes driver provides common
API's that can also be extended for other peripherals SerDes
configurations.

Signed-off-by: Hao Zhang &lt;hzhang@ti.com&gt;
Signed-off-by: Ivan Khoronzhuk &lt;ivan.khoronzhuk@ti.com&gt;
</content>
</entry>
<entry>
<title>soc: keystone_serdes: create a separate SGMII SerDes driver</title>
<updated>2014-10-23T15:27:28Z</updated>
<author>
<name>Khoronzhuk, Ivan</name>
<email>ivan.khoronzhuk@ti.com</email>
</author>
<published>2014-10-22T14:18:21Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=a43febde4452f254621c0c95d452c89ad498e959'/>
<id>urn:sha1:a43febde4452f254621c0c95d452c89ad498e959</id>
<content type='text'>
This patch split the Keystone II SGMII SerDes related code from
Ethernet driver and create a separate SGMII SerDes driver.
The SerDes driver can be used by others keystone subsystems
like PCI, sRIO, so move it to driver/soc/keystone directory.

Add soc specific drivers directory like in the Linux kernel.
It is going to be used by keysotone soc specific drivers.

Signed-off-by: Hao Zhang &lt;hzhang@ti.com&gt;
Signed-off-by: Ivan Khoronzhuk &lt;ivan.khoronzhuk@ti.com&gt;
</content>
</entry>
</feed>
