From: Florian Fainelli <f.fainelli@gmail.com>
To: Rob Herring <robh@kernel.org>, Florian Fainelli <f.fainelli@gmail.com>
Cc: linux-kernel@vger.kernel.org, Jim Quinlan <jim2101024@gmail.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Mark Rutland <mark.rutland@arm.com>,
"maintainer:BROADCOM BCM7XXX ARM ARCHITECTURE"
<bcm-kernel-feedback-list@broadcom.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"moderated list:BROADCOM BCM7XXX ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/2] dt-bindings: reset: Document BCM7216 RESCAL reset controller
Date: Thu, 19 Dec 2019 12:52:37 -0800 [thread overview]
Message-ID: <cbd9df0c-c0a5-f2af-5067-f137e49e49be@gmail.com> (raw)
In-Reply-To: <20191219204012.GA4350@bogus>
On 12/19/19 12:40 PM, Rob Herring wrote:
> On Tue, Dec 10, 2019 at 11:59:02AM -0800, Florian Fainelli wrote:
>> From: Jim Quinlan <jim2101024@gmail.com>
>>
>> BCM7216 has a special purpose RESCAL reset controller for its SATA and
>> PCIe0/1 instances. This is a simple reset controller with #reset-cells
>> set to 0.
>>
>> Signed-off-by: Jim Quinlan <jim2101024@gmail.com>
>> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
>> ---
>> .../reset/brcm,bcm7216-pcie-sata-rescal.txt | 26 +++++++++++++++++++
>> 1 file changed, 26 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/reset/brcm,bcm7216-pcie-sata-rescal.txt
>
> Can you make this DT schema format.
Yes, most certainly, I need to re-spin the reset driver as well. Thanks!
--
Florian
next prev parent reply other threads:[~2019-12-19 20:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 19:59 [PATCH 0/2] reset: Add Broadcom STB RESCAL reset controller Florian Fainelli
2019-12-10 19:59 ` [PATCH 1/2] dt-bindings: reset: Document BCM7216 " Florian Fainelli
2019-12-19 20:40 ` Rob Herring
2019-12-19 20:52 ` Florian Fainelli [this message]
2019-12-10 19:59 ` [PATCH 2/2] reset: Add Broadcom STB " Florian Fainelli
2019-12-11 9:48 ` Philipp Zabel
2019-12-11 18:12 ` Florian Fainelli
2019-12-12 10:01 ` Philipp Zabel
2019-12-30 19:05 ` Florian Fainelli
2020-01-02 11:23 ` Philipp Zabel
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=cbd9df0c-c0a5-f2af-5067-f137e49e49be@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=jim2101024@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=p.zabel@pengutronix.de \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).