linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: xuwei5@hisilicon.com (Wei Xu)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/7] ARM: hisi: enable HiP01 SoC
Date: Wed, 24 Dec 2014 11:19:14 +0800	[thread overview]
Message-ID: <549A30B2.5000408@hisilicon.com> (raw)
In-Reply-To: <1419390602-193123-1-git-send-email-long.wanglong@huawei.com>



On 2014/12/24 11:09, Wang Long wrote:
> Hi, Xu Wei
> 
> This series patch enable Hisilicon HiP01 SoC. The HiP01 SoC series
> chip is designed for networking product, it integrates a rich peripheral
> interfaces to support network applications and supports both one 
> core or dual cores and quad cores. The core is Cortex A9. 

Hi Wang Long,

> This series patch rebased on Linux 3.19-rc1.

Thanks!
I will pick up these patch set and sent a pull request to arm at kernel.org.

Best Regards,
Wei

> Best Regards
> 
> Wang Long (7):
>   ARM: debug: add HiP01 debug uart
>   ARM: hisi: enable HiP01 SoC
>   ARM: dts: Add hip01-ca9x2 dts file
>   ARM: config: enable ARCH_HIP01
>   ARM: hisi: add a common smp_prepares_cpus function
>   ARM: hisi: rename secondary_startup function
>   ARM: hisi: enable smp for HiP01
> 
>  .../bindings/arm/hisilicon/hisilicon.txt           |  25 +++++
>  arch/arm/Kconfig.debug                             |  10 ++
>  arch/arm/boot/dts/Makefile                         |   1 +
>  arch/arm/boot/dts/hip01-ca9x2.dts                  |  51 ++++++++++
>  arch/arm/boot/dts/hip01.dtsi                       | 110 +++++++++++++++++++++
>  arch/arm/configs/hisi_defconfig                    |   1 +
>  arch/arm/configs/multi_v7_defconfig                |   1 +
>  arch/arm/mach-hisi/Kconfig                         |   8 ++
>  arch/arm/mach-hisi/core.h                          |   5 +-
>  arch/arm/mach-hisi/headsmp.S                       |   2 +-
>  arch/arm/mach-hisi/hisilicon.c                     |  10 ++
>  arch/arm/mach-hisi/hotplug.c                       |  31 ++++++
>  arch/arm/mach-hisi/platsmp.c                       |  56 ++++++++++-
>  13 files changed, 306 insertions(+), 5 deletions(-)
>  create mode 100644 arch/arm/boot/dts/hip01-ca9x2.dts
>  create mode 100644 arch/arm/boot/dts/hip01.dtsi
> 

  parent reply	other threads:[~2014-12-24  3:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-24  3:09 [PATCH 0/7] ARM: hisi: enable HiP01 SoC Wang Long
2014-12-24  3:09 ` [PATCH 1/7] ARM: debug: add HiP01 debug uart Wang Long
2014-12-24  3:09 ` [PATCH 2/7] ARM: hisi: enable HiP01 SoC Wang Long
2014-12-24  3:09 ` [PATCH 3/7] ARM: dts: Add hip01-ca9x2 dts file Wang Long
2014-12-24  3:09 ` [PATCH 4/7] ARM: config: enable ARCH_HIP01 Wang Long
2014-12-24  3:10 ` [PATCH 5/7] ARM: hisi: add a common smp_prepares_cpus function Wang Long
2014-12-24  3:10 ` [PATCH 6/7] ARM: hisi: rename secondary_startup function Wang Long
2014-12-24  3:10 ` [PATCH 7/7] ARM: hisi: enable smp for HiP01 Wang Long
2014-12-24  3:19 ` Wei Xu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-11-28  2:15 [PATCH 0/7] ARM: hisi: enable HiP01 SoC Wang Long
2014-12-04 12:58 ` Arnd Bergmann
2014-12-05  0:34   ` Wei Xu

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=549A30B2.5000408@hisilicon.com \
    --to=xuwei5@hisilicon.com \
    --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).