summaryrefslogtreecommitdiffstats
path: root/Documentation/email-clients.txt
diff options
context:
space:
mode:
authorPeter Ujfalusi <peter.ujfalusi@ti.com>2014-05-07 13:20:46 +0300
committerTero Kristo <t-kristo@ti.com>2014-05-28 13:06:52 +0300
commit2d5e447914722f3c79103ad54baa1170661ac553 (patch)
tree424338cc2f483c9a3776aa4daedc40585b6a68c1 /Documentation/email-clients.txt
parent0cccd9190009aa6c037aa88a85f2a1b72a6a7963 (diff)
downloadlinux-2d5e447914722f3c79103ad54baa1170661ac553.tar.gz
linux-2d5e447914722f3c79103ad54baa1170661ac553.tar.bz2
linux-2d5e447914722f3c79103ad54baa1170661ac553.zip
dt:/bindings: DRA7 ATL (Audio Tracking Logic) clock bindings
Audio Tracking Logic is designed to be used by HD Radio applications to synchronize the audio output clocks to the baseband clock. ATL can be also used to track errors between two reference clocks (BWS, AWS) and generate a modulated clock output which averages to some desired frequency. In essence ATL is generating a clock to be used by an audio codec and also to be used by the SoC as MCLK. To be able to integrate the ATL provided clocks to the clock tree we need two types of DT binding: - DT clock nodes to represent the ATL clocks towards the CCF - binding for the ATL IP itself which is going to handle the hw configuration The reason for this type of setup is that ATL itself is a separate device in the SoC, it has it's own address space and clock domain. Other IPs can use the ATL generated clock as their functional clock (McASPs for example) and external components like audio codecs can also use the very same clock as their MCLK. The ATL IP in DRA7 contains 4 ATL instences. Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com> Signed-off-by: Tero Kristo <t-kristo@ti.com>
Diffstat (limited to 'Documentation/email-clients.txt')
0 files changed, 0 insertions, 0 deletions