<feed xmlns='http://www.w3.org/2005/Atom'>
<title>u-boot.git/arch/arm/include/asm/ti-common, branch v2015.01</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=v2015.01</id>
<link rel='self' href='http://cgit.235523.xyz/u-boot.git/atom/arch/arm/include/asm/ti-common?h=v2015.01'/>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/'/>
<updated>2014-10-23T15:27:29Z</updated>
<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>
<entry>
<title>net: keystone_net: increase MDIO clock frequency</title>
<updated>2014-10-23T15:27:05Z</updated>
<author>
<name>Vitaly Andrianov</name>
<email>vitalya@ti.com</email>
</author>
<published>2014-09-29T19:17:23Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=f0772266103686abf33fbcf87646b7674d494ec1'/>
<id>urn:sha1:f0772266103686abf33fbcf87646b7674d494ec1</id>
<content type='text'>
With MAC_PHY sgmii configuration, u-boot checks PHY link status before
sending each packet. Increasing MDIO frequency increases overall tftp
speed. We set it to maximum 2.5MHz.

Acked-by: Murali Karicheri &lt;m-karicheri2@ti.com&gt;
Signed-off-by: Vitaly Andrianov &lt;vitalya@ti.com&gt;
Signed-off-by: Ivan Khoronzhuk &lt;ivan.khoronzhuk@ti.com&gt;
</content>
</entry>
<entry>
<title>net: keystone_net: move header file from arch to ti-common</title>
<updated>2014-10-23T15:27:05Z</updated>
<author>
<name>Khoronzhuk, Ivan</name>
<email>ivan.khoronzhuk@ti.com</email>
</author>
<published>2014-09-29T19:17:22Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=0935cac6855626f9de6af9583a30b6463e8bab95'/>
<id>urn:sha1:0935cac6855626f9de6af9583a30b6463e8bab95</id>
<content type='text'>
The header file for the driver should be in correct place.
So move it to "arch/arm/include/asm/ti-common/keystone_net.h"
and correct driver's external dependencies. At the same time
align and correct some definitions.

Acked-by: Murali Karicheri &lt;m-karicheri2@ti.com&gt;
Signed-off-by: Ivan Khoronzhuk &lt;ivan.khoronzhuk@ti.com&gt;
</content>
</entry>
<entry>
<title>dma: keystone_nav: generalize driver usage</title>
<updated>2014-10-23T15:27:04Z</updated>
<author>
<name>Khoronzhuk, Ivan</name>
<email>ivan.khoronzhuk@ti.com</email>
</author>
<published>2014-09-05T16:02:48Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=9ea9021ac466f5ccc8b6238cbce37428bb58f887'/>
<id>urn:sha1:9ea9021ac466f5ccc8b6238cbce37428bb58f887</id>
<content type='text'>
The keystone_nav driver is general driver intended to be used for
working with queue manager and pktdma for different IPs like NETCP,
AIF, FFTC, etc. So the it's API shouldn't be named like it works only
with one of them, it should be general names. The names with prefix
like netcp_* rather do for drivers/net/keystone_net.c driver. So it's
good to generalize this driver to be used for different IP's and
delete confusion with real NETCP driver.

The current netcp_* functions of keystone navigator can be used for
other settings of pktdma, not only for NETCP. The API of this driver
is used by the keystone_net driver to work with NETCP, so net driver
also should be corrected. For convenience collect pkdma
configurations in drivers/dma/keystone_nav_cfg.c.

Acked-by: Vitaly Andrianov &lt;vitalya@ti.com&gt;
Signed-off-by: Ivan Khoronzhuk &lt;ivan.khoronzhuk@ti.com&gt;
</content>
</entry>
<entry>
<title>dma: keystone_nav: move keystone_nav driver to driver/dma/</title>
<updated>2014-10-23T15:27:04Z</updated>
<author>
<name>Khoronzhuk, Ivan</name>
<email>ivan.khoronzhuk@ti.com</email>
</author>
<published>2014-09-05T16:02:47Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=ef4547176d0fa4d43d060a58c0c902add7fe0aed'/>
<id>urn:sha1:ef4547176d0fa4d43d060a58c0c902add7fe0aed</id>
<content type='text'>
The keystone_nav is used by drivers/net/keystone_net.c driver to
send and receive packets, but currently it's placed at keystone
arch sources. So it should be in the drivers directory also.
It's separate driver that can be used for sending and receiving
pktdma packets by others drivers also.

This patch just move this driver to appropriate directory and
doesn't add any functional changes.

Acked-by: Murali Karicheri &lt;m-karicheri2@ti.com&gt;
Signed-off-by: Ivan Khoronzhuk &lt;ivan.khoronzhuk@ti.com&gt;
</content>
</entry>
<entry>
<title>ARM: keystone: aemif: move aemif driver to drivers/memory/ti-aemif.c</title>
<updated>2014-06-19T21:53:58Z</updated>
<author>
<name>Khoronzhuk, Ivan</name>
<email>ivan.khoronzhuk@ti.com</email>
</author>
<published>2014-06-07T02:10:49Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=909ea9aa264423c99cd3039475c98f4a069cb7a4'/>
<id>urn:sha1:909ea9aa264423c99cd3039475c98f4a069cb7a4</id>
<content type='text'>
Move AEMIF driver to drivers/memory/ti-aemif.c along with AEMIF
definitions collected in arch/arm/include/asm/ti-common/ti-aemif.h

Acked-by: Vitaly Andrianov &lt;vitalya@ti.com&gt;
Signed-off-by: Ivan Khoronzhuk &lt;ivan.khoronzhuk@ti.com&gt;
</content>
</entry>
<entry>
<title>mtd: nand: davinci: add header file for driver definitions</title>
<updated>2014-06-19T21:53:58Z</updated>
<author>
<name>Khoronzhuk, Ivan</name>
<email>ivan.khoronzhuk@ti.com</email>
</author>
<published>2014-06-07T01:22:52Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=3e01ed00da98a29fe2b71c6d60309d5b09adc0de'/>
<id>urn:sha1:3e01ed00da98a29fe2b71c6d60309d5b09adc0de</id>
<content type='text'>
The definitions inside emif_defs.h concern davinci nand driver and
should be in it's header. So create header file for davinci nand
driver and move definitions from emif_defs.h and nand_defs.h to it.

Acked-by: Vitaly Andrianov &lt;vitalya@ti.com&gt;
Signed-off-by: Ivan Khoronzhuk &lt;ivan.khoronzhuk@ti.com&gt;
[trini: Fixup more davinci breakage]
Signed-off-by: Tom Rini &lt;trini@ti.com&gt;
</content>
</entry>
</feed>
