tree 0fd5a69c3c1a8431ae72c2c00b7d69e568a4f331
parent 38a5882e4292d135cebabad0b56c9420dfdd80a5
author Sriram Periyasamy <sriramx.periyasamy@intel.com> 1511352586 +0530
committer Mark Brown <broonie@kernel.org> 1511969987 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 iQFHBAABCgAxFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAloe1MMTHGJyb29uaWVA
 a2VybmVsLm9yZwAKCRAk1otyXVSH0JsTB/9+pkINt8mWiO4pWBQheoaVaUQFhmc7
 aoDyvU4R6lJNFCF5pHTxtuZUy9rCIUyuKeSFq7tLMXN5na0f80WGrezfDyL0TrgN
 dfrbaXvoFrOdU5Lg+Xr+uaCv2TcLVtJKlQevkpzeeG4efcFUSLViiRwMiD8X4FMe
 LinHpdB7c2HjhTFs350YQF+TM/pc98lY0mIlqa5OU7tuMdHY6j7Xd0c/X9To8SGB
 TrDvDtAfHYb3p4OoTKZ4DqEXQRs1aCNgqAGKGnYHEYIKMscye0U73G4eMeJTILCL
 GL9EOwQZ3L0+g6iTRMTPPCoKGgPGAClKeQ9eEbhoY4uUDh8XYYVhyTeK
 =uO5o
 -----END PGP SIGNATURE-----

ASoC: Intel: Skylake: Parse nhlt and register clock device

When NHLT endpoint is present for a SSP then we create clock for that SSP.

MCLK is consistent across endpoints and configuration for an SSP, so query
only for first endpoint for an SSP.

For SCLK/SCLKFS, the best fit is queried from the NHLT configurations which
matches the clock rate requested. Best fit is decided based on below:

1. If rate matches with multiple configurations, then the first
   configuration is selected.

2. If for a selected fs and bits_per_sample, there are multiple endpoint
   configuration match, then the configuration with max number of
   channels is selected. So, the user has to set the rate which fits
   max number of channels

So we create a platform device and pass clock information parsed as
platform data.

Signed-off-by: Sriram Periyasamy <sriramx.periyasamy@intel.com>
Signed-off-by: Jaikrishna Nemallapudi <jaikrishnax.nemallapudi@intel.com>
Signed-off-by: Subhransu S. Prusty <subhransu.s.prusty@intel.com>
Signed-off-by: Mark Brown <broonie@kernel.org>