Mark, Liam,
The existing ASoC Tegra support is specifically for Tegra20. It turns out
that Tegra30 has pretty different hardware and requires different drivers.
A couple questions:
* The new drivers I've written use "tegra30" in Kconfig variable names,
filenames, symbol names, etc. Do you think it's a good idea to rename the
existing Tegra20 driver to basically s/tegra/tegra20/ everywhere so
everything is versioned, or do you think that's just unnecessary churn?
(My motivation is kinda like the device tree compatible properties always
being versioned)
* I assume there's little point my posting Tegra30 ASoC drivers for
inclusion in mainline, since there's no Tegra30 CPU support at all there
yet?
Thanks.
--
nvpublic