From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754892AbcDYPU4 (ORCPT ); Mon, 25 Apr 2016 11:20:56 -0400 Received: from vps0.lunn.ch ([178.209.37.122]:45428 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752601AbcDYPUy (ORCPT ); Mon, 25 Apr 2016 11:20:54 -0400 Date: Mon, 25 Apr 2016 17:20:38 +0200 From: Andrew Lunn To: Pramod Kumar Cc: Rob Herring , Catalin Marinas , Will Deacon , Masahiro Yamada , Chen-Yu Tsai , BCM Kernel Feedback , Pawel Moll , Mark Rutland , Arnd Bergmann , Suzuki K Poulose , Punit Agrawal , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org Subject: Re: [PATCH 0/6] Add Shared MDIO framework for iProc based SoCs Message-ID: <20160425152038.GJ6575@lunn.ch> References: <1461230323-27891-1-git-send-email-pramod.kumar@broadcom.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1461230323-27891-1-git-send-email-pramod.kumar@broadcom.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Apr 21, 2016 at 02:48:37PM +0530, Pramod Kumar wrote: > Broadcom iProc based SoCs uses MDIO bus for programming PHYs belonging to > different I/O subsystem like USB, SATA, PCIe, ETHERNET etc. Every subsystem > is referred as "Master" When a master is selected, all PHYs belonging to > this subsystem get active on the MDIO bus and responds to MDIO transaction. > In this way one MDIO controller is shared among all masters hence named as > "Shared MDIO controller". > > We have two important entities in "Shared MDIO Bus" framework: > 1) shared_mdio_master and > 2) shared_mdio_driver. > > The shared MDIO controller driver is registered as platform driver and it > creates shared_mdio_master instances and adds them to "Shared MDIO Bus" > framework. Hi Pramod What i'm missing is an explanation why the existing MDIO bus framework cannot be used. I recently made it more generic so that you can hang any type of device off it, not just PHYs. Thanks Andrew From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Lunn Subject: Re: [PATCH 0/6] Add Shared MDIO framework for iProc based SoCs Date: Mon, 25 Apr 2016 17:20:38 +0200 Message-ID: <20160425152038.GJ6575@lunn.ch> References: <1461230323-27891-1-git-send-email-pramod.kumar@broadcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Rob Herring , Catalin Marinas , Will Deacon , Masahiro Yamada , Chen-Yu Tsai , BCM Kernel Feedback , Pawel Moll , Mark Rutland , Arnd Bergmann , Suzuki K Poulose , Punit Agrawal , devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Pramod Kumar Return-path: Content-Disposition: inline In-Reply-To: <1461230323-27891-1-git-send-email-pramod.kumar-dY08KVG/lbpWk0Htik3J/w@public.gmane.org> Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: netdev.vger.kernel.org On Thu, Apr 21, 2016 at 02:48:37PM +0530, Pramod Kumar wrote: > Broadcom iProc based SoCs uses MDIO bus for programming PHYs belonging to > different I/O subsystem like USB, SATA, PCIe, ETHERNET etc. Every subsystem > is referred as "Master" When a master is selected, all PHYs belonging to > this subsystem get active on the MDIO bus and responds to MDIO transaction. > In this way one MDIO controller is shared among all masters hence named as > "Shared MDIO controller". > > We have two important entities in "Shared MDIO Bus" framework: > 1) shared_mdio_master and > 2) shared_mdio_driver. > > The shared MDIO controller driver is registered as platform driver and it > creates shared_mdio_master instances and adds them to "Shared MDIO Bus" > framework. Hi Pramod What i'm missing is an explanation why the existing MDIO bus framework cannot be used. I recently made it more generic so that you can hang any type of device off it, not just PHYs. Thanks Andrew -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 From: andrew@lunn.ch (Andrew Lunn) Date: Mon, 25 Apr 2016 17:20:38 +0200 Subject: [PATCH 0/6] Add Shared MDIO framework for iProc based SoCs In-Reply-To: <1461230323-27891-1-git-send-email-pramod.kumar@broadcom.com> References: <1461230323-27891-1-git-send-email-pramod.kumar@broadcom.com> Message-ID: <20160425152038.GJ6575@lunn.ch> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Thu, Apr 21, 2016 at 02:48:37PM +0530, Pramod Kumar wrote: > Broadcom iProc based SoCs uses MDIO bus for programming PHYs belonging to > different I/O subsystem like USB, SATA, PCIe, ETHERNET etc. Every subsystem > is referred as "Master" When a master is selected, all PHYs belonging to > this subsystem get active on the MDIO bus and responds to MDIO transaction. > In this way one MDIO controller is shared among all masters hence named as > "Shared MDIO controller". > > We have two important entities in "Shared MDIO Bus" framework: > 1) shared_mdio_master and > 2) shared_mdio_driver. > > The shared MDIO controller driver is registered as platform driver and it > creates shared_mdio_master instances and adds them to "Shared MDIO Bus" > framework. Hi Pramod What i'm missing is an explanation why the existing MDIO bus framework cannot be used. I recently made it more generic so that you can hang any type of device off it, not just PHYs. Thanks Andrew