From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] clk: sunxi: delay protected clocks until arch initcall
Date: Wed, 27 Jan 2016 17:14:17 +0100 [thread overview]
Message-ID: <7334994.mKnQpNNMP2@diego> (raw)
In-Reply-To: <20160127153722.GC4317@lukather>
Hi,
Am Mittwoch, 27. Januar 2016, 16:37:22 schrieb Maxime Ripard:
> I thought the patches were simply dropped and the
> rockchip people just took another approach.
nope still on track ... especially as it was Stephen's believe that orphans
shouldn't even be usable to general clock users :-).
I just remember that the proposed general solution was based on Mike's
upcoming generic critical clock handling (the handoff thingy), which would
move critical clock handling out of architecture-specific code, so I've been
prodding Mike mainly.
Another option might be to allow clock-controllers to handle orphans and only
deny orphan usage to outside clock users, maybe expanding on what I did with
the clock-conf part in patch2.
Heiko
next prev parent reply other threads:[~2016-01-27 16:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 14:10 [PATCH 0/2] defer clk_gets on orphan clocks Emilio López
2016-01-21 14:10 ` [PATCH 1/2] clk: sunxi: delay protected clocks until arch initcall Emilio López
2016-01-27 15:37 ` Maxime Ripard
2016-01-27 16:14 ` Heiko Stübner [this message]
2016-01-27 20:38 ` Maxime Ripard
2016-01-27 21:07 ` Heiko Stübner
2016-01-27 18:53 ` Emilio López
2016-02-01 19:32 ` Maxime Ripard
2016-01-21 14:19 ` [PATCH 2/2] clk: defer clk_gets on orphan clocks Emilio López
2016-01-28 8:23 ` Stephen Boyd
2016-01-28 9:03 ` Heiko Stübner
2016-01-29 19:54 ` Stephen Boyd
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=7334994.mKnQpNNMP2@diego \
--to=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.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: 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;
as well as URLs for NNTP newsgroup(s).