Hi Andrew, Thanks for reviewing. Please see my comment inline.
> -----Original Message----- > From: Andrew Lunn [mailto:and...@lunn.ch] > Sent: 30 May 2016 19:05 > To: Pramod Kumar > Cc: Rob Herring; Pawel Moll; Mark Rutland; Ian Campbell; Kumar Gala; Catalin > Marinas; Will Deacon; Kishon Vijay Abraham I; David S. Miller; > devicet...@vger.kernel.org; net...@vger.kernel.org; linux- > ker...@vger.kernel.org; bcm-kernel-feedback-l...@broadcom.com; linux-arm- > ker...@lists.infradead.org > Subject: Re: [PATCH 5/7] net:mdio-mux: Add MDIO mux driver for iProc SoCs > > On Mon, May 30, 2016 at 12:40:49PM +0530, Pramod Kumar wrote: > > iProc based SoCs supports the integrated mdio multiplexer which has > > the bus selection as well as mdio transaction generation logic inside. > > Hi Pramod > > Great to see you using the existing MDIO framework. Thanks. > > > +static int mdio_mux_iproc_switch_fn(int current_child, int desired_child, > > + void *data) > > +{ > > + struct iproc_mdiomux_desc *md = data; > > + struct mdiomux_bus_param *bp = &md->bus_param[desired_child]; > > + u32 param, bus_id; > > + bool bus_dir; > > + > > + /* select bus and its properties */ > > + bus_dir = (desired_child < EXT_BUS_START_ADDR); > > + bus_id = bus_dir ? desired_child : (desired_child - > > +EXT_BUS_START_ADDR); > > + > > + param = (bus_dir ? 1 : 0) << MDIO_PARAM_INTERNAL_SEL; > > + param |= (bp->is_c45 ? 1 : 0) << MDIO_PARAM_C45_SEL; > > + param |= (bus_id << MDIO_PARAM_BUS_ID); > > + > > + writel(param, md->base + MDIO_PARAM_OFFSET); > > + return 0; > > +} > > What i don't yet see is why you went for the concept of an integrated MDIO and > MUX. This function above is the mux function, and it looks like it could be used > to implement a standard mdio-mux driver. > iProc based SoCs Integrated MDIO Multiplexer has both logic in a hardware. MDIO transaction and Child bus selection logic share the same address space. For ex- In above mux function- Register-MDIO_PARAM_OFFSET is used for bus, direction and transaction type. Same register Is used for programming the PHY Ids and write data values in MDIO parent bus transaction. Writing MDIO bus driver and mux driver separately gives a notion of being two separate device/address space, obviously it is not our use case. Even if we used syscon for accessing the shared register, this does not appears good for writing separate drivers for a single device. > Thanks > Andrew Regards, Pramod
