drivers: soc: Add snapshot of gladiator erp driver

* MSM Gladiator error reporting driver

Required properties:

- compatible: Should be "qcom,msm-gladiator-v2"

- reg: I/O address Gladiator H/W block

- reg-names: Should be "gladiator_base"

- interrupts: Should contain the gladiator error interrupt number

- clock-names: Should be "atb_clk"

- clocks: Handles to clocks specified in "clock-names" property.

Example:

qcom,msm-gladiator-v2@b1c0000 {

	compatible = "qcom,msm-gladiator-v2";

	reg = <0xb1c0000 0xe000>;

	reg-names = "gladiator_base";

	interrupts = <0 34 0>;

	clock-names = "atb_clk";

	clocks = <&clock_gcc clk_qdss_clk>;

}

         If the configured threshold is reached, it causes SoC reset on

         gladiator hang detection and collects the context for the

         gladiator hang.

config MSM_GLADIATOR_ERP_V2

       tristate "GLADIATOR coherency interconnect error reporting driver v2"

       help

               Support dumping debug information for the GLADIATOR

               cache interconnect in the error interrupt handler.

               Meant to be used for debug scenarios only.

               If unsure, say N.

config PANIC_ON_GLADIATOR_ERROR_V2

       depends on MSM_GLADIATOR_ERP_V2

       bool "Panic on GLADIATOR error report v2"

       help

               Panic upon detection of an Gladiator coherency interconnect error

               in order to support dumping debug information.

               Meant to be used for debug scenarios only.

               If unsure, say N.

obj-$(CONFIG_QCOM_SCM)  +=      scm.o scm-boot.o

obj-$(CONFIG_SOC_BUS) += socinfo.o

obj-$(CONFIG_MSM_GLADIATOR_HANG_DETECT) += gladiator_hang_detect.o

obj-$(CONFIG_MSM_GLADIATOR_ERP_V2) += gladiator_erp_v2.o