Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754565AbbKXN5b (ORCPT ); Tue, 24 Nov 2015 08:57:31 -0500 Received: from mailout3.w1.samsung.com ([210.118.77.13]:10966 "EHLO mailout3.w1.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754479AbbKXN51 (ORCPT ); Tue, 24 Nov 2015 08:57:27 -0500 X-AuditID: cbfec7f4-f79026d00000418a-00-56546cc50a24 Subject: Re: [RFD] Functional dependencies between devices To: Mark Brown References: <1623682.7KVblAB3KQ@vostro.rjw.lan> <564B224D.3050904@samsung.com> <20151117135549.GR31303@sirena.org.uk> <564D7145.40300@samsung.com> <20151121140428.GJ26072@sirena.org.uk> Cc: "Rafael J. Wysocki" , Linux PM list , Greg Kroah-Hartman , Linux Kernel Mailing List , Alan Stern , Grant Likely , Rob Herring , Tomeu Vizoso , Thierry Reding , Dmitry Torokhov , Geert Uytterhoeven , Michael Turquette From: Andrzej Hajda Message-id: <56546C9D.3090206@samsung.com> Date: Tue, 24 Nov 2015 14:56:45 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-version: 1.0 In-reply-to: <20151121140428.GJ26072@sirena.org.uk> Content-type: text/plain; charset=windows-1252 Content-transfer-encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprEIsWRmVeSWpSXmKPExsVy+t/xq7pHc0LCDN49EbOY+vAJm8X8l53s Fs9u7WWyOPBnB6NF8+L1bBaXd81hs/jce4TR4uIpV4szpy+xWvzfs4PdYsLvC2wWfWsvsVnc /s3nwOvx/kYru8eOu0sYPRZsKvXYtKqTzePOtT1sHocOdzB67J+7ht2jt/kdm8eWq+0sHrPv /mD0+LxJLoA7issmJTUnsyy1SN8ugSvj35RepoLzXBXz1ixlbmBcw9HFyMkhIWAi0bnhGwuE LSZx4d56NhBbSGApo8Trk1ZdjFxA9nNGiS/XHjB1MXJwCAtYSSx5JwdSIyKgLHH1+14WiPq9 jBILd1uA1DML9LBINPZdYAdJsAloSvzdfBNsKK+AlsTayQ8ZQWwWAVWJ48u3gcVFBSIkJk5o YIWoEZT4Mfke2FBOAWOJ1b/3MYLsZRbQk7h/UQskzCwgL7F5zVvmCYwCs5B0zEKomoWkagEj 8ypG0dTS5ILipPRcQ73ixNzi0rx0veT83E2MkJj6soNx8TGrQ4wCHIxKPLwzioLDhFgTy4or cw8xSnAwK4nwWuuHhAnxpiRWVqUW5ccXleakFh9ilOZgURLnnbvrfYiQQHpiSWp2ampBahFM lomDU6qBcdWvB6c3LPLImXrzNEv5LLHOP39aVDojnt4oPj9xwfHr9z76sxUe1840y2tlsbqm lh44oy5Pkito/omkNZ2+1SrBcwTvbeOYcMtIV8Np4hSJNRdPnchx2NBnvn5p5PIUa649MrpM 0fstqjW++C6TsXog8Sdogd3T9+cMrn+SYeELmPonacLThUosxRmJhlrMRcWJABP9Uz+lAgAA Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1568 Lines: 41 On 11/21/2015 03:04 PM, Mark Brown wrote: > On Thu, Nov 19, 2015 at 07:50:45AM +0100, Andrzej Hajda wrote: >> On 11/17/2015 02:55 PM, Mark Brown wrote: >>> This is going to be really common but I'm not sure I see a problem with >>> it in terms of what Raphael is proposing - could you go into more detail >>> on the problem you see here? >> If clock provider is not a device driver and it depends on clocks of >> another clock >> provider you cannot 'translate' this dependency as dependency between >> devices, > What makes you say that this is the case? There should be nothing > stopping us having dependencies between two devices of the same type. To be clear I described situation that one clock provider uses clock of another clock provider and consumer is not modeled as device. > >> so this RFD does not cover them. >> Additionally if you look into kernel there are many calls in form >> 'clk_get(NULL, name)', >> it suggests that not only clock providers are consumers without >> underlying device driver. > Like I said in my earlier reply: > > | > - many clock providers, irq domains are not provided by devices, > > | That seems like something we can and possibly should change if we want. > > This applies just as much to consumers as to providers. OK, then it is just something to do :) Regards Andrzej -- 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/