u-boot.git/drivers/serial, branch v2014.10-rc1

Merge branch 'u-boot-ti/master' into 'u-boot-arm/master'

2014-07-28T10:26:21Z

Merge branch 'u-boot-sh/rmobile' into 'u-boot-arm/master'

2014-07-28T08:54:54Z

keystone2: use CONFIG_SOC_KEYSTONE in common places

2014-07-25T20:26:11Z

Use CONFIG_SOC_KEYSTONE in common places instead of defining a lot of "if def .. || if def " for different Keystone2 SoC types. Acked-by: Murali Karicheri Signed-off-by: Ivan Khoronzhuk

serial: sh: Add support R8A7794

2014-07-24T05:03:46Z

This adds the preset value to register for R8A7794. Signed-off-by: Nobuhiro Iwamatsu

Add a flag indicating when the serial console is ready

2014-07-23T13:07:25Z

For sandbox we have a fallback console which is used very early in U-Boot, before serial drivers are available. Rather than try to guess when to switch to the real console, add a flag so we can be sure. This makes sure that sandbox can always output a panic() message, for example, and avoids silent failure (which is very annoying in sandbox). Signed-off-by: Simon Glass

stdio: Pass device pointer to stdio methods

2014-07-23T13:07:23Z

At present stdio device functions do not get any clue as to which stdio device is being acted on. Some implementations go to great lengths to work around this, such as defining a whole separate set of functions for each possible device. For driver model we need to associate a stdio_dev with a device. It doesn't seem possible to continue with this work-around approach. Instead, add a stdio_dev pointer to each of the stdio member functions. Note: The serial drivers have the same problem, but it is not strictly necessary to fix that to get driver model running. Also, if we convert serial over to driver model the problem will go away. Code size increases by 244 bytes for Thumb2 and 428 for PowerPC. 22: stdio: Pass device pointer to stdio methods arm: (for 2/2 boards) all +244.0 bss -4.0 text +248.0 powerpc: (for 1/1 boards) all +428.0 text +428.0 Signed-off-by: Simon Glass Acked-by: Marek Vasut Reviewed-by: Marek Vasut

serial: ns16550: use a const variable instead of macro

2014-07-22T11:44:25Z

Just for type checking. Signed-off-by: Masahiro Yamada Cc: Marek Vasut Acked-by: Marek Vasut

serial: ns16550: use DIV_ROUND_CLOSEST macro to compute the divisor

2014-07-22T11:44:25Z

The function still returns the same value. The comment block is no longer necessary because our intention is clear enough by using DIV_ROUND_CLOSEST() macro. Signed-off-by: Masahiro Yamada

serial: ns16550: drop CONFIG_OMAP1610 from the special case

2014-07-22T11:44:25Z

If CONFIG_OMAP1610 is defined, the code returning the fixed value (26) is enabled. But this case is covered by the following code. (CONFIG_SYS_NS16550_CLK + (gd->baudrate * (MODE_X_DIV / 2))) / (MODE_X_DIV * gd->baudrate) = (48000000 + (115200 * (16 / 2))) / (16 * 115200) = 48921600 / 1843200 = 26 The "#ifdef CONFIG_OMAP1610" was added by commit 6f21347d more than ten years ago. In those days, the divide-and-round was not used. I guess that is why this weird code was added here. Signed-off-by: Masahiro Yamada Cc: Tom Rini Cc: Rishi Bhattacharya

serial_mxc: disable new features of autobaud detection

2014-05-28T15:37:47Z

Bit 7 of UCR3 is described in the i.MX3x/i.MX5x/i.MX6x reference manuals as follows: Autobaud Detection Not Improved-. Disables new features of autobaud detection (See Baud Rate Automatic Detection Protocol, for more details). 0 Autobaud detection new features selected 1 Keep old autobaud detection mechanism On at least i.MX6DQ, i.MX6DLS and i.MX53, the "new features" occasionally cause the receiver to get out of sync and continuously produce received characters of '\xff'. This patch disables the "new feature" on all boards, since there's no support for auto-baud in U-Boot on any of them. More details are available in this post on i.MX Community: https://community.freescale.com/message/403254 Signed-off-by: Eric Nelson Tested-by: Fabio Estevam Acked-by: Stefano Babic