From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <4FBE89D9.2090307@gmail.com> Date: Thu, 24 May 2012 12:19:53 -0700 From: David Daney MIME-Version: 1.0 To: Timur Tabi Subject: Re: [PATCH v6 0/3] netdev/of/phy: MDIO bus multiplexer support. References: <1336007799-31016-1-git-send-email-ddaney.cavm@gmail.com> <4FB6C728.3090507@gmail.com> <4FB6C886.3050105@freescale.com> <4FB6CBF1.40300@gmail.com> <4FBE7DD8.509@freescale.com> <4FBE82F2.6080100@gmail.com> <4FBE8605.2020507@freescale.com> In-Reply-To: <4FBE8605.2020507@freescale.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Cc: "netdev@vger.kernel.org" , "devicetree-discuss@lists.ozlabs.org" , "linuxppc-dev@lists.ozlabs.org" List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 05/24/2012 12:03 PM, Timur Tabi wrote: > David Daney wrote: > >> Well, the MDIO bus must have an associated device tree node. >> >> For my OCTEON code, the MDIO bus device is created as a result of the >> call to of_platform_bus_probe(), which takes care of filling in all the >> device tree nodes of the devices it finds and creates. > > Ok, let me give you some background. We actually already have MDIO muxing > code in-house, but it's different from yours. So now I'm rewriting it to > use your design instead. > > So our current code looks for "virtual MDIO nodes", and we call > mdiobus_alloc() and then of_mdiobus_register(). I think this is what I'm > missing now. > > I just don't know what to do next. You will have to debug it and find out why the device match is failing, then fix it. David Daney