Re: next boot: 34 pass, 5 fail (next-20140122)

2014-01-22 Thread Tero Kristo
On 01/23/2014 03:35 AM, Kevin Hilman wrote: On Wed, Jan 22, 2014 at 4:46 PM, Kevin's boot bot wrote: Automated DT boot report for various ARM defconfigs. Tree/Branch: next Git describe: next-20140122 Failed boot tests (console logs at th

Re: [PATCH 1/2] ARM: omapfb: add coherent dma memory support

2014-01-22 Thread Ivaylo Dimitrov
Hmm, maybe this https://lkml.org/lkml/2014/1/22/386 will solve our issues Ivo -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [PATCH v2 1/5] ARM: dts: omap3: Add support for INCOstartec a83x module

2014-01-22 Thread Nishanth Menon
On 01/22/2014 01:04 PM, Christoph Fritz wrote: > INCOstartec LILLY-A83X module is a TI DM3730xx100 (OMAP3) SoC > computer-on-module. > > This patch adds device tree support for most of its features. > > Signed-off-by: Christoph Fritz > --- > arch/arm/boot/dts/omap3-lilly-a83x.dtsi | 445 > +++

Re: [PATCH v2 4/5] ARM: OMAP2+: Add pdata quirk for sys_clkout2 for omap3 DBB056

2014-01-22 Thread Nishanth Menon
On 01/22/2014 01:04 PM, Christoph Fritz wrote: > Full device tree support for clock control is not yet accomplished. Until > then, configure the 24Mhz of sys_clkout2 to feed an USB-Hub here. > > Signed-off-by: Christoph Fritz > --- > arch/arm/mach-omap2/pdata-quirks.c | 37 > +

Re: [PATCH v2 5/5] [RFC] omapdss: remove FEAT_DPI_USES_VDDS_DSI from omap3

2014-01-22 Thread Javier Martinez Canillas
Hello Christoph, On 01/22/2014 04:04 PM, Christoph Fritz wrote: > DBB056 doesn't use DSI for its display, but omap3 forces this > erroneously for all its boards: > > | OMAP DSS rev 2.0 > | omapdss DPI error: can't get VDDS_DSI regulator > | omapfb omapfb: failed to connect default display >

[PATCH v2 1/5] ARM: dts: omap3: Add support for INCOstartec a83x module

2014-01-22 Thread Christoph Fritz
INCOstartec LILLY-A83X module is a TI DM3730xx100 (OMAP3) SoC computer-on-module. This patch adds device tree support for most of its features. Signed-off-by: Christoph Fritz --- arch/arm/boot/dts/omap3-lilly-a83x.dtsi | 445 +++ 1 file changed, 445 insertions(+) c

[PATCH v2 3/5] ARM: OMAP2+: add legacy display for omap3 DBB056

2014-01-22 Thread Christoph Fritz
Full device tree support for omapdss is not yet accomplished. Until then, init display by legacy platform code. Signed-off-by: Christoph Fritz --- arch/arm/mach-omap2/dss-common.c | 49 arch/arm/mach-omap2/dss-common.h |1 + arch/arm/mach-omap2/pdat

[PATCH v2 4/5] ARM: OMAP2+: Add pdata quirk for sys_clkout2 for omap3 DBB056

2014-01-22 Thread Christoph Fritz
Full device tree support for clock control is not yet accomplished. Until then, configure the 24Mhz of sys_clkout2 to feed an USB-Hub here. Signed-off-by: Christoph Fritz --- arch/arm/mach-omap2/pdata-quirks.c | 37 1 file changed, 37 insertions(+) diff --

[PATCH v2 5/5] [RFC] omapdss: remove FEAT_DPI_USES_VDDS_DSI from omap3

2014-01-22 Thread Christoph Fritz
DBB056 doesn't use DSI for its display, but omap3 forces this erroneously for all its boards: | OMAP DSS rev 2.0 | omapdss DPI error: can't get VDDS_DSI regulator | omapfb omapfb: failed to connect default display | omapfb omapfb: failed to init overlay connections | omapfb omapfb: faile

[PATCH v2 2/5] ARM: dts: omap3: Add support for INCOstartec DBB056 baseboard

2014-01-22 Thread Christoph Fritz
INCOstartec LILLY-DBB056 is a carrier board (baseboard) for computer-on-module LILLY-A83X. This patch adds device-tree support for most of its features. Signed-off-by: Christoph Fritz --- arch/arm/boot/dts/Makefile |1 + arch/arm/boot/dts/omap3-lilly-dbb056.dts | 160

[PATCH v2 0/5] ARM: add omap3 INCOstartec board support

2014-01-22 Thread Christoph Fritz
This set of patches adds board support for an omap3 system from INCOstartec. It's based on next-20140122. Previously it was based on next-20140115. There, everything works as expected. On branch git://git.linaro.org/people/ulf.hansson/clk.git linaro_clk/clk-next which holdes all &quo

[net-next PATCH v2 1/1] drivers: net: cpsw: enable promiscuous mode support

2014-01-22 Thread Mugunthan V N
Enable promiscuous mode support for CPSW. Signed-off-by: Mugunthan V N --- drivers/net/ethernet/ti/cpsw.c | 105 - drivers/net/ethernet/ti/cpsw_ale.c | 16 ++ drivers/net/ethernet/ti/cpsw_ale.h | 2 + 3 files changed, 98 insertions(+), 25 deletions(

Re: [net-next PATCH 1/1] drivers: net: cpsw: enable promiscuous mode support

2014-01-22 Thread Mugunthan V N
On Wednesday 22 January 2014 07:41 AM, David Miller wrote: > From: Mugunthan V N > Date: Mon, 20 Jan 2014 17:38:38 +0530 > >> +if (!enable && ((priv->slaves[0].ndev->flags & IFF_PROMISC) || >> +(priv->slaves[1].ndev->flags & IFF_PROMISC))) { > This assumptio

Re: [net-next PATCH 1/1] drivers: net: cpsw: enable promiscuous mode support

2014-01-22 Thread Mugunthan V N
On Wednesday 22 January 2014 07:41 AM, David Miller wrote: > From: Mugunthan V N > Date: Mon, 20 Jan 2014 17:38:38 +0530 > >> +if (!enable && ((priv->slaves[0].ndev->flags & IFF_PROMISC) || >> +(priv->slaves[1].ndev->flags & IFF_PROMISC))) { > This assumptio

Re: [PATCH RFC 08/26] dmaengine: omap-dma: consolidate setup of CCR

2014-01-22 Thread Santosh Shilimkar
On Wednesday 22 January 2014 09:19 AM, Russell King - ARM Linux wrote: > On Wed, Jan 22, 2014 at 06:25:57PM +0530, Sricharan R wrote: >> Setting up of DMA_DST_SYNC_PREFETCH is missing after this ? > > I'm not looking for the DMA engine driver to be a 100% reimplementation > of the legacy driver.

Re: [PATCH RFC 08/26] dmaengine: omap-dma: consolidate setup of CCR

2014-01-22 Thread Russell King - ARM Linux
On Wed, Jan 22, 2014 at 06:25:57PM +0530, Sricharan R wrote: > Setting up of DMA_DST_SYNC_PREFETCH is missing after this ? I'm not looking for the DMA engine driver to be a 100% reimplementation of the legacy driver. Rather than supporting the entire set of features which the legacy driver did, a

Re: [PATCH RFC 03/26] dmaengine: omap-dma: program hardware directly

2014-01-22 Thread Russell King - ARM Linux
On Wed, Jan 22, 2014 at 06:24:33PM +0530, Sricharan R wrote: > EI and FI are always set to zero. So interleaved transfers support > have to enabled in omap-dma, as it was supported by the > legacy driver. It was not enabled because of no users of the feature, > right ? None of the users of the l

Re: [PATCH RFC 08/26] dmaengine: omap-dma: consolidate setup of CCR

2014-01-22 Thread Sricharan R
Hi Russell, On Thursday 02 January 2014 08:40 PM, Russell King wrote: > Consolidate the setup of the channel control register. Prepare the > basic value in the preparation of the DMA descriptor, and write it into > the register upon descriptor execution. > > Signed-off-by: Russell King > --- >

Re: [PATCH RFC 03/26] dmaengine: omap-dma: program hardware directly

2014-01-22 Thread Sricharan R
On Thursday 02 January 2014 08:39 PM, Russell King wrote: > Program the transfer parameters directly into the hardware, rather > than using the functions in arch/arm/plat-omap/dma.c. > > Signed-off-by: Russell King > --- > drivers/dma/omap-dma.c | 144 -

[PATCH] ARM: dts: add BeagleBone Audio Cape (Rev A) dtsi

2014-01-22 Thread Jack Mitchell
From: Jack Mitchell Devicetree include file for setting up the am335x mcasp bus, i2c-2 bus, and audio codec required for a functioning BeagleBone Audio Cape. Signed-off-by: Jack Mitchell Signed-off-by: Matt Porter --- arch/arm/boot/dts/am335x-bone-audio-cape-reva.dtsi | 124 ++

Re: [alsa-devel] [PATCH RFC v2 REPOST 3/8] ASoC: davinci-evm: HDMI audio support for TDA998x trough McASP I2S bus

2014-01-22 Thread Jean-Francois Moine
On Wed, 22 Jan 2014 11:19:53 +0100 Jean-Francois Moine wrote: > As both I2S and S/PDIF may be used for HDMI output in the Cubox, > I wrote a tda998x CODEC which gets the audio ports from the DT and > dynamically sets these ports and the audio type (i2s / spdif) on audio > streaming start. I have

Re: [alsa-devel] [PATCH RFC v2 REPOST 3/8] ASoC: davinci-evm: HDMI audio support for TDA998x trough McASP I2S bus

2014-01-22 Thread Jean-Francois Moine
On Wed, 22 Jan 2014 11:20:32 +0200 Jyri Sarha wrote: > On 01/15/2014 05:51 PM, Jean-Francois Moine wrote: > > On Wed, 15 Jan 2014 13:27:21 +0200 > > Jyri Sarha wrote: > > > >> From driver/gpu/drm/i2c/tda998x_drv.c. The driver configures CTS_N > >> register statically to a value that works only

Re: [PATCH v4 2/2] usb: dwc3: adapt dwc3 core to use Generic PHY Framework

2014-01-22 Thread Kishon Vijay Abraham I
On Wednesday 22 January 2014 01:29 PM, Roger Quadros wrote: > On 01/22/2014 08:04 AM, Vivek Gautam wrote: >> Hi, >> >> >> On Tue, Jan 21, 2014 at 7:30 PM, Roger Quadros wrote: >>> Hi Kishon, >>> >>> On 01/21/2014 12:11 PM, Kishon Vijay Abraham I wrote: Adapted dwc3 core to use the Generic PHY

[PATCH 1/4] power_supply: Add inlmt,iterm, min/max temp props

2014-01-22 Thread Jenny TC
Add new power supply properties for input current, charge termination current, min and max temperature POWER_SUPPLY_PROP_TEMP_MIN - minimum operatable temperature POWER_SUPPLY_PROP_TEMP_MAX - maximum operatable temperature POWER_SUPPLY_PROP_INLMT - input current limit programmed by charger. Indic

[PATCH 3/4] power_supply: Introduce PSE compliant algorithm

2014-01-22 Thread Jenny TC
As per Product Safety Engineering (PSE) specification for battery charging, the battery characteristics and thereby the charging rates can vary on different temperature zones. This patch introduces a PSE compliant charging algorithm with maintenance charging support. The algorithm can be selected b

[PATCH 4/4] power_supply: bq24261 charger driver

2014-01-22 Thread Jenny TC
This patch introduces BQ24261 charger driver. The driver makes use of power supply charging driver to setup charging. So the driver does hardware abstraction and handles h/w specific corner cases. The charging logic resides with power supply charging driver Signed-off-by: Jenny TC --- drivers/po

[PATCH v3 0/4] power_supply: Introduce power supply charging driver

2014-01-22 Thread Jenny TC
v1: introduced feature as a framework within power supply class driver with separate files for battid framework and charging framework v2: fixed review comments, moved macros and inline functions to power_supply.h v3: moved the feature as a separate driver, combined battid framework and

Re: [alsa-devel] [PATCH RFC v2 REPOST 3/8] ASoC: davinci-evm: HDMI audio support for TDA998x trough McASP I2S bus

2014-01-22 Thread Jyri Sarha
On 01/15/2014 05:51 PM, Jean-Francois Moine wrote: On Wed, 15 Jan 2014 13:27:21 +0200 Jyri Sarha wrote: From driver/gpu/drm/i2c/tda998x_drv.c. The driver configures CTS_N register statically to a value that works only with 4 byte samples. According to my tests it is possible to support 3 and

Re: [PATCHv3 00/41] OMAPDSS: DT support v3

2014-01-22 Thread Tomi Valkeinen
On 2014-01-21 23:29, Nishanth Menon wrote: > Tomi, > > On 01/21/2014 04:56 AM, Tomi Valkeinen wrote: >> Hi, >> >> Here's version 3 of the DSS DT series. >> >> The previous version can be found from: >> >> v1: http://permalink.gmane.org/gmane.linux.ports.arm.omap/108249 >> v2: http://permalink.gman

Re: [PATCH v4 2/2] usb: dwc3: adapt dwc3 core to use Generic PHY Framework

2014-01-22 Thread Roger Quadros
On 01/22/2014 08:04 AM, Vivek Gautam wrote: > Hi, > > > On Tue, Jan 21, 2014 at 7:30 PM, Roger Quadros wrote: >> Hi Kishon, >> >> On 01/21/2014 12:11 PM, Kishon Vijay Abraham I wrote: >>> Adapted dwc3 core to use the Generic PHY Framework. So for init, exit, >>> power_on and power_off the follow