linux-kernel - Re: [PATCH 1/4] ARM: EXYNOS5: Add PPMU device tree support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 14 Jan 2013 23:26:41 +0900
From:	MyungJoo Ham <myungjoo.ham@...sung.com>
To:	Abhilash Kesavan <a.kesavan@...sung.com>
Cc:	linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org,
	kgene.kim@...sung.com, kyungmin.park@...sung.com, rjw@...k.pl,
	jhbird.choi@...sung.com
Subject: Re: [PATCH 1/4] ARM: EXYNOS5: Add PPMU device tree support

On Wed, Jan 9, 2013 at 9:06 PM, Abhilash Kesavan <a.kesavan@...sung.com> wrote:
> PPMU is required by the devfreq driver. Add a device tree
> node for it.
>
> Signed-off-by: Abhilash Kesavan <a.kesavan@...sung.com>
> Cc: Jonghwan Choi <jhbird.choi@...sung.com>
> Cc: Kukjin Kim <kgene.kim@...sung.com>

Acked-by: MyungJoo Ham <myungjoo.ham@...sung.com>

> ---
>  .../bindings/arm/exynos/ppmu-exynos5.txt           |   28 ++++++++++++++++++++
>  arch/arm/boot/dts/exynos5250.dtsi                  |    9 ++++++
>  2 files changed, 37 insertions(+), 0 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/arm/exynos/ppmu-exynos5.txt
>
> diff --git a/Documentation/devicetree/bindings/arm/exynos/ppmu-exynos5.txt b/Documentation/devicetree/bindings/arm/exynos/ppmu-exynos5.txt
> new file mode 100644
> index 0000000..a424dfa
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/arm/exynos/ppmu-exynos5.txt
> @@ -0,0 +1,28 @@
> +Exynos5 PPMU driver
> +-------------------
> +
> +Performance events are primitive values used to get performance data. These
> +events provide information about the behavior of the SoC that can be used
> +when analyzing system performance. These events are made visible using the
> +PPMU logic.
> +Exynos5 PPMU driver is used by the exynos5 devfreq driver to control the bus
> +frequency/voltage.
> +
> +Required properties:
> +- compatible: should be one of the following.
> +       * samsung,exynos5-ppmu - for exynos5250 type ppmu.
> +- reg:
> +       * physical base address of the PPMUs (DDR, Right Bus and CPU) and
> +       length of memory mapped region.
> +
> +Example:
> +--------
> +
> +       ppmu {
> +               compatible = "samsung,exynos5250-ppmu";
> +               reg = <0x10C40000 0x2000
> +                      0x10C50000 0x2000
> +                      0x10C60000 0x2000
> +                      0x10CB0000 0x2000
> +                      0x13660000 0x2000>;
> +       };
> diff --git a/arch/arm/boot/dts/exynos5250.dtsi b/arch/arm/boot/dts/exynos5250.dtsi
> index 30485de..d504cba 100644
> --- a/arch/arm/boot/dts/exynos5250.dtsi
> +++ b/arch/arm/boot/dts/exynos5250.dtsi
> @@ -732,4 +732,13 @@
>                 interrupt-parent = <&combiner>;
>                 interrupts = <24 1>;
>         };
> +
> +       ppmu {
> +               compatible = "samsung,exynos5250-ppmu";
> +               reg = <0x10C40000 0x2000        /* PPMU_DDR_C */
> +                      0x10C50000 0x2000        /* PPMU_DDR_R1 */
> +                      0x10CB0000 0x2000        /* PPMU_DDR_L */
> +                      0x13660000 0x2000        /* PPMU_DDR_RIGHT */
> +                      0x10C60000 0x2000>;      /* PPMU_DDR_CPU */
> +       };
>  };
> --
> 1.7.8.6
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pm" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



-- 
MyungJoo Ham, Ph.D.
Mobile Software Platform Lab, DMC Business, Samsung Electronics
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/