On 03/19/2014 08:21 PM, Mark Brown wrote:
On Wed, Mar 19, 2014 at 09:15:14PM +0200, Jyri Sarha wrote:
On 03/19/2014 08:51 PM, Lars-Peter Clausen wrote:
When does this make sense? Either the bitclock is inverted for all of
them or for none.
Definition of clock signal and it's inversion varies between chip
manufacturers and sometimes it may not be possible to get all the dai
drivers to work identically in this respect. Because of this in some cases
there may be a need to set the inversion bit only at one end of the link.
No, Linux has a definition of all the clock modes which applies to all
devices regardless of what the manufacturer documents in their
datasheet.
Yep. The clock properties are well defined for the different modes that can
be specified in the format property. It's up to the driver to translate this
to driver specific settings. If two drivers behave differently for the same
mode one of them (or both) are broken.
We should probably add the definitions for the different formats to the DT
bindings. E.g. what is default, what is inverted polarity, etc.
- Lars
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
