Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934020AbbKSKrI (ORCPT ); Thu, 19 Nov 2015 05:47:08 -0500 Received: from mailgw01.mediatek.com ([210.61.82.183]:46887 "EHLO mailgw01.mediatek.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1756459AbbKSKrG (ORCPT ); Thu, 19 Nov 2015 05:47:06 -0500 X-Listener-Flag: 11101 From: Andrew-CT Chen To: Srinivas Kandagatla CC: Maxime Ripard , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Matthias Brugger , Sascha Hauer , , , , , Subject: [PATCH v2 0/3] Mediatek EFUSE Support Date: Thu, 19 Nov 2015 18:46:51 +0800 Message-ID: <1447930014-19579-1-git-send-email-andrew-ct.chen@mediatek.com> X-Mailer: git-send-email 1.9.1 MIME-Version: 1.0 Content-Type: text/plain X-MTK: N Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1374 Lines: 34 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" 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/