From: Marek Szyprowski <m.szyprowski@samsung.com> To: linux-samsung-soc@vger.kernel.org, linux-arm-kernel@lists.infradead.org Cc: Chanwoo Choi <cw00.choi@samsung.com>, Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>, Krzysztof Kozlowski <krzk@kernel.org>, Marek Szyprowski <m.szyprowski@samsung.com> Subject: [PATCH v2 0/2] Exynos SoCs: enable support for ARM Architected Timers Date: Mon, 26 Aug 2019 12:31:40 +0200 [thread overview] Message-ID: <20190826103142.3477-2-m.szyprowski@samsung.com> (raw) In-Reply-To: <20190826103142.3477-1-m.szyprowski@samsung.com> Dear All, ARM Architected Timers are present in all CortexA7/A15 based Samsung Exynos SoCs. So far they were not enabled, because there were some issues related to their initialization. Samsung Exynos SoCs used custom timer hardware - Exynos MultiCore Timer. It turned out that enabling MCT it is also needed to get ARM Architected Timers working, because they both share some common hardware blocks (global system counter). This patchset enables support for ARM Architected Timer driver together with a standard Exynos MultiCore Timer driver, which is kept as a default timer source on ARM 32bit platforms. Support for ARM architected timers is essential for enabling proper KVM support on those platforms. Best regards Marek Szyprowski Samsung R&D Institute Poland Changelog: v2: - dropped MCT patches (merged to v5.1) - dropped timer priority change patch (merged to v5.3) v1: https://patchwork.kernel.org/cover/10814913/ - initial version, covers some MCT patches previously sent as a timer rework for Exynos5433 Patch summary: Marek Szyprowski (2): ARM: dts: exynos: Add support ARM architected timers ARM: exynos: Enable support for ARM architected timers arch/arm/boot/dts/exynos3250.dtsi | 10 ++++++++++ arch/arm/boot/dts/exynos5250.dtsi | 1 + arch/arm/boot/dts/exynos54xx.dtsi | 10 ++++++++++ arch/arm/mach-exynos/Kconfig | 1 + 4 files changed, 22 insertions(+) -- 2.17.1
WARNING: multiple messages have this Message-ID (diff)
From: Marek Szyprowski <m.szyprowski@samsung.com> To: linux-samsung-soc@vger.kernel.org, linux-arm-kernel@lists.infradead.org Cc: Chanwoo Choi <cw00.choi@samsung.com>, Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>, Krzysztof Kozlowski <krzk@kernel.org>, Marek Szyprowski <m.szyprowski@samsung.com> Subject: [PATCH v2 0/2] Exynos SoCs: enable support for ARM Architected Timers Date: Mon, 26 Aug 2019 12:31:40 +0200 [thread overview] Message-ID: <20190826103142.3477-2-m.szyprowski@samsung.com> (raw) In-Reply-To: <20190826103142.3477-1-m.szyprowski@samsung.com> Dear All, ARM Architected Timers are present in all CortexA7/A15 based Samsung Exynos SoCs. So far they were not enabled, because there were some issues related to their initialization. Samsung Exynos SoCs used custom timer hardware - Exynos MultiCore Timer. It turned out that enabling MCT it is also needed to get ARM Architected Timers working, because they both share some common hardware blocks (global system counter). This patchset enables support for ARM Architected Timer driver together with a standard Exynos MultiCore Timer driver, which is kept as a default timer source on ARM 32bit platforms. Support for ARM architected timers is essential for enabling proper KVM support on those platforms. Best regards Marek Szyprowski Samsung R&D Institute Poland Changelog: v2: - dropped MCT patches (merged to v5.1) - dropped timer priority change patch (merged to v5.3) v1: https://patchwork.kernel.org/cover/10814913/ - initial version, covers some MCT patches previously sent as a timer rework for Exynos5433 Patch summary: Marek Szyprowski (2): ARM: dts: exynos: Add support ARM architected timers ARM: exynos: Enable support for ARM architected timers arch/arm/boot/dts/exynos3250.dtsi | 10 ++++++++++ arch/arm/boot/dts/exynos5250.dtsi | 1 + arch/arm/boot/dts/exynos54xx.dtsi | 10 ++++++++++ arch/arm/mach-exynos/Kconfig | 1 + 4 files changed, 22 insertions(+) -- 2.17.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-08-26 10:31 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <CGME20190826103201eucas1p1358f33d8fbdc8cef8ba2ebdcb1b3a51a@eucas1p1.samsung.com> 2019-08-26 10:31 ` [PATCH 0/5] Exynos SoCs: enable support for ARM Architected Timers Marek Szyprowski 2019-08-26 10:31 ` Marek Szyprowski [not found] ` <CGME20190826103202eucas1p123d075e3da50b5aa1574ae46aa6aa946@eucas1p1.samsung.com> 2019-08-26 10:31 ` Marek Szyprowski [this message] 2019-08-26 10:31 ` [PATCH v2 0/2] " Marek Szyprowski [not found] ` <CGME20190826103202eucas1p16bd422bd505086e9ee27f528a8b48d57@eucas1p1.samsung.com> 2019-08-26 10:31 ` [PATCH v2 1/2] ARM: dts: exynos: Add support ARM architected timers Marek Szyprowski 2019-08-26 10:31 ` Marek Szyprowski [not found] ` <CGME20190826103203eucas1p2d67b0ef44758eb06252b340f7751701a@eucas1p2.samsung.com> 2019-08-26 10:31 ` [PATCH v2 2/2] ARM: exynos: Enable support for " Marek Szyprowski 2019-08-26 10:31 ` Marek Szyprowski 2019-08-26 10:49 ` Marc Zyngier 2019-08-26 10:49 ` Marc Zyngier 2019-08-28 8:22 ` Marek Szyprowski 2019-08-28 8:22 ` Marek Szyprowski
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20190826103142.3477-2-m.szyprowski@samsung.com \ --to=m.szyprowski@samsung.com \ --cc=b.zolnierkie@samsung.com \ --cc=cw00.choi@samsung.com \ --cc=krzk@kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-samsung-soc@vger.kernel.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.