From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stephen Warren <swarren@wwwdotorg.org>
Date: Thu, 2 Jun 2016 10:59:01 -0600
Subject: [U-Boot] [PATCH 1/2] Add a reset driver framework/uclass
In-Reply-To: <573C9E39.1080105@wwwdotorg.org>
References: <1463503568-14682-1-git-send-email-swarren@wwwdotorg.org>
 <CAPnjgZ07qHz+ujxoAP0Gfmd2v9tbAaf7h70S-oBPTfBV07Nt1A@mail.gmail.com>
 <573C9E39.1080105@wwwdotorg.org>
Message-ID: <575065D5.8000602@wwwdotorg.org>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On 05/18/2016 10:54 AM, Stephen Warren wrote:
> On 05/17/2016 03:56 PM, Simon Glass wrote:
>> Hi Stephen,
>>
>> On 17 May 2016 at 10:46, Stephen Warren <swarren@wwwdotorg.org> wrote:
>>> From: Stephen Warren <swarren@nvidia.com>
>>>
>>> A reset controller is a hardware module that controls reset signals that
>>> affect other hardware modules or chips.
>>>
>>> This patch defines a standard API that connects reset clients (i.e. the
>>> drivers for devices affected by reset signals) to drivers for reset
>>> controllers/providers. Initially, DT is the only supported method for
>>> connecting the two.
>>>
>>> The DT binding specification (reset.txt) was taken from Linux kernel
>>> v4.5's Documentation/devicetree/bindings/reset/reset.txt.

Simon, any further thoughts on this?