All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bin Meng <bmeng.cn@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3 v3] armv8: ls1028a: Add NXP LS1028A SoC support
Date: Thu, 16 May 2019 20:09:32 +0800	[thread overview]
Message-ID: <CAEUhbmXXeyvwxPoyR31VEAs347tiLYSdCNGP2wPm4p559311CA@mail.gmail.com> (raw)
In-Reply-To: <20190410084335.16828-1-andy.tang@nxp.com>

Hi,

On Wed, Apr 10, 2019 at 4:50 PM Yuantian Tang <andy.tang@nxp.com> wrote:
>
> Ls1028a Soc is based on Layerscape Chassis Generation 3.2
> architecture with features:
>  2 ARM v8 Cortex-A72 cores, CCI400, SEC, DDR3L/4, LCD, GPU, TSN
>  ENETC, 2 USB 3.0, 2 eSDHC, 2 FlexCAN, 2 SPI, SATA, 8 I2C controllers,
>  6 LPUARTs, GPIO, SAI, qDMA, eDMA, GIC, TMU etc.
>
> Signed-off-by: Sudhanshu Gupta <sudhanshu.gupta@nxp.com>
> Signed-off-by: Rai Harninder <harninder.rai@nxp.com>
> Signed-off-by: Rajesh Bhagat <rajesh.bhagat@nxp.com>
> Signed-off-by: Bhaskar Upadhaya <Bhaskar.Upadhaya@nxp.com>
> Signed-off-by: Tang Yuantian <andy.tang@nxp.com>
> ---
> v3:
>         -- fix some issues
>  arch/arm/cpu/armv8/fsl-layerscape/Kconfig          |  39 ++-
>  arch/arm/cpu/armv8/fsl-layerscape/Makefile         |   4 +
>  arch/arm/cpu/armv8/fsl-layerscape/cpu.c            |   3 +
>  arch/arm/cpu/armv8/fsl-layerscape/doc/README.soc   |  51 ++++
>  arch/arm/cpu/armv8/fsl-layerscape/ls1028a_serdes.c |  73 ++++++
>  arch/arm/dts/fsl-ls1028a.dtsi                      | 280 +++++++++++++++++++++
>  arch/arm/include/asm/arch-fsl-layerscape/config.h  |  61 +++++
>  .../include/asm/arch-fsl-layerscape/immap_lsch3.h  |   9 +
>  arch/arm/include/asm/arch-fsl-layerscape/soc.h     |   1 +
>  .../asm/arch-fsl-layerscape/stream_id_lsch3.h      |   2 +-
>  10 files changed, 521 insertions(+), 2 deletions(-)
>  create mode 100644 arch/arm/cpu/armv8/fsl-layerscape/ls1028a_serdes.c
>  create mode 100644 arch/arm/dts/fsl-ls1028a.dtsi
>

I really would like to see complete DM driver support on this new
platform. Please consider converting appropriate codes to driver
model. If there is no proper uclass model, please propose one and
discuss it on the list. I see the existing NXP PowerPC support is
stuck in such a situation that lots of codes are still non-DM and we
are getting close to the DM deadline. I don't want to see such happens
again in the NXP ARM support.

Thanks!

Regards,
Bin

  parent reply	other threads:[~2019-05-16 12:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-10  8:43 [U-Boot] [PATCH 1/3 v3] armv8: ls1028a: Add NXP LS1028A SoC support Yuantian Tang
2019-04-10  8:43 ` [U-Boot] [PATCH 2/3 v3] armv8: ls1028ardb: Add support for LS1028ARDB platform Yuantian Tang
2019-04-10  8:43   ` [U-Boot] [PATCH 3/3 v3] armv8: ls1028aqds: Add support of LS1028AQDS Yuantian Tang
2019-05-22 12:32     ` Prabhakar Kushwaha
2019-05-22 12:32   ` [U-Boot] [PATCH 2/3 v3] armv8: ls1028ardb: Add support for LS1028ARDB platform Prabhakar Kushwaha
2019-05-16 12:09 ` Bin Meng [this message]
2019-05-17  3:23   ` [U-Boot] [EXT] Re: [PATCH 1/3 v3] armv8: ls1028a: Add NXP LS1028A SoC support Andy Tang
2019-05-17  6:32     ` Bin Meng
2019-05-21  6:45       ` Andy Tang
2019-05-21  8:14         ` Bin Meng
2019-05-21  8:23           ` Prabhakar Kushwaha
2019-05-21  8:56             ` Andy Tang
2019-05-22 12:32 ` [U-Boot] " Prabhakar Kushwaha

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=CAEUhbmXXeyvwxPoyR31VEAs347tiLYSdCNGP2wPm4p559311CA@mail.gmail.com \
    --to=bmeng.cn@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.