public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Marek Szyprowski <m.szyprowski@samsung.com>
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 09:52:32 +0200	[thread overview]
Message-ID: <20170127075232.it4c4e7a3hno7i7e@kozik-lap> (raw)
In-Reply-To: <6cbea032-86a3-20b9-6cdf-93099f553531@samsung.com>

On Fri, Jan 27, 2017 at 08:47:44AM +0100, Marek Szyprowski wrote:
> 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.

Okay, makes sense. A partial solution would be to apply them with
status=disabled. After all it is still a valid description of a
hardware. However this would not bring much benefits anyway...

Beside the name of node I mentioned, please put all the power domains
sorted to each other by address. I see the big picture here:
https://git.linaro.org/people/marek.szyprowski/linux-srpol.git/tree/arch/arm64/boot/dts/exynos/exynos5433.dtsi?h=v4.10-next-tm2-pd
and it does not looks ordered.

Best regards,
Krzysztof

  reply	other threads:[~2017-01-27  7:52 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
2017-01-27  7:52       ` Krzysztof Kozlowski [this message]
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=20170127075232.it4c4e7a3hno7i7e@kozik-lap \
    --to=krzk@kernel.org \
    --cc=b.zolnierkie@samsung.com \
    --cc=cw00.choi@samsung.com \
    --cc=inki.dae@samsung.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --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