Hi, On Tue, May 12, 2020 at 11:18 AM Ravi Kumar Bokka <rbokka@xxxxxxxxxxxxxx> wrote: > > This patch series adds qfprom-efuse controller driver support. > > This driver can access the raw qfprom regions for fuse blowing. > > The current existed qfprom driver is only supports for cpufreq, thermal sensors > drivers by read out calibration data, speed bins..etc which is stored by > qfprom efuses. I don't understand the interaction between this driver and the existing "qcom,qfprom" driver. Can you please explain? Are they both acting on the same values and this one has write access? Are there two instances of the same hardware block and you're managing one of them with this new driver and one with thue old driver? Something else? > Ravi Kumar Bokka (3): > dt-bindings: nvmem: Add devicetree bindings for qfprom-efuse > drivers: nvmem: Add driver for QTI qfprom-efuse support > arm64: dts: qcom: sc7180: Add qfprom-efuse > > .../devicetree/bindings/nvmem/qfprom-efuse.yaml | 40 ++ > arch/arm64/boot/dts/qcom/sc7180-idp.dts | 4 + > arch/arm64/boot/dts/qcom/sc7180.dtsi | 9 + > drivers/nvmem/Kconfig | 10 + > drivers/nvmem/Makefile | 2 + > drivers/nvmem/qfprom-efuse.c | 476 +++++++++++++++++++++ > 6 files changed, 541 insertions(+) > create mode 100644 Documentation/devicetree/bindings/nvmem/qfprom-efuse.yaml > create mode 100644 drivers/nvmem/qfprom-efuse.c > > -- > Qualcomm INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by the Linux Foundation. >
