Linux clock framework development
 help / color / mirror / Atom feed
From: Marek Szyprowski <m.szyprowski@samsung.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: linux-clk@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
	Sylwester Nawrocki <s.nawrocki@samsung.com>,
	Chanwoo Choi <cw00.choi@samsung.com>,
	Inki Dae <inki.dae@samsung.com>,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Subject: Re: [PATCH 0/4] Fix problems with Exynos4412 ISP clocks
Date: Tue, 03 Oct 2017 08:03:02 +0200	[thread overview]
Message-ID: <ec302c3d-c120-320a-dd58-4d26a9294907@samsung.com> (raw)
In-Reply-To: <20171002173631.lgkqfrtbacyzqeml@kozik-lap>

Hi Krzysztof,

On 2017-10-02 19:36, Krzysztof Kozlowski wrote:
> On Mon, Oct 02, 2017 at 12:47:55PM +0200, Marek Szyprowski wrote:
>> Exynos4412 ISP clock controller is located in the SOC area, which belongs
>> to ISP power domain. This was not properly handled by the current
>> Exynos4-clk driver. This patchset instantiates a separate clock driver
>> for those clocks, updates all clients of ISP clocks and ensures that
>> the driver is properly integrated in ISP power domin using runtime PM
>> feature of the clock framework.
>>
>> This finally solves all the mysterious freezes in accessing ISP clocks
>> when ISP power domain is disabled.
>>
>> The last patch breaks support for old dtbs. It can be applied when all
>> boards are updated. Exynos4412 ISP subsystem is only used by Trats2
>> boards, for which kernel is updated always together with the dtb file,
>> so the last patch can be applied to the next kernel release after merging
>> the DTS patch.
> I am fine with this approach. However I see that third patch (dts)
> depends on previous so it will also wait one cycle. arm-soc folks for
> some time do not accept code mixed with dts.
>
> Unless you can split dts into two patches: adding new clock controller
> and removing old. In such case the new clock could be applied in
> parallel to clk code changes.

DTS patch cannot be split into two patches without breaking ISP support,
because adding a new clock controller requires changes in the clients and
register resource size of the old one, so either old or new one has to be
fully defined. If arm-soc cannot pull mixed branches, then I'm okay with
postponing DTS changes by one release.

 > ...

Best regards
-- 
Marek Szyprowski, PhD
Samsung R&D Institute Poland


  reply	other threads:[~2017-10-03  6:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20171002104824eucas1p1f9795b5403b6cd599b1e33e9dc7b604f@eucas1p1.samsung.com>
2017-10-02 10:47 ` [PATCH 0/4] Fix problems with Exynos4412 ISP clocks Marek Szyprowski
2017-10-02 10:47   ` [PATCH 1/4] clk: samsung: Instantiate Exynos4412 ISP clocks only when available Marek Szyprowski
2017-10-02 17:40     ` Krzysztof Kozlowski
2017-10-02 10:47   ` [PATCH 2/4] clk: samsung: Add a separate driver for Exynos4412 ISP clocks Marek Szyprowski
2017-10-02 18:00     ` Krzysztof Kozlowski
2017-10-03  6:16       ` [PATCH v2] " Marek Szyprowski
2017-10-03 19:32         ` Krzysztof Kozlowski
2017-10-09 10:39         ` Sylwester Nawrocki
2017-10-10 17:08     ` [PATCH 2/4] " Rob Herring
2017-10-02 10:47   ` [PATCH 3/4] ARM: dts: exynos: Add Exynos4412 ISP clock controller Marek Szyprowski
2017-10-02 10:47   ` [PATCH 4/4] clk: samsung: Remove obsolete code for Exynos4412 ISP clocks Marek Szyprowski
2017-10-02 18:00     ` Krzysztof Kozlowski
2017-10-02 17:36   ` [PATCH 0/4] Fix problems with " Krzysztof Kozlowski
2017-10-03  6:03     ` Marek Szyprowski [this message]
2017-10-09 10:34   ` Sylwester Nawrocki
2017-10-09 10:49     ` Krzysztof Kozlowski
2017-10-09 10:58       ` Sylwester Nawrocki
2017-10-11  9:33         ` Sylwester Nawrocki

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=ec302c3d-c120-320a-dd58-4d26a9294907@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-clk@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