From: Lee Jones <lee.jones@linaro.org>
To: Ray Jui <ray.jui@broadcom.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
bcm-kernel-feedback-list@broadcom.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] syscon: dt-bindings: Add binding doc for Broadcom iProc CDRU
Date: Thu, 7 Sep 2017 08:59:19 +0100 [thread overview]
Message-ID: <20170907075919.pcestmzjb33escmv@dell> (raw)
In-Reply-To: <1504744062-5941-2-git-send-email-ray.jui@broadcom.com>
On Wed, 06 Sep 2017, Ray Jui wrote:
> Add binding document for Broadcom iProc's Chip Device Resource Unit
> (CDRU). Multiple iProc based chips have this CDRU block that contains
> miscellaneous registers for chip or device configurations. Start with
> Stingray specific compatible string for the initial binding
>
> Signed-off-by: Ray Jui <ray.jui@broadcom.com>
> Reviewed-by: Scott Branden <scott.branden@broadcom.com>
> ---
> .../devicetree/bindings/mfd/brcm,iproc-cdru.txt | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/mfd/brcm,iproc-cdru.txt
Applied for v4.15, thanks.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2017-09-07 7:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 0:27 [PATCH 0/2] Binding document for iProc CDRU and MHB Ray Jui
2017-09-07 0:27 ` [PATCH 1/2] syscon: dt-bindings: Add binding doc for Broadcom iProc CDRU Ray Jui
2017-09-07 7:59 ` Lee Jones [this message]
[not found] ` <1504744062-5941-1-git-send-email-ray.jui-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2017-09-07 0:27 ` [PATCH 2/2] syscon: dt-bindings: Add binding document for iProc MHB block Ray Jui
[not found] ` <1504744062-5941-3-git-send-email-ray.jui-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2017-09-07 7:59 ` Lee Jones
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=20170907075919.pcestmzjb33escmv@dell \
--to=lee.jones@linaro.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=ray.jui@broadcom.com \
--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