On 17/09/17 08:35, Guy Shapiro wrote:
On 26/07/2017 12:01, Srinivas Kandagatla wrote:
On 18/07/17 05:52, Oleksij Rempel wrote:
Hallo all,
Here Gentle Ping to the Old King ;)
DT is already ACKed.
Thanks for patience, As this is a new driver it will be queued for 4.14 just before 4.13-rc5 is released.
thanks,
srini
Looks like this patchset is not included in 4.14-rc1.
Is it still on someone's queue?
Not sure Why I missed this patch..!!Sorry about that !!
Just sent them to Greg Now to pick it up for 4.14 next rc..
thanks,
srini
On 20.06.2017 09:09, Oleksij Rempel wrote:
changes v7:
- split imx6ul patch and squash it with with main patches.
- spell fixes in the binding documentation
- return regmap_bulk_read directly.
changes v6:
- check if device is writable by reading GPR_SL and GPR_HL bits
- use regmap_bulk_* functions instead of while() { regmap_read/write }
- add patch for imx6ul
changes v5:
- use dcfg->offset instead of priv->offset.
changes v4:
- change dependencies in Kconfig
- remove unused includes and order them alphabetically
- set MODULE_LICENSE = GPL v2
- remove unused int err variable
changes v3:
- remove regmap and offset properties.
changes v2:
- correct typos: Registe, parrent...
Oleksij Rempel (3):
nvmem: dt: document SNVS LPGPR binding
nvmem: add snvs_lpgpr driver
ARM: dts: imx6qdl.dtsi/imx6ul.dtsi: add "fsl,imx6q-snvs-lpgpr" node
.../devicetree/bindings/nvmem/snvs-lpgpr.txt | 20 +++
arch/arm/boot/dts/imx6qdl.dtsi | 4 +
arch/arm/boot/dts/imx6ul.dtsi | 4 +
drivers/nvmem/Kconfig | 10 ++
drivers/nvmem/Makefile | 2 +
drivers/nvmem/snvs_lpgpr.c | 155 +++++++++++++++++++++
6 files changed, 195 insertions(+)
create mode 100644 Documentation/devicetree/bindings/nvmem/snvs-lpgpr.txt
create mode 100644 drivers/nvmem/snvs_lpgpr.c
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
