On Fri, May 8, 2015 at 1:42 PM, Benson Leung <ble...@chromium.org> wrote:
> On Mon, May 4, 2015 at 10:36 AM, Andrew Bresticker
> <abres...@chromium.org> wrote:
>> + - compatible: For Tegra124, must contain "nvidia,tegra124-xusb-mbox".
>> + Otherwise, must contain '"nvidia,<chip>-xusb-mbox",
>> + "nvidia,tegra124-xusb-mbox"' where <chip> is tegra132.
>
> The driver doesn't seem to have any particular entry for tegra132, so
> that would be a bad example.
The convention on Tegra is to use "nvidia,<chip>-<ip>" for each IP
block. Additionally, since the XUSB-related blocks on Tegra132 are
identical to Tegra124, these devices on Tegra132 are 'compatible' with
their Tegra124 variants.
For some context, see Paul's comments in commit 193c9d23
("Documentation: DT bindings: add more Tegra chip compatible
strings").
Thanks,
Andrew
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
