From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mitch Bradley Subject: Associating devices with multiple parents Date: Thu, 16 Aug 2012 11:46:34 -1000 Message-ID: <502D6A3A.7060808@firmworks.com> References: <502D4B28.4020108@wwwdotorg.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <502D4B28.4020108-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org> 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: Stephen Warren Cc: devicetree-discuss , Mark Brown , Rob Herring , Alexandre Courbot List-Id: devicetree@vger.kernel.org Here is the situation: We (OLPC) have an audio codec that is strongly associated with an audio controller, but it also has some registers that you get at with I2C. In some sense, the codec has two parents, the audio controller (connected via I2S) and the I2C controller. 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. (We actually have two devices with the same problem - the other is an LCD panel controller than wants to be a child of the display device, but also has some I2C registers accessed by an IC2 controller that's not part of the display controller.)