On Mon, Oct 14, 2013 at 13:09 -0700, Greg Kroah-Hartman wrote: > > On Mon, Oct 14, 2013 at 02:40:44PM -0500, Kumar Gala wrote: > > > > Greg, > > > > Wondering your thoughts on drivers/qe vs something like > > drivers/soc/fsl/qe. The QuiccEngine (qe) is a communication core on > > some of the Freescale networking SoCs that provides the ability to do > > various networking/communication functionality. "Channels" on the QE > > can be used for various different things from ethernet, ATM, UART, or > > other functions. > > What makes the code "QE" specific? Are these devices that live on the > QE "bus", or are they controlling the QE controller?
You may think of the QUICC as a "programmable bitbang machine" if you like. The very same component runs arbitrary and rather different protocols depending on how you setup its parameters. There have been serial controllers capable of different protocols like UART or SPI or I2S, but all of them are "serial communication". There have been memory controllers which could bitbang different protocols (NAND, NOR/SRAM, DRAM), but all of them are "memory". The QUICC is just a little more versatile, and appears to cover cases which reside in different Linux kernel subsystems (like: it's neither serial nor network exclusively, but can be either and potentially more). IIUC the question which Kumar Gala was asking is where to put code for the component which is neither a strict subset of any subsystem. Please correct me if I'm wrong. virtually yours Gerhard Sittig -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr. 5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: off...@denx.de _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
