From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Brown Subject: Re: Associating devices with multiple parents Date: Fri, 17 Aug 2012 11:37:22 +0100 Message-ID: <20120817103722.GA32216@opensource.wolfsonmicro.com> References: <502D4B28.4020108@wwwdotorg.org> <502D6A3A.7060808@firmworks.com> 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: Stephen Warren , devicetree-discuss , Rob Herring , Alexandre Courbot List-Id: devicetree@vger.kernel.org On Thu, Aug 16, 2012 at 04:20:47PM -0600, Grant Likely wrote: > On Aug 16, 2012 3:46 PM, "Mitch Bradley" wrote: > > Is there an established Linux convention for expressing that dual-parent > > relationship for I2C? The phandle schemes for cross-tree gpio, clk, and > > interrupt relationships obviously bear some resemblance to the problem, > > but I haven't seen anything for I2C. > Yes. Place the codec under the i2c controller and use a tope level audio > complex node with phandles to both the codec and i2s nodes. The nVidia bindings are probably the best ones to look at as an example here.