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

On 11/12, Rob Herring wrote: > On Mon, Oct 26, 2015 at 02:25:10PM -0700, 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

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

On Wed, Nov 11, 2015 at 09:48:00AM -0800, Tim Bird wrote: > > > On 11/10/2015 07:14 PM, Peter Chen wrote: > > On Tue, Nov 10, 2015 at 04:46:51PM -0800, Tim Bird wrote: > >> This fixes a bug where if you disconnect and re-connect the USB cable, > >> the gadget driver stops working. > >> > >> Add

Re: [kbuild-all] [PATCH V3 4/4] dma: add Qualcomm Technologies HIDMA channel driver

Hi Arnd, On Wed, Nov 11, 2015 at 09:42:00AM +0100, Arnd Bergmann wrote: > On Wednesday 11 November 2015 10:21:03 Fengguang Wu wrote: > > Hi Sinan, > > > > Sorry please ignore this warning -- it's actually a problem specific > > to the mn10300 arch. I'll disable such warning in mn10300 in future.

Re: [PATCH V4 2/4] dma: add Qualcomm Technologies HIDMA management driver

On Thu, Nov 12, 2015 at 8:41 AM, 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

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

On 11/12, Rob Herring wrote: > On Thu, Nov 12, 2015 at 1:44 PM, Stephen Boyd wrote: > > On 11/12, Rob Herring wrote: > >> On Mon, Oct 26, 2015 at 02:25:10PM -0700, Stephen Boyd wrote: > > >> > +Some qcom based bootloaders identify the dtb blob based on a set of > >> >

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

On 11/12, Olof Johansson wrote: > On Mon, Oct 26, 2015 at 2:25 PM, Stephen Boyd wrote: > > +Examples: > > + > > + "qcom,msm8916-v1-cdp-pm8916-v2.1" > > This is just awkward, but this... > > > + > > +A CDP board with an msm8916 SoC, version 1 paired with a pm8916 PMIC

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

Hi, On Mon, Oct 26, 2015 at 2:25 PM, 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

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

On Thu, Nov 12, 2015 at 6:11 PM, Stephen Boyd wrote: > On 11/12, Rob Herring wrote: >> On Thu, Nov 12, 2015 at 1:44 PM, Stephen Boyd wrote: >> > On 11/12, Rob Herring wrote: >> >> On Mon, Oct 26, 2015 at 02:25:10PM -0700, Stephen Boyd wrote: >> >> >> >

Re: [PATCH v2 2/2] clk: qcom: Make oxili GDSC parent of oxili_cx GDSC

On 11/13/2015 11:44 AM, Stephen Boyd wrote: > On 11/13, Rajendra Nayak wrote: >> >> On 10/07/2015 01:02 AM, Stephen Boyd wrote: >>> On 10/01, Stephen Boyd wrote: The oxili_cx GDSC is inside the power domain of the oxili GDSC. Add the dependency so that the CX domain can properly power

Re: [PATCH v2 2/2] clk: qcom: Make oxili GDSC parent of oxili_cx GDSC

On 10/07/2015 01:02 AM, Stephen Boyd wrote: > On 10/01, Stephen Boyd wrote: >> The oxili_cx GDSC is inside the power domain of the oxili GDSC. >> Add the dependency so that the CX domain can properly power up. >> >> Reported-by: Rob Clark >> Cc: Rajendra Nayak

Re: [PATCH v2 2/2] clk: qcom: Make oxili GDSC parent of oxili_cx GDSC

On 11/13, Rajendra Nayak wrote: > > On 10/07/2015 01:02 AM, Stephen Boyd wrote: > > On 10/01, Stephen Boyd wrote: > >> The oxili_cx GDSC is inside the power domain of the oxili GDSC. > >> Add the dependency so that the CX domain can properly power up. > >> > >> Reported-by: Rob Clark

Re: [PATCH V4 1/4] dma: qcom_bam_dma: move to qcom directory

Sinan Kaya wrote: @@ -1,5 +1,5 @@ /* - * Copyright (c) 2013-2014, The Linux Foundation. All rights reserved. + * Copyright (c) 2013-2015, The Linux Foundation. All rights reserved. I don't think this is appropriate. You're not making any real changes to this driver, so you can't make any

Re: [kbuild-all] [PATCH V3 4/4] dma: add Qualcomm Technologies HIDMA channel driver

On Thursday 12 November 2015 16:20:15 Fengguang Wu wrote: > Hi Arnd, > > On Wed, Nov 11, 2015 at 09:42:00AM +0100, Arnd Bergmann wrote: > > On Wednesday 11 November 2015 10:21:03 Fengguang Wu wrote: > > > Hi Sinan, > > > > > > Sorry please ignore this warning -- it's actually a problem specific

Re: [PATCH v5] sched: fix incorrect wait time and wait count statistics

At present scheduler resets task's wait start timestamp when the task migrates to another rq. This misleads scheduler itself into reporting less wait time than actual by omitting time spent for waiting prior to migration and also more wait count than actual by counting migration as wait end event

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

On 11/12, Rob Herring wrote: > On Thu, Nov 12, 2015 at 6:11 PM, Stephen Boyd wrote: > > On 11/12, Rob Herring wrote: > >> On Thu, Nov 12, 2015 at 1:44 PM, Stephen Boyd wrote: > >> > On 11/12, Rob Herring wrote: > >> >> On Mon, Oct 26, 2015 at

Re: [PATCH v2 02/17] scsi: ufs: add option to change default UFS power management level

On Mon, Oct 26, 2015 at 05:40:57PM +0200, Yaniv Gardi wrote: > UFS device and link can be put in multiple different low power modes > hence UFS driver supports multiple different low power modes. > By default UFS driver selects the default (optimal) low power mode > (which gives moderate power

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

On Mon, Oct 26, 2015 at 02:25:10PM -0700, 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: [PATCH 1/3] devicetree: bindings: Document qcom board compatible format

On Thu, Nov 12, 2015 at 1:44 PM, Stephen Boyd wrote: > On 11/12, Rob Herring wrote: >> On Mon, Oct 26, 2015 at 02:25:10PM -0700, Stephen Boyd wrote: >> > Some qcom based bootloaders identify the dtb blob based on a set >> > of device properties like SoC, platform, PMIC, and