On 08/20/2014 03:34 PM, Mark Rutland wrote:
...
Sorry, I meant in the same node. I take it we never expect:
compatible = "ti,am335x-beaglebone-black-audio", "ti,da830-evm-audio";
No never like that.
> >Is the 'x' in the BBB string a wildcard? If we know the particular
> >number for BBB we should use that.
> >
>
>Yes, its a wild card. BBBs have been made at least with AM3358 and
>AM3359 SoCs.
In general we've pushed back against wildcard strings, and used the
first implementation for the naming. We should be able to use
"ti,am3358-beaglebone-black-audio" for AM335{8,9} assuming the block is
the same? Otherwise we might need separate strings anyway.
At least the relevant block (McASP) is the same. AM335x is commonly used
in all TI documentation, but I am not picky am3358 is fine with me.
Could we drop the SoC id completely and make it just
"beaglebone-black-audio"?
The board design is the unique factor here, not the SoC. McASP block can
be found from several TI SoCs.
Cheers,
Jyri
--
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
