linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: p.zabel@pengutronix.de (Philipp Zabel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/4] Amlogic: Meson: Add reset controller
Date: Wed, 01 Jun 2016 16:08:33 +0200	[thread overview]
Message-ID: <1464790113.3522.4.camel@pengutronix.de> (raw)
In-Reply-To: <1464614838-28107-1-git-send-email-narmstrong@baylibre.com>

Hi Kevin,

Am Montag, den 30.05.2016, 15:27 +0200 schrieb Neil Armstrong:
> Patchset to add and enable the reset controller driver on Meson SoCs platforms.
> 
> This reset controller has up to 256 reset lines with reset pulse generation only,
> so the assert and deassert calls are not available.
> 
> Depends on the patch :
>  - "reset: add devm_reset_controller_register API" [1]
> 
> Changes since v2 at http://lkml.kernel.org/r/1464169758-26975-1-git-send-email-narmstrong at baylibre.com :
> - Get back __iomem in _reset() callback
> - Get rid of MODULE_ALIAS
> 
> Changes since v1 at http://lkml.kernel.org/r/1463732875-23141-1-git-send-email-narmstrong at baylibre.com :
> - Remove _gxbb_ in names
> - Depends build on ARCH_MESON only
> - Add meson8b compatible and bindings
> - Re-indent dt-bindings headers
> - Switch to devm_ reset controller register
> - Remove platform "remove" callback
> - Update Dual BSD/GPL file headers
> 
> Changes since the RFC at http://lkml.kernel.org/r/1463148012-25988-1-git-send-email-narmstrong at baylibre.com :
> - Fix register mapping and bit defines in bindings header
> - Remove assert and unassert calls
> - Fix missing __iomem
> 
> [1] https://patchwork.kernel.org/patch/8988471/
> 
> Neil Armstrong (4):
>   reset: Add support for the Amlogic Meson SoC Reset Controller
>   dt-bindings: reset: Add bindings for the Meson SoC Reset Controller
>   ARM64: dts: amlogic: Enable Reset Controller on GXBB-based platforms
>   ARM: dts: amlogic: Enable Reset Controller on Meson8b platforms

Should I take the two device tree patches into the reset tree?
Is resolving the reset/deassert situation a prerequisite for these
patches?

regards
Philipp

  parent reply	other threads:[~2016-06-01 14:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-30 13:27 [PATCH v3 0/4] Amlogic: Meson: Add reset controller Neil Armstrong
2016-05-30 13:27 ` [PATCH v3 1/4] reset: Add support for the Amlogic Meson SoC Reset Controller Neil Armstrong
2016-05-30 13:27 ` [PATCH v3 2/4] dt-bindings: reset: Add bindings for the " Neil Armstrong
2016-05-30 13:27 ` [PATCH v3 3/4] ARM64: dts: amlogic: Enable Reset Controller on GXBB-based platforms Neil Armstrong
2016-05-30 13:27 ` [PATCH v3 4/4] ARM: dts: amlogic: Enable Reset Controller on Meson8b platforms Neil Armstrong
2016-06-01 14:08 ` Philipp Zabel [this message]
2016-06-01 17:43   ` [PATCH v3 0/4] Amlogic: Meson: Add reset controller Kevin Hilman
2016-06-02  7:42 ` Philipp Zabel
2016-08-18  2:15   ` Kevin Hilman
2016-08-18  2:28     ` Kevin Hilman
  -- strict thread matches above, loose matches on Subject: below --
2016-05-30 13:28 Neil Armstrong

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=1464790113.3522.4.camel@pengutronix.de \
    --to=p.zabel@pengutronix.de \
    --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).