* [PATCH 0/4] nvmem: new drivers for v4.5 @ 2015-12-07 10:56 ` Srinivas Kandagatla 0 siblings, 0 replies; 21+ messages in thread From: Srinivas Kandagatla @ 2015-12-07 10:56 UTC (permalink / raw) To: gregkh Cc: linux-kernel, maxime.ripard, linux-arm-kernel, andrew-ct.chen, ariel, Srinivas Kandagatla Hi Greg, Here are 2 new nvmem drivers which are in the mailing list for long time and are good to go for some testing and find its way to v4.5-rc*. Could you please take these patches via char-misc tree. Thanks, srini Andrew-CT Chen (2): dt-bindings: add document of mediatek efuse driver nvmem: mediatek: Add Mediatek EFUSE driver Ariel D'Alessandro (2): DT: nvmem: Add NXP LPC18xx EEPROM memory binding documentation nvmem: NXP LPC18xx EEPROM memory NVMEM driver .../devicetree/bindings/nvmem/lpc1857-eeprom.txt | 28 ++ .../devicetree/bindings/nvmem/mtk-efuse.txt | 36 +++ drivers/nvmem/Kconfig | 20 ++ drivers/nvmem/Makefile | 4 + drivers/nvmem/lpc18xx_eeprom.c | 330 +++++++++++++++++++++ drivers/nvmem/mtk-efuse.c | 89 ++++++ 6 files changed, 507 insertions(+) create mode 100644 Documentation/devicetree/bindings/nvmem/lpc1857-eeprom.txt create mode 100644 Documentation/devicetree/bindings/nvmem/mtk-efuse.txt create mode 100644 drivers/nvmem/lpc18xx_eeprom.c create mode 100644 drivers/nvmem/mtk-efuse.c -- 1.9.1 ^ permalink raw reply [flat|nested] 21+ messages in thread
* [PATCH 0/4] nvmem: new drivers for v4.5 @ 2015-12-07 10:56 ` Srinivas Kandagatla 0 siblings, 0 replies; 21+ messages in thread From: Srinivas Kandagatla @ 2015-12-07 10:56 UTC (permalink / raw) To: linux-arm-kernel Hi Greg, Here are 2 new nvmem drivers which are in the mailing list for long time and are good to go for some testing and find its way to v4.5-rc*. Could you please take these patches via char-misc tree. Thanks, srini Andrew-CT Chen (2): dt-bindings: add document of mediatek efuse driver nvmem: mediatek: Add Mediatek EFUSE driver Ariel D'Alessandro (2): DT: nvmem: Add NXP LPC18xx EEPROM memory binding documentation nvmem: NXP LPC18xx EEPROM memory NVMEM driver .../devicetree/bindings/nvmem/lpc1857-eeprom.txt | 28 ++ .../devicetree/bindings/nvmem/mtk-efuse.txt | 36 +++ drivers/nvmem/Kconfig | 20 ++ drivers/nvmem/Makefile | 4 + drivers/nvmem/lpc18xx_eeprom.c | 330 +++++++++++++++++++++ drivers/nvmem/mtk-efuse.c | 89 ++++++ 6 files changed, 507 insertions(+) create mode 100644 Documentation/devicetree/bindings/nvmem/lpc1857-eeprom.txt create mode 100644 Documentation/devicetree/bindings/nvmem/mtk-efuse.txt create mode 100644 drivers/nvmem/lpc18xx_eeprom.c create mode 100644 drivers/nvmem/mtk-efuse.c -- 1.9.1 ^ permalink raw reply [flat|nested] 21+ messages in thread
* [PATCH 1/4] DT: nvmem: Add NXP LPC18xx EEPROM memory binding documentation 2015-12-07 10:56 ` Srinivas Kandagatla @ 2015-12-07 10:57 ` Srinivas Kandagatla -1 siblings, 0 replies; 21+ messages in thread From: Srinivas Kandagatla @ 2015-12-07 10:57 UTC (permalink / raw) To: gregkh Cc: linux-kernel, maxime.ripard, linux-arm-kernel, andrew-ct.chen, ariel, Srinivas Kandagatla From: Ariel D'Alessandro <ariel@vanguardiasur.com.ar> Add the devicetree binding document for NXP LPC18xx EEPROM memory. Signed-off-by: Ariel D'Alessandro <ariel@vanguardiasur.com.ar> Acked-by: Stefan Wahren <stefan.wahren@i2se.com> Acked-by: Rob Herring <robh@kernel.org> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org> --- .../devicetree/bindings/nvmem/lpc1857-eeprom.txt | 28 ++++++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 Documentation/devicetree/bindings/nvmem/lpc1857-eeprom.txt diff --git a/Documentation/devicetree/bindings/nvmem/lpc1857-eeprom.txt b/Documentation/devicetree/bindings/nvmem/lpc1857-eeprom.txt new file mode 100644 index 0000000..809df68 --- /dev/null +++ b/Documentation/devicetree/bindings/nvmem/lpc1857-eeprom.txt @@ -0,0 +1,28 @@ +* NXP LPC18xx EEPROM memory NVMEM driver + +Required properties: + - compatible: Should be "nxp,lpc1857-eeprom" + - reg: Must contain an entry with the physical base address and length + for each entry in reg-names. + - reg-names: Must include the following entries. + - reg: EEPROM registers. + - mem: EEPROM address space. + - clocks: Must contain an entry for each entry in clock-names. + - clock-names: Must include the following entries. + - eeprom: EEPROM operating clock. + - resets: Should contain a reference to the reset controller asserting + the EEPROM in reset. + - interrupts: Should contain EEPROM interrupt. + +Example: + + eeprom: eeprom@4000e000 { + compatible = "nxp,lpc1857-eeprom"; + reg = <0x4000e000 0x1000>, + <0x20040000 0x4000>; + reg-names = "reg", "mem"; + clocks = <&ccu1 CLK_CPU_EEPROM>; + clock-names = "eeprom"; + resets = <&rgu 27>; + interrupts = <4>; + }; -- 1.9.1 ^ permalink raw reply related [flat|nested] 21+ messages in thread
* [PATCH 1/4] DT: nvmem: Add NXP LPC18xx EEPROM memory binding documentation @ 2015-12-07 10:57 ` Srinivas Kandagatla 0 siblings, 0 replies; 21+ messages in thread From: Srinivas Kandagatla @ 2015-12-07 10:57 UTC (permalink / raw) To: linux-arm-kernel From: Ariel D'Alessandro <ariel@vanguardiasur.com.ar> Add the devicetree binding document for NXP LPC18xx EEPROM memory. Signed-off-by: Ariel D'Alessandro <ariel@vanguardiasur.com.ar> Acked-by: Stefan Wahren <stefan.wahren@i2se.com> Acked-by: Rob Herring <robh@kernel.org> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org> --- .../devicetree/bindings/nvmem/lpc1857-eeprom.txt | 28 ++++++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 Documentation/devicetree/bindings/nvmem/lpc1857-eeprom.txt diff --git a/Documentation/devicetree/bindings/nvmem/lpc1857-eeprom.txt b/Documentation/devicetree/bindings/nvmem/lpc1857-eeprom.txt new file mode 100644 index 0000000..809df68 --- /dev/null +++ b/Documentation/devicetree/bindings/nvmem/lpc1857-eeprom.txt @@ -0,0 +1,28 @@ +* NXP LPC18xx EEPROM memory NVMEM driver + +Required properties: + - compatible: Should be "nxp,lpc1857-eeprom" + - reg: Must contain an entry with the physical base address and length + for each entry in reg-names. + - reg-names: Must include the following entries. + - reg: EEPROM registers. + - mem: EEPROM address space. + - clocks: Must contain an entry for each entry in clock-names. + - clock-names: Must include the following entries. + - eeprom: EEPROM operating clock. + - resets: Should contain a reference to the reset controller asserting + the EEPROM in reset. + - interrupts: Should contain EEPROM interrupt. + +Example: + + eeprom: eeprom at 4000e000 { + compatible = "nxp,lpc1857-eeprom"; + reg = <0x4000e000 0x1000>, + <0x20040000 0x4000>; + reg-names = "reg", "mem"; + clocks = <&ccu1 CLK_CPU_EEPROM>; + clock-names = "eeprom"; + resets = <&rgu 27>; + interrupts = <4>; + }; -- 1.9.1 ^ permalink raw reply related [flat|nested] 21+ messages in thread
* [PATCH 2/4] nvmem: NXP LPC18xx EEPROM memory NVMEM driver 2015-12-07 10:56 ` Srinivas Kandagatla @ 2015-12-07 10:57 ` Srinivas Kandagatla -1 siblings, 0 replies; 21+ messages in thread From: Srinivas Kandagatla @ 2015-12-07 10:57 UTC (permalink / raw) To: gregkh Cc: linux-kernel, maxime.ripard, linux-arm-kernel, andrew-ct.chen, ariel, Srinivas Kandagatla From: Ariel D'Alessandro <ariel@vanguardiasur.com.ar> This commit adds support for NXP LPC18xx EEPROM memory found in NXP LPC185x/3x and LPC435x/3x/2x/1x devices. EEPROM size is 16384 bytes and it can be entirely read and written/erased with 1 word (4 bytes) granularity. The last page (128 bytes) contains the EEPROM initialization data and is not writable. Erase/program time is less than 3ms. The EEPROM device requires a ~1500 kHz clock (min 800 kHz, max 1600 kHz) that is generated dividing the system bus clock by the division factor, contained in the divider register (minus 1 encoded). EEPROM will be kept in Power Down mode except during read/write calls. Signed-off-by: Ariel D'Alessandro <ariel@vanguardiasur.com.ar> Acked-by: Stefan Wahren <stefan.wahren@i2se.com> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org> --- drivers/nvmem/Kconfig | 9 ++ drivers/nvmem/Makefile | 2 + drivers/nvmem/lpc18xx_eeprom.c | 330 +++++++++++++++++++++++++++++++++++++++++ 3 files changed, 341 insertions(+) create mode 100644 drivers/nvmem/lpc18xx_eeprom.c diff --git a/drivers/nvmem/Kconfig b/drivers/nvmem/Kconfig index bc4ea58..6ff1b50 100644 --- a/drivers/nvmem/Kconfig +++ b/drivers/nvmem/Kconfig @@ -25,6 +25,15 @@ config NVMEM_IMX_OCOTP This driver can also be built as a module. If so, the module will be called nvmem-imx-ocotp. +config NVMEM_LPC18XX_EEPROM + tristate "NXP LPC18XX EEPROM Memory Support" + depends on ARCH_LPC18XX || COMPILE_TEST + help + Say Y here to include support for NXP LPC18xx EEPROM memory found in + NXP LPC185x/3x and LPC435x/3x/2x/1x devices. + To compile this driver as a module, choose M here: the module + will be called nvmem_lpc18xx_eeprom. + config NVMEM_MXS_OCOTP tristate "Freescale MXS On-Chip OTP Memory Support" depends on ARCH_MXS || COMPILE_TEST diff --git a/drivers/nvmem/Makefile b/drivers/nvmem/Makefile index 95dde3f..c14a556 100644 --- a/drivers/nvmem/Makefile +++ b/drivers/nvmem/Makefile @@ -8,6 +8,8 @@ nvmem_core-y := core.o # Devices obj-$(CONFIG_NVMEM_IMX_OCOTP) += nvmem-imx-ocotp.o nvmem-imx-ocotp-y := imx-ocotp.o +obj-$(CONFIG_NVMEM_LPC18XX_EEPROM) += nvmem_lpc18xx_eeprom.o +nvmem_lpc18xx_eeprom-y := lpc18xx_eeprom.o obj-$(CONFIG_NVMEM_MXS_OCOTP) += nvmem-mxs-ocotp.o nvmem-mxs-ocotp-y := mxs-ocotp.o obj-$(CONFIG_QCOM_QFPROM) += nvmem_qfprom.o diff --git a/drivers/nvmem/lpc18xx_eeprom.c b/drivers/nvmem/lpc18xx_eeprom.c new file mode 100644 index 0000000..878fce7 --- /dev/null +++ b/drivers/nvmem/lpc18xx_eeprom.c @@ -0,0 +1,330 @@ +/* + * NXP LPC18xx/LPC43xx EEPROM memory NVMEM driver + * + * Copyright (c) 2015 Ariel D'Alessandro <ariel@vanguardiasur.com> + * + * This program is free software; you can redistribute it and/or modify it + * under the terms of the GNU General Public License version 2 as published by + * the Free Software Foundation. + */ + +#include <linux/clk.h> +#include <linux/device.h> +#include <linux/delay.h> +#include <linux/err.h> +#include <linux/io.h> +#include <linux/module.h> +#include <linux/nvmem-provider.h> +#include <linux/platform_device.h> +#include <linux/regmap.h> +#include <linux/reset.h> + +/* Registers */ +#define LPC18XX_EEPROM_AUTOPROG 0x00c +#define LPC18XX_EEPROM_AUTOPROG_WORD 0x1 + +#define LPC18XX_EEPROM_CLKDIV 0x014 + +#define LPC18XX_EEPROM_PWRDWN 0x018 +#define LPC18XX_EEPROM_PWRDWN_NO 0x0 +#define LPC18XX_EEPROM_PWRDWN_YES 0x1 + +#define LPC18XX_EEPROM_INTSTAT 0xfe0 +#define LPC18XX_EEPROM_INTSTAT_END_OF_PROG BIT(2) + +#define LPC18XX_EEPROM_INTSTATCLR 0xfe8 +#define LPC18XX_EEPROM_INTSTATCLR_PROG_CLR_ST BIT(2) + +/* Fixed page size (bytes) */ +#define LPC18XX_EEPROM_PAGE_SIZE 0x80 + +/* EEPROM device requires a ~1500 kHz clock (min 800 kHz, max 1600 kHz) */ +#define LPC18XX_EEPROM_CLOCK_HZ 1500000 + +/* EEPROM requires 3 ms of erase/program time between each writing */ +#define LPC18XX_EEPROM_PROGRAM_TIME 3 + +struct lpc18xx_eeprom_dev { + struct clk *clk; + void __iomem *reg_base; + void __iomem *mem_base; + struct nvmem_device *nvmem; + unsigned reg_bytes; + unsigned val_bytes; +}; + +static struct regmap_config lpc18xx_regmap_config = { + .reg_bits = 32, + .reg_stride = 4, + .val_bits = 32, +}; + +static inline void lpc18xx_eeprom_writel(struct lpc18xx_eeprom_dev *eeprom, + u32 reg, u32 val) +{ + writel(val, eeprom->reg_base + reg); +} + +static inline u32 lpc18xx_eeprom_readl(struct lpc18xx_eeprom_dev *eeprom, + u32 reg) +{ + return readl(eeprom->reg_base + reg); +} + +static int lpc18xx_eeprom_busywait_until_prog(struct lpc18xx_eeprom_dev *eeprom) +{ + unsigned long end; + u32 val; + + /* Wait until EEPROM program operation has finished */ + end = jiffies + msecs_to_jiffies(LPC18XX_EEPROM_PROGRAM_TIME * 10); + + while (time_is_after_jiffies(end)) { + val = lpc18xx_eeprom_readl(eeprom, LPC18XX_EEPROM_INTSTAT); + + if (val & LPC18XX_EEPROM_INTSTAT_END_OF_PROG) { + lpc18xx_eeprom_writel(eeprom, LPC18XX_EEPROM_INTSTATCLR, + LPC18XX_EEPROM_INTSTATCLR_PROG_CLR_ST); + return 0; + } + + usleep_range(LPC18XX_EEPROM_PROGRAM_TIME * USEC_PER_MSEC, + (LPC18XX_EEPROM_PROGRAM_TIME + 1) * USEC_PER_MSEC); + } + + return -ETIMEDOUT; +} + +static int lpc18xx_eeprom_gather_write(void *context, const void *reg, + size_t reg_size, const void *val, + size_t val_size) +{ + struct lpc18xx_eeprom_dev *eeprom = context; + unsigned int offset = *(u32 *)reg; + int ret; + + if (offset % lpc18xx_regmap_config.reg_stride) + return -EINVAL; + + lpc18xx_eeprom_writel(eeprom, LPC18XX_EEPROM_PWRDWN, + LPC18XX_EEPROM_PWRDWN_NO); + + /* Wait 100 us while the EEPROM wakes up */ + usleep_range(100, 200); + + while (val_size) { + writel(*(u32 *)val, eeprom->mem_base + offset); + ret = lpc18xx_eeprom_busywait_until_prog(eeprom); + if (ret < 0) + return ret; + + val_size -= eeprom->val_bytes; + val += eeprom->val_bytes; + offset += eeprom->val_bytes; + } + + lpc18xx_eeprom_writel(eeprom, LPC18XX_EEPROM_PWRDWN, + LPC18XX_EEPROM_PWRDWN_YES); + + return 0; +} + +static int lpc18xx_eeprom_write(void *context, const void *data, size_t count) +{ + struct lpc18xx_eeprom_dev *eeprom = context; + unsigned int offset = eeprom->reg_bytes; + + if (count <= offset) + return -EINVAL; + + return lpc18xx_eeprom_gather_write(context, data, eeprom->reg_bytes, + data + offset, count - offset); +} + +static int lpc18xx_eeprom_read(void *context, const void *reg, size_t reg_size, + void *val, size_t val_size) +{ + struct lpc18xx_eeprom_dev *eeprom = context; + unsigned int offset = *(u32 *)reg; + + lpc18xx_eeprom_writel(eeprom, LPC18XX_EEPROM_PWRDWN, + LPC18XX_EEPROM_PWRDWN_NO); + + /* Wait 100 us while the EEPROM wakes up */ + usleep_range(100, 200); + + while (val_size) { + *(u32 *)val = readl(eeprom->mem_base + offset); + val_size -= eeprom->val_bytes; + val += eeprom->val_bytes; + offset += eeprom->val_bytes; + } + + lpc18xx_eeprom_writel(eeprom, LPC18XX_EEPROM_PWRDWN, + LPC18XX_EEPROM_PWRDWN_YES); + + return 0; +} + +static struct regmap_bus lpc18xx_eeprom_bus = { + .write = lpc18xx_eeprom_write, + .gather_write = lpc18xx_eeprom_gather_write, + .read = lpc18xx_eeprom_read, + .reg_format_endian_default = REGMAP_ENDIAN_NATIVE, + .val_format_endian_default = REGMAP_ENDIAN_NATIVE, +}; + +static bool lpc18xx_eeprom_writeable_reg(struct device *dev, unsigned int reg) +{ + /* + * The last page contains the EEPROM initialization data and is not + * writable. + */ + return reg <= lpc18xx_regmap_config.max_register - + LPC18XX_EEPROM_PAGE_SIZE; +} + +static bool lpc18xx_eeprom_readable_reg(struct device *dev, unsigned int reg) +{ + return reg <= lpc18xx_regmap_config.max_register; +} + +static struct nvmem_config lpc18xx_nvmem_config = { + .name = "lpc18xx-eeprom", + .owner = THIS_MODULE, +}; + +static int lpc18xx_eeprom_probe(struct platform_device *pdev) +{ + struct lpc18xx_eeprom_dev *eeprom; + struct device *dev = &pdev->dev; + struct reset_control *rst; + unsigned long clk_rate; + struct regmap *regmap; + struct resource *res; + int ret; + + eeprom = devm_kzalloc(dev, sizeof(*eeprom), GFP_KERNEL); + if (!eeprom) + return -ENOMEM; + + res = platform_get_resource_byname(pdev, IORESOURCE_MEM, "reg"); + eeprom->reg_base = devm_ioremap_resource(dev, res); + if (IS_ERR(eeprom->reg_base)) + return PTR_ERR(eeprom->reg_base); + + res = platform_get_resource_byname(pdev, IORESOURCE_MEM, "mem"); + eeprom->mem_base = devm_ioremap_resource(dev, res); + if (IS_ERR(eeprom->mem_base)) + return PTR_ERR(eeprom->mem_base); + + eeprom->clk = devm_clk_get(&pdev->dev, "eeprom"); + if (IS_ERR(eeprom->clk)) { + dev_err(&pdev->dev, "failed to get eeprom clock\n"); + return PTR_ERR(eeprom->clk); + } + + ret = clk_prepare_enable(eeprom->clk); + if (ret < 0) { + dev_err(dev, "failed to prepare/enable eeprom clk: %d\n", ret); + return ret; + } + + rst = devm_reset_control_get(dev, NULL); + if (IS_ERR(rst)) { + dev_err(dev, "failed to get reset: %ld\n", PTR_ERR(rst)); + ret = PTR_ERR(rst); + goto err_clk; + } + + ret = reset_control_assert(rst); + if (ret < 0) { + dev_err(dev, "failed to assert reset: %d\n", ret); + goto err_clk; + } + + eeprom->val_bytes = lpc18xx_regmap_config.val_bits / BITS_PER_BYTE; + eeprom->reg_bytes = lpc18xx_regmap_config.reg_bits / BITS_PER_BYTE; + + /* + * Clock rate is generated by dividing the system bus clock by the + * division factor, contained in the divider register (minus 1 encoded). + */ + clk_rate = clk_get_rate(eeprom->clk); + clk_rate = DIV_ROUND_UP(clk_rate, LPC18XX_EEPROM_CLOCK_HZ) - 1; + lpc18xx_eeprom_writel(eeprom, LPC18XX_EEPROM_CLKDIV, clk_rate); + + /* + * Writing a single word to the page will start the erase/program cycle + * automatically + */ + lpc18xx_eeprom_writel(eeprom, LPC18XX_EEPROM_AUTOPROG, + LPC18XX_EEPROM_AUTOPROG_WORD); + + lpc18xx_eeprom_writel(eeprom, LPC18XX_EEPROM_PWRDWN, + LPC18XX_EEPROM_PWRDWN_YES); + + lpc18xx_regmap_config.max_register = resource_size(res) - 1; + lpc18xx_regmap_config.writeable_reg = lpc18xx_eeprom_writeable_reg; + lpc18xx_regmap_config.readable_reg = lpc18xx_eeprom_readable_reg; + + regmap = devm_regmap_init(dev, &lpc18xx_eeprom_bus, eeprom, + &lpc18xx_regmap_config); + if (IS_ERR(regmap)) { + dev_err(dev, "regmap init failed: %ld\n", PTR_ERR(regmap)); + ret = PTR_ERR(regmap); + goto err_clk; + } + + lpc18xx_nvmem_config.dev = dev; + + eeprom->nvmem = nvmem_register(&lpc18xx_nvmem_config); + if (IS_ERR(eeprom->nvmem)) { + ret = PTR_ERR(eeprom->nvmem); + goto err_clk; + } + + platform_set_drvdata(pdev, eeprom); + + return 0; + +err_clk: + clk_disable_unprepare(eeprom->clk); + + return ret; +} + +static int lpc18xx_eeprom_remove(struct platform_device *pdev) +{ + struct lpc18xx_eeprom_dev *eeprom = platform_get_drvdata(pdev); + int ret; + + ret = nvmem_unregister(eeprom->nvmem); + if (ret < 0) + return ret; + + clk_disable_unprepare(eeprom->clk); + + return 0; +} + +static const struct of_device_id lpc18xx_eeprom_of_match[] = { + { .compatible = "nxp,lpc1857-eeprom" }, + { }, +}; +MODULE_DEVICE_TABLE(of, lpc18xx_eeprom_of_match); + +static struct platform_driver lpc18xx_eeprom_driver = { + .probe = lpc18xx_eeprom_probe, + .remove = lpc18xx_eeprom_remove, + .driver = { + .name = "lpc18xx-eeprom", + .of_match_table = lpc18xx_eeprom_of_match, + }, +}; + +module_platform_driver(lpc18xx_eeprom_driver); + +MODULE_AUTHOR("Ariel D'Alessandro <ariel@vanguardiasur.com.ar>"); +MODULE_DESCRIPTION("NXP LPC18xx EEPROM memory Driver"); +MODULE_LICENSE("GPL v2"); -- 1.9.1 ^ permalink raw reply related [flat|nested] 21+ messages in thread
* [PATCH 2/4] nvmem: NXP LPC18xx EEPROM memory NVMEM driver @ 2015-12-07 10:57 ` Srinivas Kandagatla 0 siblings, 0 replies; 21+ messages in thread From: Srinivas Kandagatla @ 2015-12-07 10:57 UTC (permalink / raw) To: linux-arm-kernel From: Ariel D'Alessandro <ariel@vanguardiasur.com.ar> This commit adds support for NXP LPC18xx EEPROM memory found in NXP LPC185x/3x and LPC435x/3x/2x/1x devices. EEPROM size is 16384 bytes and it can be entirely read and written/erased with 1 word (4 bytes) granularity. The last page (128 bytes) contains the EEPROM initialization data and is not writable. Erase/program time is less than 3ms. The EEPROM device requires a ~1500 kHz clock (min 800 kHz, max 1600 kHz) that is generated dividing the system bus clock by the division factor, contained in the divider register (minus 1 encoded). EEPROM will be kept in Power Down mode except during read/write calls. Signed-off-by: Ariel D'Alessandro <ariel@vanguardiasur.com.ar> Acked-by: Stefan Wahren <stefan.wahren@i2se.com> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org> --- drivers/nvmem/Kconfig | 9 ++ drivers/nvmem/Makefile | 2 + drivers/nvmem/lpc18xx_eeprom.c | 330 +++++++++++++++++++++++++++++++++++++++++ 3 files changed, 341 insertions(+) create mode 100644 drivers/nvmem/lpc18xx_eeprom.c diff --git a/drivers/nvmem/Kconfig b/drivers/nvmem/Kconfig index bc4ea58..6ff1b50 100644 --- a/drivers/nvmem/Kconfig +++ b/drivers/nvmem/Kconfig @@ -25,6 +25,15 @@ config NVMEM_IMX_OCOTP This driver can also be built as a module. If so, the module will be called nvmem-imx-ocotp. +config NVMEM_LPC18XX_EEPROM + tristate "NXP LPC18XX EEPROM Memory Support" + depends on ARCH_LPC18XX || COMPILE_TEST + help + Say Y here to include support for NXP LPC18xx EEPROM memory found in + NXP LPC185x/3x and LPC435x/3x/2x/1x devices. + To compile this driver as a module, choose M here: the module + will be called nvmem_lpc18xx_eeprom. + config NVMEM_MXS_OCOTP tristate "Freescale MXS On-Chip OTP Memory Support" depends on ARCH_MXS || COMPILE_TEST diff --git a/drivers/nvmem/Makefile b/drivers/nvmem/Makefile index 95dde3f..c14a556 100644 --- a/drivers/nvmem/Makefile +++ b/drivers/nvmem/Makefile @@ -8,6 +8,8 @@ nvmem_core-y := core.o # Devices obj-$(CONFIG_NVMEM_IMX_OCOTP) += nvmem-imx-ocotp.o nvmem-imx-ocotp-y := imx-ocotp.o +obj-$(CONFIG_NVMEM_LPC18XX_EEPROM) += nvmem_lpc18xx_eeprom.o +nvmem_lpc18xx_eeprom-y := lpc18xx_eeprom.o obj-$(CONFIG_NVMEM_MXS_OCOTP) += nvmem-mxs-ocotp.o nvmem-mxs-ocotp-y := mxs-ocotp.o obj-$(CONFIG_QCOM_QFPROM) += nvmem_qfprom.o diff --git a/drivers/nvmem/lpc18xx_eeprom.c b/drivers/nvmem/lpc18xx_eeprom.c new file mode 100644 index 0000000..878fce7 --- /dev/null +++ b/drivers/nvmem/lpc18xx_eeprom.c @@ -0,0 +1,330 @@ +/* + * NXP LPC18xx/LPC43xx EEPROM memory NVMEM driver + * + * Copyright (c) 2015 Ariel D'Alessandro <ariel@vanguardiasur.com> + * + * This program is free software; you can redistribute it and/or modify it + * under the terms of the GNU General Public License version 2 as published by + * the Free Software Foundation. + */ + +#include <linux/clk.h> +#include <linux/device.h> +#include <linux/delay.h> +#include <linux/err.h> +#include <linux/io.h> +#include <linux/module.h> +#include <linux/nvmem-provider.h> +#include <linux/platform_device.h> +#include <linux/regmap.h> +#include <linux/reset.h> + +/* Registers */ +#define LPC18XX_EEPROM_AUTOPROG 0x00c +#define LPC18XX_EEPROM_AUTOPROG_WORD 0x1 + +#define LPC18XX_EEPROM_CLKDIV 0x014 + +#define LPC18XX_EEPROM_PWRDWN 0x018 +#define LPC18XX_EEPROM_PWRDWN_NO 0x0 +#define LPC18XX_EEPROM_PWRDWN_YES 0x1 + +#define LPC18XX_EEPROM_INTSTAT 0xfe0 +#define LPC18XX_EEPROM_INTSTAT_END_OF_PROG BIT(2) + +#define LPC18XX_EEPROM_INTSTATCLR 0xfe8 +#define LPC18XX_EEPROM_INTSTATCLR_PROG_CLR_ST BIT(2) + +/* Fixed page size (bytes) */ +#define LPC18XX_EEPROM_PAGE_SIZE 0x80 + +/* EEPROM device requires a ~1500 kHz clock (min 800 kHz, max 1600 kHz) */ +#define LPC18XX_EEPROM_CLOCK_HZ 1500000 + +/* EEPROM requires 3 ms of erase/program time between each writing */ +#define LPC18XX_EEPROM_PROGRAM_TIME 3 + +struct lpc18xx_eeprom_dev { + struct clk *clk; + void __iomem *reg_base; + void __iomem *mem_base; + struct nvmem_device *nvmem; + unsigned reg_bytes; + unsigned val_bytes; +}; + +static struct regmap_config lpc18xx_regmap_config = { + .reg_bits = 32, + .reg_stride = 4, + .val_bits = 32, +}; + +static inline void lpc18xx_eeprom_writel(struct lpc18xx_eeprom_dev *eeprom, + u32 reg, u32 val) +{ + writel(val, eeprom->reg_base + reg); +} + +static inline u32 lpc18xx_eeprom_readl(struct lpc18xx_eeprom_dev *eeprom, + u32 reg) +{ + return readl(eeprom->reg_base + reg); +} + +static int lpc18xx_eeprom_busywait_until_prog(struct lpc18xx_eeprom_dev *eeprom) +{ + unsigned long end; + u32 val; + + /* Wait until EEPROM program operation has finished */ + end = jiffies + msecs_to_jiffies(LPC18XX_EEPROM_PROGRAM_TIME * 10); + + while (time_is_after_jiffies(end)) { + val = lpc18xx_eeprom_readl(eeprom, LPC18XX_EEPROM_INTSTAT); + + if (val & LPC18XX_EEPROM_INTSTAT_END_OF_PROG) { + lpc18xx_eeprom_writel(eeprom, LPC18XX_EEPROM_INTSTATCLR, + LPC18XX_EEPROM_INTSTATCLR_PROG_CLR_ST); + return 0; + } + + usleep_range(LPC18XX_EEPROM_PROGRAM_TIME * USEC_PER_MSEC, + (LPC18XX_EEPROM_PROGRAM_TIME + 1) * USEC_PER_MSEC); + } + + return -ETIMEDOUT; +} + +static int lpc18xx_eeprom_gather_write(void *context, const void *reg, + size_t reg_size, const void *val, + size_t val_size) +{ + struct lpc18xx_eeprom_dev *eeprom = context; + unsigned int offset = *(u32 *)reg; + int ret; + + if (offset % lpc18xx_regmap_config.reg_stride) + return -EINVAL; + + lpc18xx_eeprom_writel(eeprom, LPC18XX_EEPROM_PWRDWN, + LPC18XX_EEPROM_PWRDWN_NO); + + /* Wait 100 us while the EEPROM wakes up */ + usleep_range(100, 200); + + while (val_size) { + writel(*(u32 *)val, eeprom->mem_base + offset); + ret = lpc18xx_eeprom_busywait_until_prog(eeprom); + if (ret < 0) + return ret; + + val_size -= eeprom->val_bytes; + val += eeprom->val_bytes; + offset += eeprom->val_bytes; + } + + lpc18xx_eeprom_writel(eeprom, LPC18XX_EEPROM_PWRDWN, + LPC18XX_EEPROM_PWRDWN_YES); + + return 0; +} + +static int lpc18xx_eeprom_write(void *context, const void *data, size_t count) +{ + struct lpc18xx_eeprom_dev *eeprom = context; + unsigned int offset = eeprom->reg_bytes; + + if (count <= offset) + return -EINVAL; + + return lpc18xx_eeprom_gather_write(context, data, eeprom->reg_bytes, + data + offset, count - offset); +} + +static int lpc18xx_eeprom_read(void *context, const void *reg, size_t reg_size, + void *val, size_t val_size) +{ + struct lpc18xx_eeprom_dev *eeprom = context; + unsigned int offset = *(u32 *)reg; + + lpc18xx_eeprom_writel(eeprom, LPC18XX_EEPROM_PWRDWN, + LPC18XX_EEPROM_PWRDWN_NO); + + /* Wait 100 us while the EEPROM wakes up */ + usleep_range(100, 200); + + while (val_size) { + *(u32 *)val = readl(eeprom->mem_base + offset); + val_size -= eeprom->val_bytes; + val += eeprom->val_bytes; + offset += eeprom->val_bytes; + } + + lpc18xx_eeprom_writel(eeprom, LPC18XX_EEPROM_PWRDWN, + LPC18XX_EEPROM_PWRDWN_YES); + + return 0; +} + +static struct regmap_bus lpc18xx_eeprom_bus = { + .write = lpc18xx_eeprom_write, + .gather_write = lpc18xx_eeprom_gather_write, + .read = lpc18xx_eeprom_read, + .reg_format_endian_default = REGMAP_ENDIAN_NATIVE, + .val_format_endian_default = REGMAP_ENDIAN_NATIVE, +}; + +static bool lpc18xx_eeprom_writeable_reg(struct device *dev, unsigned int reg) +{ + /* + * The last page contains the EEPROM initialization data and is not + * writable. + */ + return reg <= lpc18xx_regmap_config.max_register - + LPC18XX_EEPROM_PAGE_SIZE; +} + +static bool lpc18xx_eeprom_readable_reg(struct device *dev, unsigned int reg) +{ + return reg <= lpc18xx_regmap_config.max_register; +} + +static struct nvmem_config lpc18xx_nvmem_config = { + .name = "lpc18xx-eeprom", + .owner = THIS_MODULE, +}; + +static int lpc18xx_eeprom_probe(struct platform_device *pdev) +{ + struct lpc18xx_eeprom_dev *eeprom; + struct device *dev = &pdev->dev; + struct reset_control *rst; + unsigned long clk_rate; + struct regmap *regmap; + struct resource *res; + int ret; + + eeprom = devm_kzalloc(dev, sizeof(*eeprom), GFP_KERNEL); + if (!eeprom) + return -ENOMEM; + + res = platform_get_resource_byname(pdev, IORESOURCE_MEM, "reg"); + eeprom->reg_base = devm_ioremap_resource(dev, res); + if (IS_ERR(eeprom->reg_base)) + return PTR_ERR(eeprom->reg_base); + + res = platform_get_resource_byname(pdev, IORESOURCE_MEM, "mem"); + eeprom->mem_base = devm_ioremap_resource(dev, res); + if (IS_ERR(eeprom->mem_base)) + return PTR_ERR(eeprom->mem_base); + + eeprom->clk = devm_clk_get(&pdev->dev, "eeprom"); + if (IS_ERR(eeprom->clk)) { + dev_err(&pdev->dev, "failed to get eeprom clock\n"); + return PTR_ERR(eeprom->clk); + } + + ret = clk_prepare_enable(eeprom->clk); + if (ret < 0) { + dev_err(dev, "failed to prepare/enable eeprom clk: %d\n", ret); + return ret; + } + + rst = devm_reset_control_get(dev, NULL); + if (IS_ERR(rst)) { + dev_err(dev, "failed to get reset: %ld\n", PTR_ERR(rst)); + ret = PTR_ERR(rst); + goto err_clk; + } + + ret = reset_control_assert(rst); + if (ret < 0) { + dev_err(dev, "failed to assert reset: %d\n", ret); + goto err_clk; + } + + eeprom->val_bytes = lpc18xx_regmap_config.val_bits / BITS_PER_BYTE; + eeprom->reg_bytes = lpc18xx_regmap_config.reg_bits / BITS_PER_BYTE; + + /* + * Clock rate is generated by dividing the system bus clock by the + * division factor, contained in the divider register (minus 1 encoded). + */ + clk_rate = clk_get_rate(eeprom->clk); + clk_rate = DIV_ROUND_UP(clk_rate, LPC18XX_EEPROM_CLOCK_HZ) - 1; + lpc18xx_eeprom_writel(eeprom, LPC18XX_EEPROM_CLKDIV, clk_rate); + + /* + * Writing a single word to the page will start the erase/program cycle + * automatically + */ + lpc18xx_eeprom_writel(eeprom, LPC18XX_EEPROM_AUTOPROG, + LPC18XX_EEPROM_AUTOPROG_WORD); + + lpc18xx_eeprom_writel(eeprom, LPC18XX_EEPROM_PWRDWN, + LPC18XX_EEPROM_PWRDWN_YES); + + lpc18xx_regmap_config.max_register = resource_size(res) - 1; + lpc18xx_regmap_config.writeable_reg = lpc18xx_eeprom_writeable_reg; + lpc18xx_regmap_config.readable_reg = lpc18xx_eeprom_readable_reg; + + regmap = devm_regmap_init(dev, &lpc18xx_eeprom_bus, eeprom, + &lpc18xx_regmap_config); + if (IS_ERR(regmap)) { + dev_err(dev, "regmap init failed: %ld\n", PTR_ERR(regmap)); + ret = PTR_ERR(regmap); + goto err_clk; + } + + lpc18xx_nvmem_config.dev = dev; + + eeprom->nvmem = nvmem_register(&lpc18xx_nvmem_config); + if (IS_ERR(eeprom->nvmem)) { + ret = PTR_ERR(eeprom->nvmem); + goto err_clk; + } + + platform_set_drvdata(pdev, eeprom); + + return 0; + +err_clk: + clk_disable_unprepare(eeprom->clk); + + return ret; +} + +static int lpc18xx_eeprom_remove(struct platform_device *pdev) +{ + struct lpc18xx_eeprom_dev *eeprom = platform_get_drvdata(pdev); + int ret; + + ret = nvmem_unregister(eeprom->nvmem); + if (ret < 0) + return ret; + + clk_disable_unprepare(eeprom->clk); + + return 0; +} + +static const struct of_device_id lpc18xx_eeprom_of_match[] = { + { .compatible = "nxp,lpc1857-eeprom" }, + { }, +}; +MODULE_DEVICE_TABLE(of, lpc18xx_eeprom_of_match); + +static struct platform_driver lpc18xx_eeprom_driver = { + .probe = lpc18xx_eeprom_probe, + .remove = lpc18xx_eeprom_remove, + .driver = { + .name = "lpc18xx-eeprom", + .of_match_table = lpc18xx_eeprom_of_match, + }, +}; + +module_platform_driver(lpc18xx_eeprom_driver); + +MODULE_AUTHOR("Ariel D'Alessandro <ariel@vanguardiasur.com.ar>"); +MODULE_DESCRIPTION("NXP LPC18xx EEPROM memory Driver"); +MODULE_LICENSE("GPL v2"); -- 1.9.1 ^ permalink raw reply related [flat|nested] 21+ messages in thread
* [PATCH 3/4] dt-bindings: add document of mediatek efuse driver 2015-12-07 10:56 ` Srinivas Kandagatla @ 2015-12-07 10:57 ` Srinivas Kandagatla -1 siblings, 0 replies; 21+ messages in thread From: Srinivas Kandagatla @ 2015-12-07 10:57 UTC (permalink / raw) To: gregkh Cc: linux-kernel, maxime.ripard, linux-arm-kernel, andrew-ct.chen, ariel, Srinivas Kandagatla From: Andrew-CT Chen <andrew-ct.chen@mediatek.com> Add Mediatek MT8173 EFUSE Devicetree binding file Signed-off-by: Andrew-CT Chen <andrew-ct.chen@mediatek.com> Reviewed-by: Sascha Hauer <s.hauer@pengutronix.de> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org> --- .../devicetree/bindings/nvmem/mtk-efuse.txt | 36 ++++++++++++++++++++++ 1 file changed, 36 insertions(+) create mode 100644 Documentation/devicetree/bindings/nvmem/mtk-efuse.txt diff --git a/Documentation/devicetree/bindings/nvmem/mtk-efuse.txt b/Documentation/devicetree/bindings/nvmem/mtk-efuse.txt new file mode 100644 index 0000000..74cf529 --- /dev/null +++ b/Documentation/devicetree/bindings/nvmem/mtk-efuse.txt @@ -0,0 +1,36 @@ += Mediatek MTK-EFUSE device tree bindings = + +This binding is intended to represent MTK-EFUSE which is found in most Mediatek SOCs. + +Required properties: +- compatible: should be "mediatek,mt8173-efuse" or "mediatek,efuse" +- reg: Should contain registers location and length + += Data cells = +Are child nodes of MTK-EFUSE, bindings of which as described in +bindings/nvmem/nvmem.txt + +Example: + + efuse: efuse@10206000 { + compatible = "mediatek,mt8173-efuse"; + reg = <0 0x10206000 0 0x1000>; + #address-cells = <1>; + #size-cells = <1>; + + /* Data cells */ + thermal_calibration: calib@528 { + reg = <0x528 0xc>; + }; + }; + += Data consumers = +Are device nodes which consume nvmem data cells. + +For example: + + thermal { + ... + nvmem-cells = <&thermal_calibration>; + nvmem-cell-names = "calibration"; + }; -- 1.9.1 ^ permalink raw reply related [flat|nested] 21+ messages in thread
* [PATCH 3/4] dt-bindings: add document of mediatek efuse driver @ 2015-12-07 10:57 ` Srinivas Kandagatla 0 siblings, 0 replies; 21+ messages in thread From: Srinivas Kandagatla @ 2015-12-07 10:57 UTC (permalink / raw) To: linux-arm-kernel From: Andrew-CT Chen <andrew-ct.chen@mediatek.com> Add Mediatek MT8173 EFUSE Devicetree binding file Signed-off-by: Andrew-CT Chen <andrew-ct.chen@mediatek.com> Reviewed-by: Sascha Hauer <s.hauer@pengutronix.de> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org> --- .../devicetree/bindings/nvmem/mtk-efuse.txt | 36 ++++++++++++++++++++++ 1 file changed, 36 insertions(+) create mode 100644 Documentation/devicetree/bindings/nvmem/mtk-efuse.txt diff --git a/Documentation/devicetree/bindings/nvmem/mtk-efuse.txt b/Documentation/devicetree/bindings/nvmem/mtk-efuse.txt new file mode 100644 index 0000000..74cf529 --- /dev/null +++ b/Documentation/devicetree/bindings/nvmem/mtk-efuse.txt @@ -0,0 +1,36 @@ += Mediatek MTK-EFUSE device tree bindings = + +This binding is intended to represent MTK-EFUSE which is found in most Mediatek SOCs. + +Required properties: +- compatible: should be "mediatek,mt8173-efuse" or "mediatek,efuse" +- reg: Should contain registers location and length + += Data cells = +Are child nodes of MTK-EFUSE, bindings of which as described in +bindings/nvmem/nvmem.txt + +Example: + + efuse: efuse at 10206000 { + compatible = "mediatek,mt8173-efuse"; + reg = <0 0x10206000 0 0x1000>; + #address-cells = <1>; + #size-cells = <1>; + + /* Data cells */ + thermal_calibration: calib at 528 { + reg = <0x528 0xc>; + }; + }; + += Data consumers = +Are device nodes which consume nvmem data cells. + +For example: + + thermal { + ... + nvmem-cells = <&thermal_calibration>; + nvmem-cell-names = "calibration"; + }; -- 1.9.1 ^ permalink raw reply related [flat|nested] 21+ messages in thread
* [PATCH 4/4] nvmem: mediatek: Add Mediatek EFUSE driver 2015-12-07 10:56 ` Srinivas Kandagatla @ 2015-12-07 10:58 ` Srinivas Kandagatla -1 siblings, 0 replies; 21+ messages in thread From: Srinivas Kandagatla @ 2015-12-07 10:58 UTC (permalink / raw) To: gregkh Cc: linux-kernel, maxime.ripard, linux-arm-kernel, andrew-ct.chen, ariel, Srinivas Kandagatla From: Andrew-CT Chen <andrew-ct.chen@mediatek.com> Add Mediatek EFUSE driver to access hardware data like thermal sensor calibration or HDMI impedance. Signed-off-by: Andrew-CT Chen <andrew-ct.chen@mediatek.com> Reviewed-by: Sascha Hauer <s.hauer@pengutronix.de> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org> --- drivers/nvmem/Kconfig | 11 ++++++ drivers/nvmem/Makefile | 2 ++ drivers/nvmem/mtk-efuse.c | 89 +++++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 102 insertions(+) create mode 100644 drivers/nvmem/mtk-efuse.c diff --git a/drivers/nvmem/Kconfig b/drivers/nvmem/Kconfig index 6ff1b50..5bd18cc 100644 --- a/drivers/nvmem/Kconfig +++ b/drivers/nvmem/Kconfig @@ -45,6 +45,17 @@ config NVMEM_MXS_OCOTP This driver can also be built as a module. If so, the module will be called nvmem-mxs-ocotp. +config MTK_EFUSE + tristate "Mediatek SoCs EFUSE support" + depends on ARCH_MEDIATEK || COMPILE_TEST + select REGMAP_MMIO + help + This is a driver to access hardware related data like sensor + calibration, HDMI impedance etc. + + This driver can also be built as a module. If so, the module + will be called efuse-mtk. + config QCOM_QFPROM tristate "QCOM QFPROM Support" depends on ARCH_QCOM || COMPILE_TEST diff --git a/drivers/nvmem/Makefile b/drivers/nvmem/Makefile index c14a556..45ab1ae 100644 --- a/drivers/nvmem/Makefile +++ b/drivers/nvmem/Makefile @@ -12,6 +12,8 @@ obj-$(CONFIG_NVMEM_LPC18XX_EEPROM) += nvmem_lpc18xx_eeprom.o nvmem_lpc18xx_eeprom-y := lpc18xx_eeprom.o obj-$(CONFIG_NVMEM_MXS_OCOTP) += nvmem-mxs-ocotp.o nvmem-mxs-ocotp-y := mxs-ocotp.o +obj-$(CONFIG_MTK_EFUSE) += nvmem_mtk-efuse.o +nvmem_mtk-efuse-y := mtk-efuse.o obj-$(CONFIG_QCOM_QFPROM) += nvmem_qfprom.o nvmem_qfprom-y := qfprom.o obj-$(CONFIG_ROCKCHIP_EFUSE) += nvmem_rockchip_efuse.o diff --git a/drivers/nvmem/mtk-efuse.c b/drivers/nvmem/mtk-efuse.c new file mode 100644 index 0000000..7b35f5b --- /dev/null +++ b/drivers/nvmem/mtk-efuse.c @@ -0,0 +1,89 @@ +/* + * Copyright (c) 2015 MediaTek Inc. + * Author: Andrew-CT Chen <andrew-ct.chen@mediatek.com> + * + * This program is free software; you can redistribute it and/or modify + * it under the terms of the GNU General Public License version 2 as + * published by the Free Software Foundation. + * + * This program is distributed in the hope that it will be useful, + * but WITHOUT ANY WARRANTY; without even the implied warranty of + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + * GNU General Public License for more details. + */ + +#include <linux/device.h> +#include <linux/module.h> +#include <linux/nvmem-provider.h> +#include <linux/platform_device.h> +#include <linux/regmap.h> + +static struct regmap_config mtk_regmap_config = { + .reg_bits = 32, + .val_bits = 32, + .reg_stride = 4, +}; + +static int mtk_efuse_probe(struct platform_device *pdev) +{ + struct device *dev = &pdev->dev; + struct resource *res; + struct nvmem_device *nvmem; + struct nvmem_config *econfig; + struct regmap *regmap; + void __iomem *base; + + res = platform_get_resource(pdev, IORESOURCE_MEM, 0); + base = devm_ioremap_resource(dev, res); + if (IS_ERR(base)) + return PTR_ERR(base); + + econfig = devm_kzalloc(dev, sizeof(*econfig), GFP_KERNEL); + if (!econfig) + return -ENOMEM; + + mtk_regmap_config.max_register = resource_size(res) - 1; + + regmap = devm_regmap_init_mmio(dev, base, &mtk_regmap_config); + if (IS_ERR(regmap)) { + dev_err(dev, "regmap init failed\n"); + return PTR_ERR(regmap); + } + + econfig->dev = dev; + econfig->owner = THIS_MODULE; + nvmem = nvmem_register(econfig); + if (IS_ERR(nvmem)) + return PTR_ERR(nvmem); + + platform_set_drvdata(pdev, nvmem); + + return 0; +} + +static int mtk_efuse_remove(struct platform_device *pdev) +{ + struct nvmem_device *nvmem = platform_get_drvdata(pdev); + + return nvmem_unregister(nvmem); +} + +static const struct of_device_id mtk_efuse_of_match[] = { + { .compatible = "mediatek,mt8173-efuse",}, + { .compatible = "mediatek,efuse",}, + {/* sentinel */}, +}; +MODULE_DEVICE_TABLE(of, mtk_efuse_of_match); + +static struct platform_driver mtk_efuse_driver = { + .probe = mtk_efuse_probe, + .remove = mtk_efuse_remove, + .driver = { + .name = "mediatek,efuse", + .of_match_table = mtk_efuse_of_match, + }, +}; +module_platform_driver(mtk_efuse_driver); +MODULE_AUTHOR("Andrew-CT Chen <andrew-ct.chen@mediatek.com>"); +MODULE_DESCRIPTION("Mediatek EFUSE driver"); +MODULE_LICENSE("GPL v2"); -- 1.9.1 ^ permalink raw reply related [flat|nested] 21+ messages in thread
* [PATCH 4/4] nvmem: mediatek: Add Mediatek EFUSE driver @ 2015-12-07 10:58 ` Srinivas Kandagatla 0 siblings, 0 replies; 21+ messages in thread From: Srinivas Kandagatla @ 2015-12-07 10:58 UTC (permalink / raw) To: linux-arm-kernel From: Andrew-CT Chen <andrew-ct.chen@mediatek.com> Add Mediatek EFUSE driver to access hardware data like thermal sensor calibration or HDMI impedance. Signed-off-by: Andrew-CT Chen <andrew-ct.chen@mediatek.com> Reviewed-by: Sascha Hauer <s.hauer@pengutronix.de> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org> --- drivers/nvmem/Kconfig | 11 ++++++ drivers/nvmem/Makefile | 2 ++ drivers/nvmem/mtk-efuse.c | 89 +++++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 102 insertions(+) create mode 100644 drivers/nvmem/mtk-efuse.c diff --git a/drivers/nvmem/Kconfig b/drivers/nvmem/Kconfig index 6ff1b50..5bd18cc 100644 --- a/drivers/nvmem/Kconfig +++ b/drivers/nvmem/Kconfig @@ -45,6 +45,17 @@ config NVMEM_MXS_OCOTP This driver can also be built as a module. If so, the module will be called nvmem-mxs-ocotp. +config MTK_EFUSE + tristate "Mediatek SoCs EFUSE support" + depends on ARCH_MEDIATEK || COMPILE_TEST + select REGMAP_MMIO + help + This is a driver to access hardware related data like sensor + calibration, HDMI impedance etc. + + This driver can also be built as a module. If so, the module + will be called efuse-mtk. + config QCOM_QFPROM tristate "QCOM QFPROM Support" depends on ARCH_QCOM || COMPILE_TEST diff --git a/drivers/nvmem/Makefile b/drivers/nvmem/Makefile index c14a556..45ab1ae 100644 --- a/drivers/nvmem/Makefile +++ b/drivers/nvmem/Makefile @@ -12,6 +12,8 @@ obj-$(CONFIG_NVMEM_LPC18XX_EEPROM) += nvmem_lpc18xx_eeprom.o nvmem_lpc18xx_eeprom-y := lpc18xx_eeprom.o obj-$(CONFIG_NVMEM_MXS_OCOTP) += nvmem-mxs-ocotp.o nvmem-mxs-ocotp-y := mxs-ocotp.o +obj-$(CONFIG_MTK_EFUSE) += nvmem_mtk-efuse.o +nvmem_mtk-efuse-y := mtk-efuse.o obj-$(CONFIG_QCOM_QFPROM) += nvmem_qfprom.o nvmem_qfprom-y := qfprom.o obj-$(CONFIG_ROCKCHIP_EFUSE) += nvmem_rockchip_efuse.o diff --git a/drivers/nvmem/mtk-efuse.c b/drivers/nvmem/mtk-efuse.c new file mode 100644 index 0000000..7b35f5b --- /dev/null +++ b/drivers/nvmem/mtk-efuse.c @@ -0,0 +1,89 @@ +/* + * Copyright (c) 2015 MediaTek Inc. + * Author: Andrew-CT Chen <andrew-ct.chen@mediatek.com> + * + * This program is free software; you can redistribute it and/or modify + * it under the terms of the GNU General Public License version 2 as + * published by the Free Software Foundation. + * + * This program is distributed in the hope that it will be useful, + * but WITHOUT ANY WARRANTY; without even the implied warranty of + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + * GNU General Public License for more details. + */ + +#include <linux/device.h> +#include <linux/module.h> +#include <linux/nvmem-provider.h> +#include <linux/platform_device.h> +#include <linux/regmap.h> + +static struct regmap_config mtk_regmap_config = { + .reg_bits = 32, + .val_bits = 32, + .reg_stride = 4, +}; + +static int mtk_efuse_probe(struct platform_device *pdev) +{ + struct device *dev = &pdev->dev; + struct resource *res; + struct nvmem_device *nvmem; + struct nvmem_config *econfig; + struct regmap *regmap; + void __iomem *base; + + res = platform_get_resource(pdev, IORESOURCE_MEM, 0); + base = devm_ioremap_resource(dev, res); + if (IS_ERR(base)) + return PTR_ERR(base); + + econfig = devm_kzalloc(dev, sizeof(*econfig), GFP_KERNEL); + if (!econfig) + return -ENOMEM; + + mtk_regmap_config.max_register = resource_size(res) - 1; + + regmap = devm_regmap_init_mmio(dev, base, &mtk_regmap_config); + if (IS_ERR(regmap)) { + dev_err(dev, "regmap init failed\n"); + return PTR_ERR(regmap); + } + + econfig->dev = dev; + econfig->owner = THIS_MODULE; + nvmem = nvmem_register(econfig); + if (IS_ERR(nvmem)) + return PTR_ERR(nvmem); + + platform_set_drvdata(pdev, nvmem); + + return 0; +} + +static int mtk_efuse_remove(struct platform_device *pdev) +{ + struct nvmem_device *nvmem = platform_get_drvdata(pdev); + + return nvmem_unregister(nvmem); +} + +static const struct of_device_id mtk_efuse_of_match[] = { + { .compatible = "mediatek,mt8173-efuse",}, + { .compatible = "mediatek,efuse",}, + {/* sentinel */}, +}; +MODULE_DEVICE_TABLE(of, mtk_efuse_of_match); + +static struct platform_driver mtk_efuse_driver = { + .probe = mtk_efuse_probe, + .remove = mtk_efuse_remove, + .driver = { + .name = "mediatek,efuse", + .of_match_table = mtk_efuse_of_match, + }, +}; +module_platform_driver(mtk_efuse_driver); +MODULE_AUTHOR("Andrew-CT Chen <andrew-ct.chen@mediatek.com>"); +MODULE_DESCRIPTION("Mediatek EFUSE driver"); +MODULE_LICENSE("GPL v2"); -- 1.9.1 ^ permalink raw reply related [flat|nested] 21+ messages in thread
* Re: [PATCH 0/4] nvmem: new drivers for v4.5 2015-12-07 10:56 ` Srinivas Kandagatla @ 2016-01-11 13:21 ` Srinivas Kandagatla -1 siblings, 0 replies; 21+ messages in thread From: Srinivas Kandagatla @ 2016-01-11 13:21 UTC (permalink / raw) To: gregkh Cc: linux-kernel, maxime.ripard, linux-arm-kernel, andrew-ct.chen, ariel On 07/12/15 10:56, Srinivas Kandagatla wrote: > Hi Greg, > > Here are 2 new nvmem drivers which are in the mailing list for long time > and are good to go for some testing and find its way to v4.5-rc*. > > Could you please take these patches via char-misc tree. Hi Greg, I have not seen these patches or https://lkml.org/lkml/2015/12/14/169 appear in your char-misc tree/linux-next. Just wanted to know whats your plan on these patches? All these drivers are reviewed/tested and other parts of these driver like Device tree are already making way to v4.5-rc1. Please let me know if you want me to resend them, in case you missed them. thanks, srini > > Thanks, > srini > > Andrew-CT Chen (2): > dt-bindings: add document of mediatek efuse driver > nvmem: mediatek: Add Mediatek EFUSE driver > > Ariel D'Alessandro (2): > DT: nvmem: Add NXP LPC18xx EEPROM memory binding documentation > nvmem: NXP LPC18xx EEPROM memory NVMEM driver > > .../devicetree/bindings/nvmem/lpc1857-eeprom.txt | 28 ++ > .../devicetree/bindings/nvmem/mtk-efuse.txt | 36 +++ > drivers/nvmem/Kconfig | 20 ++ > drivers/nvmem/Makefile | 4 + > drivers/nvmem/lpc18xx_eeprom.c | 330 +++++++++++++++++++++ > drivers/nvmem/mtk-efuse.c | 89 ++++++ > 6 files changed, 507 insertions(+) > create mode 100644 Documentation/devicetree/bindings/nvmem/lpc1857-eeprom.txt > create mode 100644 Documentation/devicetree/bindings/nvmem/mtk-efuse.txt > create mode 100644 drivers/nvmem/lpc18xx_eeprom.c > create mode 100644 drivers/nvmem/mtk-efuse.c > ^ permalink raw reply [flat|nested] 21+ messages in thread
* [PATCH 0/4] nvmem: new drivers for v4.5 @ 2016-01-11 13:21 ` Srinivas Kandagatla 0 siblings, 0 replies; 21+ messages in thread From: Srinivas Kandagatla @ 2016-01-11 13:21 UTC (permalink / raw) To: linux-arm-kernel On 07/12/15 10:56, Srinivas Kandagatla wrote: > Hi Greg, > > Here are 2 new nvmem drivers which are in the mailing list for long time > and are good to go for some testing and find its way to v4.5-rc*. > > Could you please take these patches via char-misc tree. Hi Greg, I have not seen these patches or https://lkml.org/lkml/2015/12/14/169 appear in your char-misc tree/linux-next. Just wanted to know whats your plan on these patches? All these drivers are reviewed/tested and other parts of these driver like Device tree are already making way to v4.5-rc1. Please let me know if you want me to resend them, in case you missed them. thanks, srini > > Thanks, > srini > > Andrew-CT Chen (2): > dt-bindings: add document of mediatek efuse driver > nvmem: mediatek: Add Mediatek EFUSE driver > > Ariel D'Alessandro (2): > DT: nvmem: Add NXP LPC18xx EEPROM memory binding documentation > nvmem: NXP LPC18xx EEPROM memory NVMEM driver > > .../devicetree/bindings/nvmem/lpc1857-eeprom.txt | 28 ++ > .../devicetree/bindings/nvmem/mtk-efuse.txt | 36 +++ > drivers/nvmem/Kconfig | 20 ++ > drivers/nvmem/Makefile | 4 + > drivers/nvmem/lpc18xx_eeprom.c | 330 +++++++++++++++++++++ > drivers/nvmem/mtk-efuse.c | 89 ++++++ > 6 files changed, 507 insertions(+) > create mode 100644 Documentation/devicetree/bindings/nvmem/lpc1857-eeprom.txt > create mode 100644 Documentation/devicetree/bindings/nvmem/mtk-efuse.txt > create mode 100644 drivers/nvmem/lpc18xx_eeprom.c > create mode 100644 drivers/nvmem/mtk-efuse.c > ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [PATCH 0/4] nvmem: new drivers for v4.5 2016-01-11 13:21 ` Srinivas Kandagatla @ 2016-01-11 18:30 ` Greg KH -1 siblings, 0 replies; 21+ messages in thread From: Greg KH @ 2016-01-11 18:30 UTC (permalink / raw) To: Srinivas Kandagatla Cc: linux-kernel, maxime.ripard, linux-arm-kernel, andrew-ct.chen, ariel On Mon, Jan 11, 2016 at 01:21:44PM +0000, Srinivas Kandagatla wrote: > > > On 07/12/15 10:56, Srinivas Kandagatla wrote: > >Hi Greg, > > > >Here are 2 new nvmem drivers which are in the mailing list for long time > >and are good to go for some testing and find its way to v4.5-rc*. > > > >Could you please take these patches via char-misc tree. > Hi Greg, > > I have not seen these patches or https://lkml.org/lkml/2015/12/14/169 appear > in your char-misc tree/linux-next. > > Just wanted to know whats your plan on these patches? To wait until after 4.5-rc1 is out, sorry, my patch backlog got huge during Nov/Dec due to other external issues, I'll be digging out from them after 4.5-rc1 is out. thanks, greg k-h ^ permalink raw reply [flat|nested] 21+ messages in thread
* [PATCH 0/4] nvmem: new drivers for v4.5 @ 2016-01-11 18:30 ` Greg KH 0 siblings, 0 replies; 21+ messages in thread From: Greg KH @ 2016-01-11 18:30 UTC (permalink / raw) To: linux-arm-kernel On Mon, Jan 11, 2016 at 01:21:44PM +0000, Srinivas Kandagatla wrote: > > > On 07/12/15 10:56, Srinivas Kandagatla wrote: > >Hi Greg, > > > >Here are 2 new nvmem drivers which are in the mailing list for long time > >and are good to go for some testing and find its way to v4.5-rc*. > > > >Could you please take these patches via char-misc tree. > Hi Greg, > > I have not seen these patches or https://lkml.org/lkml/2015/12/14/169 appear > in your char-misc tree/linux-next. > > Just wanted to know whats your plan on these patches? To wait until after 4.5-rc1 is out, sorry, my patch backlog got huge during Nov/Dec due to other external issues, I'll be digging out from them after 4.5-rc1 is out. thanks, greg k-h ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [PATCH 0/4] nvmem: new drivers for v4.5 2016-01-11 18:30 ` Greg KH (?) @ 2016-01-19 18:15 ` Daniel Kurtz -1 siblings, 0 replies; 21+ messages in thread From: Daniel Kurtz @ 2016-01-19 18:15 UTC (permalink / raw) To: Greg KH Cc: Srinivas Kandagatla, linux-kernel, Maxime Ripard, linux-arm-kernel, Andrew-CT Chen, ariel, Sascha Hauer, Eduardo Valentin, Javi Merino, linux-pm Hi Greg, On Mon, Jan 11, 2016 at 10:30 AM, Greg KH <gregkh@linuxfoundation.org> wrote: > > On Mon, Jan 11, 2016 at 01:21:44PM +0000, Srinivas Kandagatla wrote: > > > > > > On 07/12/15 10:56, Srinivas Kandagatla wrote: > > >Hi Greg, > > > > > >Here are 2 new nvmem drivers which are in the mailing list for long time > > >and are good to go for some testing and find its way to v4.5-rc*. > > > > > >Could you please take these patches via char-misc tree. > > Hi Greg, > > > > I have not seen these patches or https://lkml.org/lkml/2015/12/14/169 appear > > in your char-misc tree/linux-next. > > > > Just wanted to know whats your plan on these patches? > > To wait until after 4.5-rc1 is out, sorry, my patch backlog got huge > during Nov/Dec due to other external issues, I'll be digging out from > them after 4.5-rc1 is out. Soon after 4.5-rc1 sounds great. FYI, to add some context, the Mediatek nvmem driver is actually blocking several other drivers that we would also like to see land in v4.5: Mediatek thermal, Mediatek cpufreq_thermal, and Mediatek devfreq_thermal. So, the sooner nvmem lands, the earlier we can start staging/pushing through the rest. Thanks, -Dan > > thanks, > > greg k-h ^ permalink raw reply [flat|nested] 21+ messages in thread
* [PATCH 0/4] nvmem: new drivers for v4.5 @ 2016-01-19 18:15 ` Daniel Kurtz 0 siblings, 0 replies; 21+ messages in thread From: Daniel Kurtz @ 2016-01-19 18:15 UTC (permalink / raw) To: linux-arm-kernel Hi Greg, On Mon, Jan 11, 2016 at 10:30 AM, Greg KH <gregkh@linuxfoundation.org> wrote: > > On Mon, Jan 11, 2016 at 01:21:44PM +0000, Srinivas Kandagatla wrote: > > > > > > On 07/12/15 10:56, Srinivas Kandagatla wrote: > > >Hi Greg, > > > > > >Here are 2 new nvmem drivers which are in the mailing list for long time > > >and are good to go for some testing and find its way to v4.5-rc*. > > > > > >Could you please take these patches via char-misc tree. > > Hi Greg, > > > > I have not seen these patches or https://lkml.org/lkml/2015/12/14/169 appear > > in your char-misc tree/linux-next. > > > > Just wanted to know whats your plan on these patches? > > To wait until after 4.5-rc1 is out, sorry, my patch backlog got huge > during Nov/Dec due to other external issues, I'll be digging out from > them after 4.5-rc1 is out. Soon after 4.5-rc1 sounds great. FYI, to add some context, the Mediatek nvmem driver is actually blocking several other drivers that we would also like to see land in v4.5: Mediatek thermal, Mediatek cpufreq_thermal, and Mediatek devfreq_thermal. So, the sooner nvmem lands, the earlier we can start staging/pushing through the rest. Thanks, -Dan > > thanks, > > greg k-h ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [PATCH 0/4] nvmem: new drivers for v4.5 @ 2016-01-19 18:15 ` Daniel Kurtz 0 siblings, 0 replies; 21+ messages in thread From: Daniel Kurtz @ 2016-01-19 18:15 UTC (permalink / raw) To: Greg KH Cc: Srinivas Kandagatla, linux-kernel, Maxime Ripard, linux-arm-kernel, Andrew-CT Chen, ariel, Sascha Hauer, Eduardo Valentin, Javi Merino, linux-pm Hi Greg, On Mon, Jan 11, 2016 at 10:30 AM, Greg KH <gregkh@linuxfoundation.org> wrote: > > On Mon, Jan 11, 2016 at 01:21:44PM +0000, Srinivas Kandagatla wrote: > > > > > > On 07/12/15 10:56, Srinivas Kandagatla wrote: > > >Hi Greg, > > > > > >Here are 2 new nvmem drivers which are in the mailing list for long time > > >and are good to go for some testing and find its way to v4.5-rc*. > > > > > >Could you please take these patches via char-misc tree. > > Hi Greg, > > > > I have not seen these patches or https://lkml.org/lkml/2015/12/14/169 appear > > in your char-misc tree/linux-next. > > > > Just wanted to know whats your plan on these patches? > > To wait until after 4.5-rc1 is out, sorry, my patch backlog got huge > during Nov/Dec due to other external issues, I'll be digging out from > them after 4.5-rc1 is out. Soon after 4.5-rc1 sounds great. FYI, to add some context, the Mediatek nvmem driver is actually blocking several other drivers that we would also like to see land in v4.5: Mediatek thermal, Mediatek cpufreq_thermal, and Mediatek devfreq_thermal. So, the sooner nvmem lands, the earlier we can start staging/pushing through the rest. Thanks, -Dan > > thanks, > > greg k-h ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [PATCH 0/4] nvmem: new drivers for v4.5 2016-01-11 18:30 ` Greg KH @ 2016-02-01 10:33 ` Srinivas Kandagatla -1 siblings, 0 replies; 21+ messages in thread From: Srinivas Kandagatla @ 2016-02-01 10:33 UTC (permalink / raw) To: Greg KH Cc: linux-kernel, maxime.ripard, linux-arm-kernel, andrew-ct.chen, ariel, Matthias Brugger Hi Greg, On 11/01/16 18:30, Greg KH wrote: > On Mon, Jan 11, 2016 at 01:21:44PM +0000, Srinivas Kandagatla wrote: >> >> >> On 07/12/15 10:56, Srinivas Kandagatla wrote: >>> Hi Greg, >>> >>> Here are 2 new nvmem drivers which are in the mailing list for long time >>> and are good to go for some testing and find its way to v4.5-rc*. >>> >>> Could you please take these patches via char-misc tree. >> Hi Greg, >> >> I have not seen these patches or https://lkml.org/lkml/2015/12/14/169 appear >> in your char-misc tree/linux-next. >> >> Just wanted to know whats your plan on these patches? > > To wait until after 4.5-rc1 is out, sorry, my patch backlog got huge > during Nov/Dec due to other external issues, I'll be digging out from > them after 4.5-rc1 is out. Am not sure if this was forgotten, just wanted know if you still have plans to pick this series for any rc on 4.5? thanks, srini > > thanks, > > greg k-h > ^ permalink raw reply [flat|nested] 21+ messages in thread
* [PATCH 0/4] nvmem: new drivers for v4.5 @ 2016-02-01 10:33 ` Srinivas Kandagatla 0 siblings, 0 replies; 21+ messages in thread From: Srinivas Kandagatla @ 2016-02-01 10:33 UTC (permalink / raw) To: linux-arm-kernel Hi Greg, On 11/01/16 18:30, Greg KH wrote: > On Mon, Jan 11, 2016 at 01:21:44PM +0000, Srinivas Kandagatla wrote: >> >> >> On 07/12/15 10:56, Srinivas Kandagatla wrote: >>> Hi Greg, >>> >>> Here are 2 new nvmem drivers which are in the mailing list for long time >>> and are good to go for some testing and find its way to v4.5-rc*. >>> >>> Could you please take these patches via char-misc tree. >> Hi Greg, >> >> I have not seen these patches or https://lkml.org/lkml/2015/12/14/169 appear >> in your char-misc tree/linux-next. >> >> Just wanted to know whats your plan on these patches? > > To wait until after 4.5-rc1 is out, sorry, my patch backlog got huge > during Nov/Dec due to other external issues, I'll be digging out from > them after 4.5-rc1 is out. Am not sure if this was forgotten, just wanted know if you still have plans to pick this series for any rc on 4.5? thanks, srini > > thanks, > > greg k-h > ^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [PATCH 0/4] nvmem: new drivers for v4.5 2016-02-01 10:33 ` Srinivas Kandagatla @ 2016-02-01 21:06 ` Greg KH -1 siblings, 0 replies; 21+ messages in thread From: Greg KH @ 2016-02-01 21:06 UTC (permalink / raw) To: Srinivas Kandagatla Cc: linux-kernel, maxime.ripard, linux-arm-kernel, andrew-ct.chen, ariel, Matthias Brugger On Mon, Feb 01, 2016 at 10:33:12AM +0000, Srinivas Kandagatla wrote: > Hi Greg, > > On 11/01/16 18:30, Greg KH wrote: > >On Mon, Jan 11, 2016 at 01:21:44PM +0000, Srinivas Kandagatla wrote: > >> > >> > >>On 07/12/15 10:56, Srinivas Kandagatla wrote: > >>>Hi Greg, > >>> > >>>Here are 2 new nvmem drivers which are in the mailing list for long time > >>>and are good to go for some testing and find its way to v4.5-rc*. > >>> > >>>Could you please take these patches via char-misc tree. > >>Hi Greg, > >> > >>I have not seen these patches or https://lkml.org/lkml/2015/12/14/169 appear > >>in your char-misc tree/linux-next. > >> > >>Just wanted to know whats your plan on these patches? > > > >To wait until after 4.5-rc1 is out, sorry, my patch backlog got huge > >during Nov/Dec due to other external issues, I'll be digging out from > >them after 4.5-rc1 is out. > > Am not sure if this was forgotten, just wanted know if you still have plans > to pick this series for any rc on 4.5? They are in my queue... ^ permalink raw reply [flat|nested] 21+ messages in thread
* [PATCH 0/4] nvmem: new drivers for v4.5 @ 2016-02-01 21:06 ` Greg KH 0 siblings, 0 replies; 21+ messages in thread From: Greg KH @ 2016-02-01 21:06 UTC (permalink / raw) To: linux-arm-kernel On Mon, Feb 01, 2016 at 10:33:12AM +0000, Srinivas Kandagatla wrote: > Hi Greg, > > On 11/01/16 18:30, Greg KH wrote: > >On Mon, Jan 11, 2016 at 01:21:44PM +0000, Srinivas Kandagatla wrote: > >> > >> > >>On 07/12/15 10:56, Srinivas Kandagatla wrote: > >>>Hi Greg, > >>> > >>>Here are 2 new nvmem drivers which are in the mailing list for long time > >>>and are good to go for some testing and find its way to v4.5-rc*. > >>> > >>>Could you please take these patches via char-misc tree. > >>Hi Greg, > >> > >>I have not seen these patches or https://lkml.org/lkml/2015/12/14/169 appear > >>in your char-misc tree/linux-next. > >> > >>Just wanted to know whats your plan on these patches? > > > >To wait until after 4.5-rc1 is out, sorry, my patch backlog got huge > >during Nov/Dec due to other external issues, I'll be digging out from > >them after 4.5-rc1 is out. > > Am not sure if this was forgotten, just wanted know if you still have plans > to pick this series for any rc on 4.5? They are in my queue... ^ permalink raw reply [flat|nested] 21+ messages in thread
end of thread, other threads:[~2016-02-01 21:06 UTC | newest] Thread overview: 21+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2015-12-07 10:56 [PATCH 0/4] nvmem: new drivers for v4.5 Srinivas Kandagatla 2015-12-07 10:56 ` Srinivas Kandagatla 2015-12-07 10:57 ` [PATCH 1/4] DT: nvmem: Add NXP LPC18xx EEPROM memory binding documentation Srinivas Kandagatla 2015-12-07 10:57 ` Srinivas Kandagatla 2015-12-07 10:57 ` [PATCH 2/4] nvmem: NXP LPC18xx EEPROM memory NVMEM driver Srinivas Kandagatla 2015-12-07 10:57 ` Srinivas Kandagatla 2015-12-07 10:57 ` [PATCH 3/4] dt-bindings: add document of mediatek efuse driver Srinivas Kandagatla 2015-12-07 10:57 ` Srinivas Kandagatla 2015-12-07 10:58 ` [PATCH 4/4] nvmem: mediatek: Add Mediatek EFUSE driver Srinivas Kandagatla 2015-12-07 10:58 ` Srinivas Kandagatla 2016-01-11 13:21 ` [PATCH 0/4] nvmem: new drivers for v4.5 Srinivas Kandagatla 2016-01-11 13:21 ` Srinivas Kandagatla 2016-01-11 18:30 ` Greg KH 2016-01-11 18:30 ` Greg KH 2016-01-19 18:15 ` Daniel Kurtz 2016-01-19 18:15 ` Daniel Kurtz 2016-01-19 18:15 ` Daniel Kurtz 2016-02-01 10:33 ` Srinivas Kandagatla 2016-02-01 10:33 ` Srinivas Kandagatla 2016-02-01 21:06 ` Greg KH 2016-02-01 21:06 ` Greg KH
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.