Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751656AbbH1CDX (ORCPT ); Thu, 27 Aug 2015 22:03:23 -0400 Received: from mail-yk0-f171.google.com ([209.85.160.171]:36369 "EHLO mail-yk0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751113AbbH1CDV (ORCPT ); Thu, 27 Aug 2015 22:03:21 -0400 MIME-Version: 1.0 In-Reply-To: <7hmvxc45w2.fsf@deeprootsystems.com> References: <1440487486-6154-1-git-send-email-wxt@rock-chips.com> <1440487486-6154-5-git-send-email-wxt@rock-chips.com> <7hfv37axhj.fsf@deeprootsystems.com> <7htwrn6l7g.fsf@deeprootsystems.com> <7hmvxc45w2.fsf@deeprootsystems.com> Date: Thu, 27 Aug 2015 19:03:20 -0700 X-Google-Sender-Auth: vt1VnVBhQOpyIKnyYN73zu4LEpg Message-ID: Subject: Re: [RESEND PATCH v16 4/4] ARM: dts: add the support power-domain node on RK3288 SoCs From: Doug Anderson To: Kevin Hilman Cc: Dmitry Torokhov , Caesar Wang , =?UTF-8?Q?Heiko_St=C3=BCbner?= , Ulf Hansson , "linux-arm-kernel@lists.infradead.org" , "open list:ARM/Rockchip SoC..." , Tomasz Figa , "linux-kernel@vger.kernel.org" , Kumar Gala , Russell King , Rob Herring , Arnd Bergmann , Linus Walleij , Ian Campbell , "devicetree@vger.kernel.org" , "jinkun.hong" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1351 Lines: 31 Kevin, On Thu, Aug 27, 2015 at 5:24 PM, Kevin Hilman wrote: >> That is not really workable: the attach and detach happen in >> probe/remove path; if you do not have driver for the device you will >> miss the clocks for it. > > And in my proposal, I suggested that clocks without drivers are > good candidates to list in the domain, with the caveat that the be > called out (documented) as being device clocks that are missing a > driver, so when a driver shows up they can be moved accordingly, and in > a way that actually describes the hardware. What happens if someone disables the driver using the CONFIG subsystem? What happens if this is a device that someone has set to 'status = "disabled";' in the device tree? Even if the device is disabled in one of those two ways, we still need the clocks to be turned on. ...so if we turn on/off the VIO domain we need to turn on the EDP clock even if there's no EDP in the current board / config. We might turn on/off VIO for one of the other devices in the VIO domain for one of the other devices in VIO that we are using. -Doug -- 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/