[PATCH v2 0/3] Mediatek EFUSE Support
From: Srinivas Kandagatla <hidden>
Date: 2016-01-21 14:32:33
Also in:
linux-devicetree, linux-mediatek, lkml
On 21/01/16 09:33, Matthias Brugger wrote:
On 14/12/15 11:07, Srinivas Kandagatla wrote:quoted
Hi Andrew, On 14/12/15 04:27, Daniel Kurtz wrote:quoted
Hi Srinivas, On Thu, Nov 19, 2015 at 6:46 PM, Andrew-CT Chen [off-list ref] wrote:quoted
This patch adds EFUSE support driver which is used by other drivers like thermal sensor and HDMI impedance. There are some efuses these fuses store things like calibration data, speed bins.. etc. Drivers like thermal sensor, HDMI impedance would read out this data for configuring the driver. Change in v2: 1. Rebase to 4.4-rc1 2. Modify the driver Makefile for more consistent with other drivers 3. Modify the compatible string to "mediatek,mt8173-efuse" and "mediatek,efuse"Do you still plan to queue this for v4.5?Sorry guys, for the long delay in replying your pings, got busy with regular office stuff :-) Yes, It should go in v4.5, I did send request with my sign-off to Greg, he should take it via char-misc tree.I can't see this patches in the char-misc tree [1]. Can you please double check?
Hi Matthias, Thanks for the patience. You should expect them to see after v4.5-rc1, that's when Greg said he would push the patches. thanks, srini
Thanks, Matthias [1] https://git.kernel.org/cgit/linux/kernel/git/gregkh/char-misc.git/quoted
Thanks, sriniquoted
quoted
Andrew-CT Chen (3): dt-bindings: add document of mediatek efuse driver nvmem: mediatek: Add Mediatek EFUSE driver dts: arm64: Add EFUSE device node .../devicetree/bindings/nvmem/mtk-efuse.txt | 36 +++++++++ arch/arm64/boot/dts/mediatek/mt8173.dtsi | 5 ++ drivers/nvmem/Kconfig | 11 +++ drivers/nvmem/Makefile | 2 + drivers/nvmem/mtk-efuse.c | 89 ++++++++++++++++++++++ 5 files changed, 143 insertions(+) create mode 100644 Documentation/devicetree/bindings/nvmem/mtk-efuse.txt create mode 100644 drivers/nvmem/mtk-efuse.c -- 1.9.1 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo at vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/