From: Marek Szyprowski <m.szyprowski@samsung.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: linux-samsung-soc@vger.kernel.org, linux-pm@vger.kernel.org,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
Inki Dae <inki.dae@samsung.com>
Subject: Re: [PATCH 0/8] Power domains support for Exynos5433 SoCs
Date: Fri, 27 Jan 2017 08:47:44 +0100 [thread overview]
Message-ID: <6cbea032-86a3-20b9-6cdf-93099f553531@samsung.com> (raw)
In-Reply-To: <20170127074346.iwzaavl2lnu64uxq@kozik-lap>
Hi Krzysztof,
On 2017-01-27 08:43, Krzysztof Kozlowski wrote:
> On Wed, Jan 25, 2017 at 12:55:34PM +0100, Marek Szyprowski wrote:
>> Hello,
>>
>> This patchset is a final step to add support for all power domains
>> on Exynos5433 SoCs. This patchset contains patches for adding Exynos5433
>> support to Exynos power domain driver and definitions of all power
>> domains found in Exynos5433 SoCs.
>>
>> Patches have been generated on top of linux-next from 25th January 2017.
>>
>> This is a part of a larger task, which goal is to add support for power
>> domains on Exynos5433 SoCs / TM2 boards. All patches needed to get it
>> working have been pushed to the following git repo:
>> https://git.linaro.org/people/marek.szyprowski/linux-srpol.git v4.10-next-tm2-pd
>>
>> To get everything working following patches/patchsets are needed on top
>> of the linux-next tree:
> By "get everything working" you also mean that there is a runtime
> dependency? In other words, can I apply DTS patches here?
IMHO we should wait with applying pm domains DTS patches. Without ALL
other patches
kernel will sooner or later panic with "(a)synchronous external abort"
or deadlock
in a different way.
>
> Best regards,
> Krzysztof
>
>
>> 1. "Add support for the S6E3HA2 panel on TM2 board" v8 patchset:
>> http://www.spinics.net/lists/devicetree/msg157859.html
>> 2. "drm/exynos/decon5433: configure sysreg in case of hardware trigger" v2:
>> https://patchwork.kernel.org/patch/9493177/
>> 3. "Move pad retention control to Exynos pin controller driver" v3 patchset:
>> https://www.spinics.net/lists/arm-kernel/msg556074.html
>> 4. "Pad retentions support for Exynos5433" patchset
>> (posted a few minutes ago, no link yet available)
>> 5. "Exynos5433/TM2: add clocks configuration for display subsystem" patchset
>> (posted a few minutes ago, no link yet available)
>> 6. "clk: samsung: pll: Add enable/disable support for PLL35XX" patch
>> (posted a few minutes ago, no link yet available)
>> 7. "IOMMU probe deferral support" v7 patchset:
>> https://www.spinics.net/lists/arm-kernel/msg557110.html
>> 8. "Add runtime PM support for clocks (on Exynos SoC example)" v5 patchset
>> (posted a few minutes ago, no link yet available)
>> 9. "Power domains support for Exynos5433 SoCs" patchset
>> (this patchset)
>>
>> Best regards
>> Marek Szyprowski
>> Samsung R&D Institute Poland
>>
>>
>> Patch summary:
>>
>> Chanwoo Choi (1):
>> soc: samsung: pm_domains: Add new exynos5433 compatible
>>
>> Marek Szyprowski (7):
>> arm64: dts: exynos: Add GSCL power domain to Exynos 5433 SoC
>> arm64: dts: exynos: Add DISP power domain to Exynos 5433 SoC
>> arm64: dts: exynos: Add MSCL power domain to Exynos 5433 SoC
>> arm64: dts: exynos: Add MFC power domain to Exynos 5433 SoC
>> arm64: dts: exynos: Add AUD power domain to Exynos5433 SoC
>> arm64: dts: exynos: Add FSYS power domain to Exynos5433 SoC
>> arm64: dts: exynos: Add remaining power domains to Exynos5433 SoC
>>
>> .../devicetree/bindings/power/pd-samsung.txt | 1 +
>> arch/arm64/boot/dts/exynos/exynos5433.dtsi | 118 +++++++++++++++++++++
>> drivers/soc/samsung/pm_domains.c | 7 ++
>> 3 files changed, 126 insertions(+)
>>
>> --
>> 1.9.1
>>
>
Best regards
--
Marek Szyprowski, PhD
Samsung R&D Institute Poland
next prev parent reply other threads:[~2017-01-27 7:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170125115558eucas1p18dcb5c4cbab28dcb10bd412b825256b7@eucas1p1.samsung.com>
2017-01-25 11:55 ` [PATCH 0/8] Power domains support for Exynos5433 SoCs Marek Szyprowski
2017-01-25 11:55 ` [PATCH 1/8] soc: samsung: pm_domains: Add new exynos5433 compatible Marek Szyprowski
2017-01-27 7:42 ` Krzysztof Kozlowski
2017-01-25 11:55 ` [PATCH 2/8] arm64: dts: exynos: Add GSCL power domain to Exynos 5433 SoC Marek Szyprowski
2017-01-27 7:46 ` Krzysztof Kozlowski
2017-01-27 10:33 ` Marek Szyprowski
2017-01-27 11:28 ` Krzysztof Kozlowski
2017-01-25 11:55 ` [PATCH 3/8] arm64: dts: exynos: Add DISP " Marek Szyprowski
2017-01-25 11:55 ` [PATCH 4/8] arm64: dts: exynos: Add MSCL " Marek Szyprowski
2017-01-25 11:55 ` [PATCH 5/8] arm64: dts: exynos: Add MFC " Marek Szyprowski
2017-01-25 11:55 ` [PATCH 6/8] arm64: dts: exynos: Add AUD power domain to Exynos5433 SoC Marek Szyprowski
2017-01-25 11:55 ` [PATCH 7/8] arm64: dts: exynos: Add FSYS " Marek Szyprowski
2017-01-25 11:55 ` [PATCH 8/8] arm64: dts: exynos: Add remaining power domains " Marek Szyprowski
2017-01-27 7:43 ` [PATCH 0/8] Power domains support for Exynos5433 SoCs Krzysztof Kozlowski
2017-01-27 7:47 ` Marek Szyprowski [this message]
2017-01-27 7:52 ` Krzysztof Kozlowski
2017-01-27 7:59 ` 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=6cbea032-86a3-20b9-6cdf-93099f553531@samsung.com \
--to=m.szyprowski@samsung.com \
--cc=b.zolnierkie@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=inki.dae@samsung.com \
--cc=krzk@kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=s.nawrocki@samsung.com \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox