On Wed, Jul 19, 2017 at 01:24:56AM +0530, Lokesh Vutla wrote:
> Adding board generic support for dra76 family.
>
> Signed-off-by: Lokesh Vutla <lokeshvutla@xxxxxx>
> ---
> Documentation/devicetree/bindings/arm/omap/omap.txt | 3 +++
> arch/arm/mach-omap2/board-generic.c | 1 +
> 2 files changed, 4 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/omap/omap.txt b/Documentation/devicetree/bindings/arm/omap/omap.txt
> index 8219b2c6bb29..ffe02755a285 100644
> --- a/Documentation/devicetree/bindings/arm/omap/omap.txt
> +++ b/Documentation/devicetree/bindings/arm/omap/omap.txt
> @@ -80,6 +80,9 @@ SoCs:
> - OMAP5432
> compatible = "ti,omap5432", "ti,omap5"
>
> +- DRA762
> + compatible = "ti,dra76", "ti,dra7"
76 or 762?
How many of these 2 or 3 compatible strings actually get used? I'd
prefer to see one of these less specific compatibles get dropped.
> +
> - DRA742
> compatible = "ti,dra742", "ti,dra74", "ti,dra7"
>
> diff --git a/arch/arm/mach-omap2/board-generic.c b/arch/arm/mach-omap2/board-generic.c
> index dc9e34e670a2..e5d9d769a76e 100644
> --- a/arch/arm/mach-omap2/board-generic.c
> +++ b/arch/arm/mach-omap2/board-generic.c
> @@ -312,6 +312,7 @@ MACHINE_END
>
> #ifdef CONFIG_SOC_DRA7XX
> static const char *const dra74x_boards_compat[] __initconst = {
> + "ti,dra76",
> "ti,am5728",
> "ti,am5726",
> "ti,dra742",
> --
> 2.13.0
>
--
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
