[PATCH 14/18] ARM: mvebu: add support for the Armada 395 SoC family
Rob Herring
robh at kernel.org
Thu Jul 21 15:16:05 PDT 2016
On Thu, Jul 21, 2016 at 02:44:11PM +0200, Grzegorz Jaszczyk wrote:
> Beside interfaces described in the armada-39x.dtsi, the Armada 395 SoC
> family supports: 2 x SATA3 (2 ports in one unit) and the USB3.0
>
> Signed-off-by: Grzegorz Jaszczyk <jaz at semihalf.com>
> ---
> .../devicetree/bindings/arm/marvell/armada-39x.txt | 2 +-
> arch/arm/boot/dts/armada-395.dtsi | 76 ++++++++++++++++++++++
> 2 files changed, 77 insertions(+), 1 deletion(-)
> create mode 100644 arch/arm/boot/dts/armada-395.dtsi
>
> diff --git a/Documentation/devicetree/bindings/arm/marvell/armada-39x.txt b/Documentation/devicetree/bindings/arm/marvell/armada-39x.txt
> index 53d4ff9..f066801 100644
> --- a/Documentation/devicetree/bindings/arm/marvell/armada-39x.txt
> +++ b/Documentation/devicetree/bindings/arm/marvell/armada-39x.txt
> @@ -17,4 +17,4 @@ compatible: must contain "marvell,armada398"
>
> Example:
>
> -compatible = "marvell,a398-db", "marvell,armada398", "marvell,armada390";
> +compatible = "marvell,a398-db", "marvell,armada398", "marvell,armada395", "marvell,armada390";
If 395 came after 398, then it should come first in the order. This
implies that marvell,armada398 is a better match than marvell,armada395.
Or perhaps you shouldn't have both?
Rob
More information about the linux-arm-kernel
mailing list