Re: [PATCH v2 10/10] dt-bindings: Add DSIv2 documentation

On 11/21/2015 1:29 AM, Rob Herring wrote: +Stephen On Wed, Nov 18, 2015 at 9:24 AM, Archit Taneja wrote: Hi Rob, On 11/18/2015 6:48 PM, Rob Herring wrote: +dt list On Wed, Nov 18, 2015 at 4:55 AM, Archit Taneja wrote: Add additional

Re: [RFC/PATCH] pinctrl: qcom: Add generic ssbi and spmi GPIO/MPP bindings

> On Nov 18, 2015, at 3:00 AM, Stephen Boyd wrote: > > The drivers don't really need to know which PMIC they're for, so > make a generic binding for them. This alleviates us from updating > the drivers every time a new PMIC comes out. It's still > recommended that we

Re: [RFC/PATCH 0/3] ARM: Use udiv/sdiv for __aeabi_{u}idiv library functions

On Sun, 22 Nov 2015, Arnd Bergmann wrote: > I've also found some /proc/cpuinfo output to cross-reference SoCs > to their core names. > > variant partrevisionnamefeatures > dove: 0 0x581 5 PJ4 idivt I just managed to

Re: [PATCH V6 2/3] dma: add Qualcomm Technologies HIDMA management driver

>>> >>> Can it be like >>> >>> /sys/…/DEVICExx/ >>> channelYY/ >>> attr1 >>> attr2 >>> … >>> >>> ? >> >> I'll work on it. I didn't know that you are allowed to create subdirectories >> in sysfs. I was just creating attributes to keep it simple. But, your >> suggestion is cleaner. >> >>> >>> I

Re: [PATCH 2/2] usb: phy: msm: fix connect/disconnect bug for dragonboard OTG port

On Fri, Nov 20, 2015 at 06:58:59PM -0600, Felipe Balbi wrote: > > Hi, > > Tim Bird writes: > > On 11/16/2015 09:21 AM, Felipe Balbi wrote: > >> > >> Hi, > >> > >> Peter Chen writes: > >>> On Wed, Nov 11, 2015 at 09:48:00AM -0800, Tim Bird

[PATCH V7 0/3] dma: add Qualcomm Technologies HIDMA driver

The Qualcomm Technologies HIDMA device has been designed to support virtualization technology. The driver has been divided into two to follow the hardware design. 1. HIDMA Management driver 2. HIDMA Channel driver Each HIDMA HW consists of multiple channels. These channels share some set of

[PATCH V7 3/3] dma: add Qualcomm Technologies HIDMA channel driver

This patch adds support for hidma engine. The driver consists of two logical blocks. The DMA engine interface and the low-level interface. The hardware only supports memcpy/memset and this driver only support memcpy interface. HW and driver doesn't support slave interface. Signed-off-by: Sinan

[PATCH V7 2/3] dma: add Qualcomm Technologies HIDMA management driver

The Qualcomm Technologies HIDMA device has been designed to support virtualization technology. The driver has been divided into two to follow the hardware design. 1. HIDMA Management driver 2. HIDMA Channel driver Each HIDMA HW consists of multiple channels. These channels share some set of

[PATCH V7 1/3] dma: qcom_bam_dma: move to qcom directory

Creating a QCOM directory for all QCOM DMA source files. Signed-off-by: Sinan Kaya --- drivers/dma/Kconfig| 11 ++- drivers/dma/Makefile | 2 +- drivers/dma/qcom/Kconfig | 8

Re: [RFC/PATCH 0/3] ARM: Use udiv/sdiv for __aeabi_{u}idiv library functions

On 21 November 2015 at 23:21, Arnd Bergmann wrote: > Regarding PJ4, it's still unclear whether that has the same > problem and it only reports idivt when it actually supports idiva, > or whether the lack of idiva support on PJ4 is instead the reason > why the ARM ARM was updated to

Re: [RFC/PATCH 0/3] ARM: Use udiv/sdiv for __aeabi_{u}idiv library functions

On Sunday 22 November 2015 13:29:29 Peter Maydell wrote: > On 21 November 2015 at 23:21, Arnd Bergmann wrote: > > Regarding PJ4, it's still unclear whether that has the same > > problem and it only reports idivt when it actually supports idiva, > > or whether the lack of idiva

Re: [RFC/PATCH 0/3] ARM: Use udiv/sdiv for __aeabi_{u}idiv library functions

Arnd Bergmann writes: > On Sunday 22 November 2015 13:29:29 Peter Maydell wrote: >> On 21 November 2015 at 23:21, Arnd Bergmann wrote: >> > Regarding PJ4, it's still unclear whether that has the same >> > problem and it only reports idivt when it actually supports

Re: [RFC/PATCH 0/3] ARM: Use udiv/sdiv for __aeabi_{u}idiv library functions

On Sun, Nov 22, 2015 at 08:25:27PM +0100, Arnd Bergmann wrote: > The question is really about Marvell Dove, MMP and Armada 370, > which are all based on PJ4 or PJ4B (CPU part : 0x581), so ARMv7-A > and report idivt support but idiva. Well, it's pretty hard to test when binutils blocks your

Re: [PATCH V6 2/3] dma: add Qualcomm Technologies HIDMA management driver

> On Sun, Nov 22, 2015 at 6:37 PM, Sinan Kaya wrote: >> The Qualcomm Technologies HIDMA device has been designed >> to support virtualization technology. The driver has been >> divided into two to follow the hardware design. >> >> 1. HIDMA Management driver >> 2. HIDMA

Re: [RFC/PATCH 0/3] ARM: Use udiv/sdiv for __aeabi_{u}idiv library functions

On Sunday 22 November 2015 19:47:05 Russell King - ARM Linux wrote: > On Sun, Nov 22, 2015 at 08:25:27PM +0100, Arnd Bergmann wrote: > > The question is really about Marvell Dove, MMP and Armada 370, > > which are all based on PJ4 or PJ4B (CPU part : 0x581), so ARMv7-A > > and report idivt support

Re: [RFC/PATCH 0/3] ARM: Use udiv/sdiv for __aeabi_{u}idiv library functions

On Sun, Nov 22, 2015 at 08:58:08PM +0100, Arnd Bergmann wrote: > does it work with -mcpu=cortex-a15? I've tried crosstool as versions > 2.23.52.20130913, 2.24.0.20141017 and 2.25.51.20150518, and they > all seem to behave as expected, failing with -mcpu=cortex-a9 and > marvell-pj4 but succeeding

[PATCH V6 0/3] dma: add Qualcomm Technologies HIDMA driver

been designed to support virtualization technology. The driver has been divided into two to follow the hardware design. 1. HIDMA Management driver 2. HIDMA Channel driver Each HIDMA HW consists of multiple channels. These channels share some set of common parameters. These parameters are

Re: [PATCH V6 2/3] dma: add Qualcomm Technologies HIDMA management driver

On Sun, Nov 22, 2015 at 6:37 PM, Sinan Kaya wrote: > The Qualcomm Technologies HIDMA device has been designed > to support virtualization technology. The driver has been > divided into two to follow the hardware design. > > 1. HIDMA Management driver > 2. HIDMA Channel

[PATCH V6 1/3] dma: qcom_bam_dma: move to qcom directory

Creating a QCOM directory for all QCOM DMA source files. Signed-off-by: Sinan Kaya --- drivers/dma/Kconfig| 11 ++- drivers/dma/Makefile | 2 +- drivers/dma/qcom/Kconfig | 9 +

[PATCH V6 3/3] dma: add Qualcomm Technologies HIDMA channel driver

This patch adds support for hidma engine. The driver consists of two logical blocks. The DMA engine interface and the low-level interface. The hardware only supports memcpy/memset and this driver only support memcpy interface. HW and driver doesn't support slave interface. Signed-off-by: Sinan

[PATCH V6 2/3] dma: add Qualcomm Technologies HIDMA management driver

The Qualcomm Technologies HIDMA device has been designed to support virtualization technology. The driver has been divided into two to follow the hardware design. 1. HIDMA Management driver 2. HIDMA Channel driver Each HIDMA HW consists of multiple channels. These channels share some set of

Re: [PATCH V6 2/3] dma: add Qualcomm Technologies HIDMA management driver

On Sun, Nov 22, 2015 at 9:52 PM, wrote: >> On Sun, Nov 22, 2015 at 6:37 PM, Sinan Kaya wrote: [] >>> + if (!is_power_of_2(mgmtdev->max_write_request) || >>> + (mgmtdev->max_write_request < 128) || >> >> Someone likes parens. > >

Re: [RFC/PATCH 0/3] ARM: Use udiv/sdiv for __aeabi_{u}idiv library functions

On Sunday 22 November 2015 20:03:26 Russell King - ARM Linux wrote: > On Sun, Nov 22, 2015 at 08:58:08PM +0100, Arnd Bergmann wrote: > > does it work with -mcpu=cortex-a15? I've tried crosstool as versions > > 2.23.52.20130913, 2.24.0.20141017 and 2.25.51.20150518, and they > > all seem to behave

Re: [PATCH v4 1/3] Documentation: dt-bindings: add async_irq to msm_hsusb

On Fri, Nov 20, 2015 at 03:47:18PM -0800, Tim Bird wrote: > Add optional async_irq to msm_hsusb binding doc. > > Signed-off-by: Tim Bird Acked-by: Rob Herring > --- > Documentation/devicetree/bindings/usb/msm-hsusb.txt | 10 -- > 1 file

Re: [PATCH v2 1/5] devicetree: bindings: Document qcom board compatible format

On Fri, Nov 20, 2015 at 03:31:16PM -0800, Stephen Boyd wrote: > Some qcom based bootloaders identify the dtb blob based on a set > of device properties like SoC, platform, PMIC, and revisions of > those components. In downstream kernels, these values are added > to the different component dtsi

Re: [RFC/PATCH 0/3] ARM: Use udiv/sdiv for __aeabi_{u}idiv library functions

On Sunday 22 November 2015 20:39:54 Måns Rullgård wrote: > Arnd Bergmann writes: > > > arnd@wuerfel:/tmp$ arm-linux-gnueabihf-gcc -Wall -O2 -mcpu=cortex-a15 > > idiv.c -c -o idiv-arm.o > > arnd@wuerfel:/tmp$ objdump -dr idiv-arm.o > > > > idiv-arm.o: file format