On Friday 15 April 2016 02:18 PM, Petr Kulhavy wrote: > On 13.04.2016 16:30, Rob Herring wrote: >> On Mon, Apr 11, 2016 at 01:45:12PM +0200, Petr Kulhavy wrote: >>> a/Documentation/devicetree/bindings/sound/davinci-mcbsp.txt >>> b/Documentation/devicetree/bindings/sound/davinci-mcbsp.txt >>> new file mode 100644 >>> index 000000000000..de45865c3863 >>> --- /dev/null >>> +++ b/Documentation/devicetree/bindings/sound/davinci-mcbsp.txt >>> @@ -0,0 +1,51 @@ >>> +Texas Instruments DaVinci McBSP module >>> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>> + >>> +This binding describes the "Multi-channel Buffered Serial Port" (McBSP) >>> +audio interface found in some TI DaVinci processors like the >>> OMAP-L138 or AM180x. >>> + >>> + >>> +Required properties: >>> +~~~~~~~~~~~~~~~~~~~~ >>> +- compatible : "ti,da850-mcbsp" >> You list several SoCs above, but only one compatible string here. A >> specific compatible string per SoC please. >> > Hi Rob, > > thank you for your feedback. I can test only on the AM1808 platform, > however as far as I understand the OMAP L138 and AM1808 use the same > McBSP hardware. The TI guys can give more insight here... Isn't it then > redundant to define more compatible strings? Sorry for my ignorance, I > just don't know the policy of defining the compatible strings. DA850, OMAP-L138 and AM18x are pin-for-pin compatible devices meant for different markets/applications. IP-wise, silicon-integration-wise or pin-wise, there is no difference in way McASP behaves between the parts. Thanks, Sekhar -- 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
