On 08/10/2011 12:19 PM, Robin Holt wrote: > On Wed, Aug 10, 2011 at 11:56:28AM -0500, Scott Wood wrote: >> On 08/10/2011 11:27 AM, Robin Holt wrote: >>> -CPI Clock- Can Protocol Interface Clock >>> - This CLK_SRC bit of CTRL(control register) selects the clock source to >>> - the CAN Protocol Interface(CPI) to be either the peripheral clock >>> - (driven by the PLL) or the crystal oscillator clock. The selected clock >>> - is the one fed to the prescaler to generate the Serial Clock (Sclock). >>> - The PRESDIV field of CTRL(control register) controls a prescaler that >>> - generates the Serial Clock (Sclock), whose period defines the >>> - time quantum used to compose the CAN waveform. >>> +- compatible : Should be "fsl,flexcan" and optionally >>> + "fsl,flexcan-<processor>" >> >> fsl,<processor>-flexcan, and it should not be optional, and should come >> before "fsl,flexcan". >> >> Also may want to list fsl,p1010-rdb as a "canonical compatible" for >> anything which is backwards compatible with p1010's implementation. > > How do I specify 'canonical compatible'?
Something like: compatible: Should be "fsl,<processor>-flexcan" and "fsl,flexcan". An implementation should also claim any of the following compatibles that it is fully backwards compatible with: - fsl,p1010-rdb > What would be the use of it in that implementation? It limits the number of compatibles a driver has to care about, so you don't need a huge ID table just to be able to figure out whether this is a p1010-style flexcan or ARM-style. -Scott _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
