From mboxrd@z Thu Jan 1 00:00:00 1970 From: Russell King Subject: Re: Best practice device tree design for display subsystems/DRM Date: Fri, 5 Jul 2013 09:50:20 +0100 Message-ID: <20130705085020.GV13924@flint.arm.linux.org.uk> References: <20130702204255.2044c01b@armhf> <20130702191923.GD13924@flint.arm.linux.org.uk> <51D330AC.5060903@gmail.com> <20130702202548.GE13924@flint.arm.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org Sender: "devicetree-discuss" To: Grant Likely Cc: Jean-Francois Moine , "devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org" , Daniel Drake , dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org, Sebastian Hesselbarth List-Id: devicetree@vger.kernel.org On Fri, Jul 05, 2013 at 09:37:34AM +0100, Grant Likely wrote: > Alternatively, you can have the same effect with a property or set of > properties in the controller node that contains phandles to the > required devices. That would provide the driver with the same > information about which devices must be present. How do you go from phandle to something-that-the-driver-for-that-device- has-setup? >>From what I can see, you can go from phandle to OF node, but no further. I'm guessing we'd need some kind of "registry" for sub-drivers with these structures to register their devices OF node plus "shared" data so that other drivers can find it. "shared" data might be a standardized operations struct or something similar to 'struct device_driver' but for componentised devices. -- Russell King