Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754889AbbG3KKH (ORCPT ); Thu, 30 Jul 2015 06:10:07 -0400 Received: from down.free-electrons.com ([37.187.137.238]:60332 "EHLO mail.free-electrons.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751013AbbG3KKE (ORCPT ); Thu, 30 Jul 2015 06:10:04 -0400 Date: Thu, 30 Jul 2015 12:09:08 +0200 From: Maxime Ripard To: Heiko =?iso-8859-1?Q?St=FCbner?= Cc: Stephen Boyd , Kevin Hilman , Mike Turquette , Doug Anderson , linux-clk@vger.kernel.org, lkml , "linux-arm-kernel@lists.infradead.org" , Boris Brezillon , Alex Elder , Alexandre Belloni , Stephen Warren , Max Filippov , Sascha Hauer , Zhangfei Gao , Santosh Shilimkar , Chao Xie , Jason Cooper , Stefan Wahren , Andrew Bresticker , Robert Jarzmik , Georgi Djakov , Sylwester Nawrocki , Geert Uytterhoeven , Barry Song , Dinh Nguyen , Viresh Kumar , Gabriel FERNANDEZ , Emilio =?iso-8859-1?Q?L=F3pez?= , Peter De Sc hrijver , Tero Kristo , Ulf Hansson , Pawel Moll , Michal Simek , Olof Johansson , Tyler Baker Subject: Re: [PATCH v3 0/2] clk: improve handling of orphan clocks Message-ID: <20150730100908.GI2564@lukather> References: <1429735986-18592-1-git-send-email-heiko@sntech.de> <554BD33D.7050907@codeaurora.org> <20150508100247.GQ11057@lukather> <4099394.C7vEjTFs8V@diego> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0OMWfJhzSPULbgPV" Content-Disposition: inline In-Reply-To: <4099394.C7vEjTFs8V@diego> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2558 Lines: 73 --0OMWfJhzSPULbgPV Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Heiko, On Mon, Jul 27, 2015 at 10:57:33AM +0200, Heiko St=FCbner wrote: > > > Also we can try to see if critical clocks aren't being forced on by > > > applying this patch and looking for clk_get() failures > >=20 > > And that shows that the CPU and DDR clocks are not protected, which > > obviously is pretty mad. > >=20 > > I've mass converted all our probing code to use OF_CLK_DECLARE, and > > make things work again. > >=20 > > http://code.bulix.org/5goa5j-88345?raw > >=20 > > Is this an acceptable solution? > >=20 > > We were already moving to this, I'm not really fond of doing this like > > that, but I guess this whole debacle makes it necessary. >=20 >=20 > did this lead anywhere meanwhile. >=20 > Last I remember the change to orphan handling made sunxi fail, but > I'm still hoping to get this usable at some point :-) To be honest, I don't know what the current status is. I haven't get any news since that mail. I started to move a significant portion of our clocks to CLK_OF_DECLARE, but not all of them are (which probably make the situation worse for the time being). Maxime --=20 Maxime Ripard, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com --0OMWfJhzSPULbgPV Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJVuffEAAoJEBx+YmzsjxAgj+AP/jqrMrqEMYIGWB1/O1aWO+rc jEt9NgPjkRayhyb8e7EbS7yAPbn2g9Y08LzPE1R4JAhyLh/5SLmGErz+vtzDGzs1 46eoSBeo3BulYWdZadj0gFX7bj+JhmNG2wYgl7BcMXoqkwHxD/pYk/tCAahXwyBQ Qd50eMDQkCKnfSiTHqPjM59ot2/E7bUrce9KFf1lJ5CkV4c7WyhMCXEUMnmrXqhk zfy73/GwR1ehWPkZJDKVdYwMB4k0xa89zskMCb7UWphpi7UVPCtEgTwsXq9NvMGK Af1dKba9Tsd6nNSdB58A5bG4yb0Kk1krQuAK1TN5qYdfvDH/6sdJGX+RSB2yOKUm yL3/Wizw/kL71jtJgNQZ50WTQfs6dhTYsfuKsA6y59QV8EyM2TjxyFo9IqjyJ79g bVT0jfxJVgHrhLeAsOGHv6Gg2jKDp5Okbousi+XbiEhX+ufBCcJf2T5OCSsIV5FQ 7brGQlr6N0vAjSE5XUl2qWLDrh3q5Ykm98clYSkt+Fu7/kMeD2/E8uNxBkk91f5f lLHJYb/wYVNGu4xWKIR9WuA6qVViguGid+uQ6B2SCzeYj9EoLU6xSS7fnzHs+yHN OYWcERBHbQYe2W3qv+F4OLYM9LWt347vvJ7kEQewJoHMhCpx6Lx9U4HJ68SzkKI1 l91PtXPaPeh+Mqbfy2te =ej/e -----END PGP SIGNATURE----- --0OMWfJhzSPULbgPV-- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/