Josh Cartwright | 1 Oct 19:03 2014

[PATCH 0/4] Add KPSS watchdog driver to relevant device trees

Now that the Krait Processor Sub-system (KPSS) Watchdog driver has been pulled
into Wim's tree destined for 3.18, add descriptions of the WDT in the relevant
device trees, and include the driver in qcom_defconfig.

Josh Cartwright (4):
  ARM: qcom: add QCOM_WDT driver to qcom_defconfig
  ARM: qcom: add description of KPSS WDT for IPQ8064
  ARM: qcom: add description of KPSS WDT for APQ8064
  ARM: qcom: add description of KPSS WDT for MSM8960

 arch/arm/boot/dts/qcom-apq8064.dtsi | 15 +++++++++++++++
 arch/arm/boot/dts/qcom-ipq8064.dtsi | 15 +++++++++++++++
 arch/arm/boot/dts/qcom-msm8960.dtsi | 15 +++++++++++++++
 arch/arm/configs/qcom_defconfig     |  2 ++
 4 files changed, 47 insertions(+)


Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation

Ivan T. Ivanov | 1 Oct 18:30 2014

[PATCH v5 0/4] Qualcomm SPMI PMIC pin controller drivers

Changes since v4:

- Use PMIC name in compatible string.
- PINCTRL_QCOM_SPMI_PMIC from Kconfig symbol.
- Remove pmic string from drivers file names.
- Fixed coding style issues.
- Use qcom-spmi-gpio and qcom-spmi-mpp from dirver names,
  to be similar to qcom-spmi-iadc, qcom-spmi-vadc and 
  qcom-spmi-temp-alarm drivers.

Short description:

Patches adds pin control drivers for Multi-Purpose Pin (MPP) and
General-purpose pin (GPIO) controllers found in Qualcomm SPMI based
PMIC chips.

MPP's are enhanced GPIO's with analog circuits, which support 
analog and digital input/output.

v4: <at>

Bjorn Andersson (1):
  pinctrl: Device tree bindings for Qualcomm PMIC GPIO block

Ivan T. Ivanov (3):
  pinctrl: Device tree bindings for Qualcomm PMIC MPP block
  pinctrl: Qualcomm SPMI PMIC GPIO pin controller driver
  pinctrl: Qualcomm SPMI PMIC MPP pin controller driver

 .../devicetree/bindings/pinctrl/qcom,pmic-gpio.txt | 215 +++++
(Continue reading)

Mike Rapoport | 1 Oct 18:09 2014

[PATCH v4] ARM: dts: qcom: add CM-QS600 board

CM-QS600 is a APQ8064 based computer on module.
The details are available at

Signed-off-by: Mike Rapoport <mike.rapoport <at>>
Acked-by: Igor Grinberg <grinberg <at>>
v2 changes: duplicate the settings for the cm-qs600 board in its .dts file as Kumar suggested
v3 changes: add board details and keep dts Makefile sorted alphabetically
v4 changes: fix eeprom defintion and update subject as per Igor's comments

 arch/arm/boot/dts/Makefile                  |  1 +
 arch/arm/boot/dts/qcom-apq8064-cm-qs600.dts | 59 +++++++++++++++++++++++++++++
 2 files changed, 60 insertions(+)
 create mode 100644 arch/arm/boot/dts/qcom-apq8064-cm-qs600.dts

diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
index aaa1a68..3243722 100644
--- a/arch/arm/boot/dts/Makefile
+++ b/arch/arm/boot/dts/Makefile
 <at>  <at>  -339,6 +339,7  <at>  <at>  dtb-$(CONFIG_ARCH_ORION5X) += orion5x-lacie-d2-network.dtb \
 dtb-$(CONFIG_ARCH_PRIMA2) += prima2-evb.dtb
 dtb-$(CONFIG_ARCH_QCOM) += \
+	qcom-apq8064-cm-qs600.dtb \
 	qcom-apq8064-ifc6410.dtb \
 	qcom-apq8074-dragonboard.dtb \
 	qcom-apq8084-ifc6540.dtb \
diff --git a/arch/arm/boot/dts/qcom-apq8064-cm-qs600.dts b/arch/arm/boot/dts/qcom-apq8064-cm-qs600.dts
new file mode 100644
(Continue reading)

Ivan T. Ivanov | 1 Oct 17:53 2014

[PATCH v3] thermal: Add QPNP PMIC temperature alarm driver

Add support for the temperature alarm peripheral found inside
Qualcomm plug-and-play (QPNP) PMIC chips.  The temperature alarm
peripheral outputs a pulse on an interrupt line whenever the
thermal over temperature stage value changes.  Implement an ISR
to manage this interrupt.

Register a thermal zone device in sysfs with multiple trip points
corresponding to the physical threshold temperatures between over
temperature stages.  The temperature reported by this thermal
zone device should reflect the actual PMIC die temperature if an
ADC is present on the given PMIC.  If no ADC is present, then the
reported temperature should be estimated from the over
temperature stage value.

Send a notification to userspace via sysfs_notify() whenever the
over temperature stage value changes.

Cc: David Collins <collinsd <at>>
Signed-off-by: Ivan T. Ivanov <iivanov <at>>

Changes since v2:

- Fixed review comments from Kiran Padwal
- Files renamed from qpnp-* to qcom-spmi-* to be inline with
  other PMIC sub-function drivers like qcom-spmi-iadc and


(Continue reading)

Tim Bird | 1 Oct 00:49 2014

[PATCH v3] ARM: dts: Add initial DTS file for Sony Xperia Z1 phone

This DTS has support for the Sony Xperia Z1 phone (codenamed Honami).
This first version of the DTS supports just a serial console.

changes from V2
 - fixed dtb name in Makefile

changes from v1
 - removed qcom,msm-id attribute
 - removed mis-capitalized Qualcomm word
 - changed dts file name
 - added board-specific compatible-string

Signed-off-by: Tim Bird <tim.bird <at>>
Tested-by: Kevin Hilman <khilman <at>>

This version fixes the dtb name.  I asked previously about adding to qcom_dt_match,
but apparently board compatibles are being removed from that list in

Kevin tested this (modulu re-adding back the qcom,msm-id).  I have a new
mkqcdtbootimg which works without requiring the qcom,msm-id attribute,
that I'll send to Kevin shortly (and publish on github).

 Documentation/devicetree/bindings/vendor-prefixes.txt |  1 +
 arch/arm/boot/dts/Makefile                            |  3 ++-
 arch/arm/boot/dts/qcom-msm8974-sony-xperia-honami.dts | 17 +++++++++++++++++
 3 files changed, 20 insertions(+), 1 deletion(-)
 create mode 100644 arch/arm/boot/dts/qcom-msm8974-sony-xperia-honami.dts
(Continue reading)

Andy Gross | 30 Sep 23:21 2014

[Patch v3] spi: qup: Fix incorrect block transfers

This patch fixes a number of errors with the QUP block transfer mode.  Errors
manifested themselves as input underruns, output overruns, and timed out

The block mode does not require the priming that occurs in FIFO mode.  At the
moment that the QUP is placed into the RUN state, the QUP will immediately raise
an interrupt if the request is a write.  Therefore, there is no need to prime
the pump.

In addition, the block transfers require that whole blocks of data are
read/written at a time.  The last block of data that completes a transaction may
contain less than a full blocks worth of data.

Each block of data results in an input/output service interrupt accompanied with
a input/output block flag set.  Additional block reads/writes require clearing
of the service flag.  It is ok to check for additional blocks of data in the
ISR, but you have to ack every block you transfer.  Imbalanced acks result in
early return from complete transactions with pending interrupts that still have
to be ack'd.  The next transaction can be affected by these interrupts.
Transactions are deemed complete when the MAX_INPUT or MAX_OUTPUT flag are set.

Changes from v2:
- Added in additional completion check so that transaction done is not
  prematurely signaled.
- Fixed various review comments.

Changes from v1:
- Split out read/write block function.
- Removed extraneous checks for transfer length

(Continue reading)

Bjorn Andersson | 30 Sep 06:35 2014

[PATCH v4] hwspinlock: qcom: Add support for Qualcomm HW Mutex block

From: Kumar Gala <galak <at>>

Add driver for Qualcomm Hardware Mutex block that exists on newer
Qualcomm SoCs.

Cc: Jeffrey Hugo <jhugo <at>>
Cc: Eric Holmberg <eholmber <at>>
Cc: Courtney Cavin <courtney.cavin <at>>
Signed-off-by: Kumar Gala <galak <at>>
[bjorn: added pm_runtime calls, from Courtney,
	added sfpb-mutex compatible,
	updated DT binding documentation formatting,
	replaced msm prefix with qcom,
	cleaned up includes]
Signed-off-by: Bjorn Andersson <bjorn.andersson <at>>

We need this driver to add support for the shared memory manager, so I'm
reviving Kumars patch from a year ago, with some additional sprinkles on top.

Changes since v3:
 - Reverted back to getting stride from of_match, per Kumars request

Changes since v2:
 - Changed prefix to qcom
 - Cleaned up includes
 - Rely on reg and num-locks to figure out stride, instead of of_match data

Changes since v1:
(Continue reading)

小贺 | 29 Sep 05:03 2014

用了一次你就会觉得是最好的短信发送平台 th9



(Continue reading)

Tanya Brokhman | 28 Sep 08:37 2014

[RFC/PATCH 4/5] mtd: ubi: Read threshold verification

From: Tatyana Brokhman <tlinder <at>>

One of the criteria to scrub an eraseblock due to read disturb issue is
if that eraseblock was read from more times then a pre-defined threshold.
This is verified at each LEB read according to the read counter
parameter of the read PEB.
An eraseblock that is found needs scrubbing is added to the ubi->scrub

Signed-off-by: Tanya Brokhman <tlinder <at>>
 drivers/mtd/ubi/eba.c |  7 ++++++-
 drivers/mtd/ubi/wl.c  | 56 +++++++++++++++++++++++++++++++++++++++++++++------
 2 files changed, 56 insertions(+), 7 deletions(-)

diff --git a/drivers/mtd/ubi/eba.c b/drivers/mtd/ubi/eba.c
index 0e11671d..1c7b5f9 100644
--- a/drivers/mtd/ubi/eba.c
+++ b/drivers/mtd/ubi/eba.c
 <at>  <at>  -1,5 +1,8  <at>  <at> 
  * Copyright (c) International Business Machines Corp., 2006
+ * Copyright (c) 2014, Linux Foundation. All rights reserved.
+ * Linux Foundation chooses to take subject only to the GPLv2
+ * license terms, and distributes only under these terms.
  * This program is free software; you can redistribute it and/or modify
  * it under the terms of the GNU General Public License as published by
 <at>  <at>  -466,8 +469,10  <at>  <at>  retry:
 			goto out_unlock;
(Continue reading)

Tanya Brokhman | 28 Sep 08:37 2014

[RFC/PATCH 1/5] mtd: ubi: Read disturb infrastructure

The need for performing read disturb is determined according to new
statistics collected per eraseblock:
- read counter: incremented at each read operation
                reset at each erase
- last erase time stamp: updated at each erase

This patch adds the infrastructure for the above statistics

Signed-off-by: Tanya Brokhman <tlinder <at>>
 drivers/mtd/ubi/build.c     | 57 +++++++++++++++++++++++++++++++++++++++++++++
 drivers/mtd/ubi/fastmap.c   | 14 +++++++----
 drivers/mtd/ubi/ubi-media.h | 32 ++++++++++++++++++++++---
 drivers/mtd/ubi/ubi.h       | 34 +++++++++++++++++++++++++++
 drivers/mtd/ubi/wl.c        |  6 +++++
 5 files changed, 135 insertions(+), 8 deletions(-)

diff --git a/drivers/mtd/ubi/build.c b/drivers/mtd/ubi/build.c
index 6e30a3c..34fe23a 100644
--- a/drivers/mtd/ubi/build.c
+++ b/drivers/mtd/ubi/build.c
 <at>  <at>  -1,6 +1,9  <at>  <at> 
  * Copyright (c) International Business Machines Corp., 2006
  * Copyright (c) Nokia Corporation, 2007
+ * Copyright (c) 2014, Linux Foundation. All rights reserved.
+ * Linux Foundation chooses to take subject only to the GPLv2
+ * license terms, and distributes only under these terms.
  * This program is free software; you can redistribute it and/or modify
(Continue reading)

Tanya Brokhman | 28 Sep 08:36 2014

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

One of the limitations of the NAND devices is the method used to read
NAND flash memory may cause bit-flips on the surrounding cells and result
in uncorrectable ECC errors. This is known as the read disturb or data

Today’s Linux NAND drivers implementation doesn’t address the read disturb
and the data retention limitations of the NAND devices. To date these
issues could be overlooked since the possibility of their occurrence in
today’s NAND devices is very low. 

With the evolution of NAND devices and the requirement for a “long life”
NAND flash, read disturb and data retention can no longer be ignored
otherwise there will be data loss over time.

The following patch set implements handling of Read-disturb and Data
retention by the UBI layer.

Tanya Brokhman (2):
  mtd: ubi: Read disturb infrastructure
  mtd: ubi: Add sysfs entry to force all pebs' scan

Tatyana Brokhman (3):
  mtd: ubi: Fill read disturb statistics
  mtd: ubi: Make in_wl_tree function public
  mtd: ubi: Read threshold verification

 drivers/mtd/ubi/attach.c    | 137 ++++++++++++++++------
 drivers/mtd/ubi/build.c     |  81 +++++++++++++
 drivers/mtd/ubi/debug.c     |  11 ++
 drivers/mtd/ubi/eba.c       |   7 +-
(Continue reading)