mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Wei Xu <xuwei5@hisilicon.com>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
	<p.zabel@pengutronix.de>, <robh+dt@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<guodong.xu@linaro.org>, <john.stultz@linaro.org>,
	<xuwei5@hisilicon.com>
Subject: Re: [PATCH v2 0/2] Add Reset controller support for HI3670 SoC
Date: Mon, 15 Apr 2019 16:53:36 +0100	[thread overview]
Message-ID: <fa2bf251-56f4-fe2c-b645-4b634a87940f@hisilicon.com> (raw)
In-Reply-To: <20190215054955.788-1-manivannan.sadhasivam@linaro.org>

Hi Manivannan,

On 2/15/2019 5:49 AM, Manivannan Sadhasivam wrote:
> Hello,
> 
> This patchset adds Reset controller support for HiSilicon HI3670 SoC.
> HI3670 SoC is architecturally same as HI3660 SoC, hence the same driver
> is reused.
> 
> This patchset has been tested on HiKey970 board.
> 
> Thanks,
> Mani
> 
> Changes in v2:
> 
> * Used the DT compatible fallback approach instead of adding a new one
>   for HI3670
> 
> Manivannan Sadhasivam (2):
>   dt-bindings: reset: Add HI3670 reset controller binding
>   arm64: dts: hisilicon: hi3670: Add reset controller support
> 
>  .../devicetree/bindings/reset/hisilicon,hi3660-reset.txt   | 7 ++++---
>  arch/arm64/boot/dts/hisilicon/hi3670.dtsi                  | 6 ++++++
>  2 files changed, 10 insertions(+), 3 deletions(-)
> 

Thanks!
Applied the series to the hisilicon dts tree.

Best Regards,
Wei


      parent reply	other threads:[~2019-04-15 15:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-15  5:49 Manivannan Sadhasivam
2019-02-15  5:49 ` [PATCH v2 1/2] dt-bindings: reset: Add HI3670 reset controller binding Manivannan Sadhasivam
2019-02-15 10:25   ` Philipp Zabel
2019-02-18 20:08   ` Rob Herring
2019-02-15  5:49 ` [PATCH v2 2/2] arm64: dts: hisilicon: hi3670: Add reset controller support Manivannan Sadhasivam
2019-04-15 15:53 ` Wei Xu [this message]

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=fa2bf251-56f4-fe2c-b645-4b634a87940f@hisilicon.com \
    --to=xuwei5@hisilicon.com \
    --cc=devicetree@vger.kernel.org \
    --cc=guodong.xu@linaro.org \
    --cc=john.stultz@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=p.zabel@pengutronix.de \
    --cc=robh+dt@kernel.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
all inboxes | Powered by JetHome®