Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752736AbcDZRpU (ORCPT ); Tue, 26 Apr 2016 13:45:20 -0400 Received: from vps0.lunn.ch ([178.209.37.122]:46589 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751848AbcDZRpR (ORCPT ); Tue, 26 Apr 2016 13:45:17 -0400 Date: Tue, 26 Apr 2016 19:45:05 +0200 From: Andrew Lunn To: Florian Fainelli Cc: Pramod Kumar , Mark Rutland , devicetree@vger.kernel.org, Arnd Bergmann , Pawel Moll , Suzuki K Poulose , Catalin Marinas , Punit Agrawal , Will Deacon , linux-kernel@vger.kernel.org, Masahiro Yamada , Chen-Yu Tsai , Rob Herring , BCM Kernel Feedback , netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Anup Patel Subject: Re: [PATCH 1/6] bus: Add shared MDIO bus framework Message-ID: <20160426174505.GD11668@lunn.ch> References: <1461230323-27891-1-git-send-email-pramod.kumar@broadcom.com> <1461230323-27891-2-git-send-email-pramod.kumar@broadcom.com> <20160425205650.GA31129@lunn.ch> <666dffb41a922b0c8638f2f002a2de08@mail.gmail.com> <20160426121335.GC11668@lunn.ch> <571FA3F6.7000903@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <571FA3F6.7000903@gmail.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 Content-Length: 503 Lines: 12 > I am not clear on how common a shared MDIO bus is on other SoCs, but the > other Broadcom SoCs I am familiar with have dedicated MDIO buses > instances per type of PHY (PCIe, BUSB, Ethernet), thus making the split > a ton easier. I don't actually see this shared bus being an issue, once the mux it implemented. With the mux, you see N MDIO busses, each acting like a normal MDIO bus. I've used the GPIO variety and had no issues: http://marc.info/?l=linux-arm-kernel&m=145910090401796&w=2 Andrew