Re: [1/3][PATCH][v2] Device Tree bindings for Freescale TDM controller

[Scott Wood <scottwood@freescale.com>]

On Tue, 2015-04-14 at 08:50 -0500, Singh Sandeep-B37400 wrote:
> > > +TDM (Time Division Multiplexing)
> > > +
> > > +DESCRIPTION
> > > +
> > > +The TDM is full duplex serial port designed to allow various devices
> > > +including digital signal processors (DSPs) to communicate with a
> > > +variety of serial devices including industry standard framers, codecs, other
> > DSPs and microprocessors.
> > > +
> > > +The below properties describe the device tree bindings for Freescale
> > > +TDM controller.
> > > +This TDM controller is available on various Freescale Processors like
> > > +MPC8313, P1020, P1022 and P1010.
> > > +
> > > +PROPERTIES
> > > +
> > > +  - compatible
> > > +      Usage: required
> > > +      Value type: <string>
> > > +      Definition: Should contain "fsl,tdm1.0".
> > 
> > What does 1.0 refer to?  Is the TDM block identical on all the chips that currently
> > have it?  Is this a real version number scheme (public or
> > otherwise) or something made up for software?
> [Sandeep] Starlite TDM block is identical on all the chips. This is a software only version.

Then I recommend arbitrarily picking one of the chips and naming the
compatible after that: "fsl,mpc8313-tdm".

> > > +  - reg
> > > +      Usage: required
> > > +      Definition: A standard property. The first reg specifier describes the
> > > +          TDM registers, and the second describes the TDM DMAC registers.
> > > +
> > > +  - clock-frequency
> > > +      Usage: optional
> > > +      Value type: <u32 or u64>
> > > +      Definition: The frequency at which the TDM block is operating.
> > 
> > It'd be nice if new bindings used clock nodes rather than relying on U-Boot fixups.
> [Sandeep] This field is not currently used, but is planned to be used in future.

I don't see how that answers my request.

> > > +EXAMPLE
> > > +
> > > +	tdm@16000 {
> > > +		compatible = "fsl,tdm1.0";
> > > +		reg = <0x16000 0x200 0x2c000 0x2000>;
> > > +		clock-frequency = <0>;
> > > +		interrupts = <16 8 62 8>;
> > > +		phy-handle = <&zarlink1>;
> > > +		fsl,max-time-slots = <128>;
> > > +	};
> > 
> > The example refers to a "zarlink1" node but it is not present.  What does a "line
> > controller or framer node" look like?
> [Sandeep] phy-handle again is currently not being used. Added for future use.

Please submit a complete binding.

-Scott