devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhangfei Gao <zhangfei.gao@linaro.org>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	Zhangfei Gao <zhangfei.gao@linaro.org>
Subject: [RFC V2:PATCH 0/2] add reset-hi3660
Date: Wed, 23 Nov 2016 16:07:54 +0800	[thread overview]
Message-ID: <1479888476-13138-1-git-send-email-zhangfei.gao@linaro.org> (raw)
In-Reply-To: <Arnd Bergmann <arnd@arndb.de>,>

Considering Arnd and Philipp suggestions, 
move reset register to dts as table instead of dts header in case of ABI issue

Zhangfei Gao (2):
  dt-bindings: Document the hi3660 reset bindings
  reset: hisilicon: add reset-hi3660

 .../bindings/reset/hisilicon,hi3660-reset.txt      |  51 ++++++++
 drivers/reset/hisilicon/Kconfig                    |   7 +
 drivers/reset/hisilicon/Makefile                   |   1 +
 drivers/reset/hisilicon/reset-hi3660.c             | 144 +++++++++++++++++++++
 4 files changed, 203 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/reset/hisilicon,hi3660-reset.txt
 create mode 100644 drivers/reset/hisilicon/reset-hi3660.c

-- 
2.7.4

       reply	other threads:[~2016-11-23  8:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Arnd Bergmann <arnd@arndb.de>
2016-11-23  8:07 ` Zhangfei Gao [this message]
2016-11-23  8:07   ` [RFC v2: PATCH 1/2] dt-bindings: Document the hi3660 reset bindings Zhangfei Gao
     [not found]     ` <1479888476-13138-2-git-send-email-zhangfei.gao-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-11-24  9:26       ` Philipp Zabel
2016-11-24  9:40         ` zhangfei
     [not found]           ` <ac3c8e65-e4f2-3a9d-452c-f270d245cf9d-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-11-24  9:50             ` Philipp Zabel
     [not found]               ` <1479981017.2472.14.camel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2016-11-24 10:20                 ` zhangfei
     [not found]                   ` <8328a235-faeb-2218-4c49-a3f282599e95-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-11-25 10:25                     ` Philipp Zabel
     [not found]                       ` <1480069523.4058.17.camel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2016-11-25 10:42                         ` zhangfei
     [not found]                           ` <e71cfe28-cd31-828f-8c7f-b4faeed5d27f-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-11-25 10:54                             ` Philipp Zabel
     [not found]                               ` <1480071241.4058.23.camel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2016-11-25 12:08                                 ` zhangfei
2016-11-30 10:03                                   ` Philipp Zabel
     [not found]         ` <1479979605.2472.4.camel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2016-11-25  3:04           ` zhangfei
     [not found]             ` <01de97d9-e910-d9f3-f081-215a78f7f4d2-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-11-25 10:27               ` Philipp Zabel
2016-11-25  2:38       ` Zhangfei Gao
2016-11-23  8:07   ` [RFC V2: PATCH 2/2] reset: hisilicon: add reset-hi3660 Zhangfei Gao

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=1479888476-13138-1-git-send-email-zhangfei.gao@linaro.org \
    --to=zhangfei.gao@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=p.zabel@pengutronix.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 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).