linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND][PATCH 6/6] arm64: Add DTS support for FSL's LS2088A SoC
Date: Mon, 14 Nov 2016 14:33:48 +0800	[thread overview]
Message-ID: <20161114063346.GH3310@dragon> (raw)
In-Reply-To: <1478597664-14799-7-git-send-email-abhimanyu.saini@nxp.com>

On Tue, Nov 08, 2016 at 03:04:24PM +0530, Abhimanyu Saini wrote:
> This patch adds the device tree support for FSL LS2088A SoC based on
> ARMv8 architecture.
> 
> Following levels of DTSI/DTS files have been created for the LS2088A
> SoC family:
> 
>      - fsl-ls2088a.dtsi:
>             DTS-Include file for FSL LS2088A SoC.
> 
>      - fsl-ls2088a-qds.dts:
>             DTS file for FSL LS2088A QDS board.
> 
>      - fsl-ls2088a-rdb.dts:
>             DTS file for FSL LS2088A RDB board.

I compared the following files.

 fsl-ls2088a.dtsi vs. fsl-ls2080a.dtsi
 fsl-ls2088a-qds.dtsi vs. fsl-ls2080a-qds.dtsi
 fsl-ls2088a-rdb.dtsi vs. fsl-ls2080a-rdb.dtsi

They are basically identical except a couple of small changes.  Can we
do something to have these SoCs share the dts files at some level to
avoid maintaining duplicated files?

Shawn 

> Signed-off-by: Priyanka Jain <priyanka.jain@nxp.com>
> Signed-off-by: Ashish Kumar <ashish.kumar@nxp.com>
> Signed-off-by: Abhimanyu Saini <abhimanyu.saini@nxp.com>
> ---
>  arch/arm64/boot/dts/freescale/Makefile            |   2 +
>  arch/arm64/boot/dts/freescale/fsl-ls2088a-qds.dts | 211 +++++++
>  arch/arm64/boot/dts/freescale/fsl-ls2088a-rdb.dts | 166 +++++
>  arch/arm64/boot/dts/freescale/fsl-ls2088a.dtsi    | 703 ++++++++++++++++++++++
>  4 files changed, 1082 insertions(+)
>  create mode 100644 arch/arm64/boot/dts/freescale/fsl-ls2088a-qds.dts
>  create mode 100644 arch/arm64/boot/dts/freescale/fsl-ls2088a-rdb.dts
>  create mode 100644 arch/arm64/boot/dts/freescale/fsl-ls2088a.dtsi

       reply	other threads:[~2016-11-14  6:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1478597664-14799-1-git-send-email-abhimanyu.saini@nxp.com>
     [not found] ` <1478597664-14799-7-git-send-email-abhimanyu.saini@nxp.com>
2016-11-14  6:33   ` Shawn Guo [this message]
2016-11-17 12:31     ` [RESEND][PATCH 6/6] arm64: Add DTS support for FSL's LS2088A SoC Abhimanyu Saini
     [not found] ` <1478597664-14799-2-git-send-email-abhimanyu.saini@nxp.com>
2016-11-14 17:11   ` [RESEND][PATCH 1/6] dt-bindings: arm: Update bindings for LS2088A targets Rob Herring
     [not found] ` <1478597664-14799-3-git-send-email-abhimanyu.saini@nxp.com>
2016-11-14 17:12   ` [RESEND][PATCH 2/6] dt-bindings: pci: Update bindings for LS2088A Rob Herring
     [not found] ` <1478597664-14799-4-git-send-email-abhimanyu.saini@nxp.com>
2016-11-14 17:13   ` [RESEND][PATCH 3/6] dt-bindings: mtd: fsl-quadspi: Update qspi " Rob Herring
     [not found] ` <1478597664-14799-5-git-send-email-abhimanyu.saini@nxp.com>
2016-11-14 17:13   ` [RESEND][PATCH 4/6] dt-bindings: spi: Update dspi " Rob Herring
     [not found] ` <1478597664-14799-6-git-send-email-abhimanyu.saini@nxp.com>
2016-11-14 17:14   ` [RESEND][PATCH 5/6] dt-bindings: gpio: Update gpio " Rob Herring

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161114063346.GH3310@dragon \
    --to=shawnguo@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).