Re: [PATCH 3/3] drm/msm: a4xx support for msm-drm

2014-11-07 Thread Ganesan, Aravind
On 11/6/2014 2:13 PM, Rob Clark wrote: > On Fri, Oct 31, 2014 at 11:08 AM, Ganesan, Aravind > wrote: >> Added a4xx GPU support. >> >> Signed-off-by: Aravind Ganesan >> --- >> Resend the patch-set with the same thread-id >> Resend in patch-set format and with dri-de...@lists.freedesktop.org on >

Re: [PATCH 2/3] drm/msm: Handle register offset differences between a3xx, and a4xx

2014-11-07 Thread Ganesan, Aravind
On 11/6/2014 2:11 PM, Rob Clark wrote: > On Fri, Oct 31, 2014 at 11:08 AM, Ganesan, Aravind > wrote: >> Register offsets have changed between a3xx and a4xx GPUs. >> To be able access these registers in common code, we create >> a lookup table, and set of read-write APIs to access the >> register

Re: [PATCH] mfd: qcom-spmi-pmic: Add support for more chips versions

2014-11-07 Thread Gilad Avidov
On 11/6/2014 12:54 AM, Ivan T. Ivanov wrote: On Wed, 2014-11-05 at 17:36 -0800, Bjorn Andersson wrote: On Wed, Nov 5, 2014 at 10:31 AM, Ivan T. Ivanov wrote: On Wed, 2014-11-05 at 10:11 -0800, Bjorn Andersson wrote: On Tue, Nov 4, 2014 at 5:33 AM, Ivan T. Ivanov wrote: [..] @@ -28,11 +144,2

Re: [PATCH] tty: serial: msm_serial: Use DT aliases

2014-11-07 Thread Frank Rowand
On 11/7/2014 1:47 AM, Arnd Bergmann wrote: > On Thursday 06 November 2014 22:42:47 Frank Rowand wrote: >> This same change is also needed in: >> >> qcom-ipq8064.dtsi >> qcom-msm8960.dtsi >> qcom-apq8084.dtsi >> qcom-apq8064.dtsi >> qcom-msm8660.dtsi >> >> but I did not want to just blindl

Re: [PATCH 2/3] i2c: qup: Remove .owner field for driver

2014-11-07 Thread Wolfram Sang
On Thu, Oct 09, 2014 at 01:08:32PM +0530, Kiran Padwal wrote: > There is no need to init .owner field. > > Based on the patch from Peter Griffin > "mmc: remove .owner field for drivers using module_platform_driver" > > This patch removes the superfluous .owner field for drivers which > use the m

Re: [PATCH] mfd: qcom-spmi-pmic: Add support for more chips versions

2014-11-07 Thread Ivan T. Ivanov
On Fri, 2014-11-07 at 17:33 +0200, Ivan T. Ivanov wrote: > On Thu, 2014-11-06 at 08:55 -0800, Bjorn Andersson wrote: > > On Wed, Nov 5, 2014 at 11:54 PM, Ivan T. Ivanov wrote: > > > On Wed, 2014-11-05 at 17:36 -0800, Bjorn Andersson wrote: > > > > On Wed, Nov 5, 2014 at 10:31 AM, Ivan T. Ivanov

Re: [PATCH] mfd: qcom-spmi-pmic: Add support for more chips versions

2014-11-07 Thread Ivan T. Ivanov
On Thu, 2014-11-06 at 08:55 -0800, Bjorn Andersson wrote: > On Wed, Nov 5, 2014 at 11:54 PM, Ivan T. Ivanov wrote: > > On Wed, 2014-11-05 at 17:36 -0800, Bjorn Andersson wrote: > > > On Wed, Nov 5, 2014 at 10:31 AM, Ivan T. Ivanov > > > wrote: > [..] > > > > Some of the child device drivers hav

Re: [PATCH V6] UBI: Extend UBI layer debug/messaging capabilities

2014-11-07 Thread Tanya Brokhman
On 11/7/2014 12:08 PM, hujianyang wrote: On 2014/11/5 23:35, Artem Bityutskiy wrote: On Mon, 2014-11-03 at 15:58 +0200, Tanya Brokhman wrote: If there is more then one UBI device mounted, there is no way to distinguish between messages from different UBI devices. Add device number to all ubi la

Re: [PATCH V6] UBI: Extend UBI layer debug/messaging capabilities

2014-11-07 Thread hujianyang
On 2014/11/5 23:35, Artem Bityutskiy wrote: > On Mon, 2014-11-03 at 15:58 +0200, Tanya Brokhman wrote: >> If there is more then one UBI device mounted, there is no way to >> distinguish between messages from different UBI devices. >> Add device number to all ubi layer message types. >> >> The R/O b

Re: [PATCH] tty: serial: msm_serial: Use DT aliases

2014-11-07 Thread Arnd Bergmann
On Thursday 06 November 2014 22:42:47 Frank Rowand wrote: > This same change is also needed in: > > qcom-ipq8064.dtsi > qcom-msm8960.dtsi > qcom-apq8084.dtsi > qcom-apq8064.dtsi > qcom-msm8660.dtsi > > but I did not want to just blindly apply those changes without testing. > Is there

Re: [RFC/PATCH 0/5 v2] mtd:ubi: Read disturb and Data retention handling

2014-11-07 Thread Artem Bityutskiy
On Sun, 2014-11-02 at 15:30 +0200, Tanya Brokhman wrote: > > If NAND why not use ECC to monitor for disturb? > > We don't want just to monitor, we want to prevent cases where ecc cant > be fixed. You said it yourself later on "BCH ECC will tell you if bits > have changed and will correct up to 5