From: Matthias Brugger <matthias.bgg@gmail.com>
To: sean.wang@mediatek.com, rpurdie@rpsys.net,
jacek.anaszewski@gmail.com, pavel@ucw.cz, robh+dt@kernel.org,
mark.rutland@arm.com
Cc: devicetree@vger.kernel.org, linux-leds@vger.kernel.org,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, keyhaede@gmail.com,
lee.jones@linaro.org
Subject: Re: [PATCH v5 2/4] dt-bindings: mfd: Add LED subnode binding for MT6323 PMIC
Date: Mon, 13 Mar 2017 13:00:31 +0100 [thread overview]
Message-ID: <c86eacdb-d5c8-2f0a-11f1-1a3bc623b4b0@gmail.com> (raw)
In-Reply-To: <1488549385-19899-3-git-send-email-sean.wang@mediatek.com>
On 03/03/17 14:56, sean.wang@mediatek.com wrote:
> From: Sean Wang <sean.wang@mediatek.com>
>
> This patch adds documentation for devicetree bindings
> for LED support as the subnode of MT6323 PMIC
>
> Signed-off-by: Sean Wang <sean.wang@mediatek.com>
> ---
> Documentation/devicetree/bindings/mfd/mt6397.txt | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/mfd/mt6397.txt b/Documentation/devicetree/bindings/mfd/mt6397.txt
> index 949c85f..522a3bb 100644
> --- a/Documentation/devicetree/bindings/mfd/mt6397.txt
> +++ b/Documentation/devicetree/bindings/mfd/mt6397.txt
> @@ -6,6 +6,7 @@ MT6397/MT6323 is a multifunction device with the following sub modules:
> - Audio codec
> - GPIO
> - Clock
> +- LED
>
> It is interfaced to host controller using SPI interface by a proprietary hardware
> called PMIC wrapper or pwrap. MT6397/MT6323 MFD is a child device of pwrap.
> @@ -34,6 +35,10 @@ Optional subnodes:
> - clk
> Required properties:
> - compatible: "mediatek,mt6397-clk"
> +- led
> + Required properties:
> + - compatible: "mediatek,mt6323-led"
> + see Documentation/devicetree/bindings/leds/leds-mt6323.txt
Part of this patch is already part of linux-next:
05daab3 ("Documentation: devicetree: Add LED subnode binding for MT6323
PMIC")
Regards,
Matthias
next prev parent reply other threads:[~2017-03-13 12:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 13:56 [PATCH v5 0/4] leds: add leds-mt6323 support on MT7623 SoC sean.wang
2017-03-03 13:56 ` [PATCH v5 1/4] dt-bindings: leds: Add document bindings for leds-mt6323 sean.wang
2017-03-12 14:04 ` Rob Herring
2017-03-03 13:56 ` [PATCH v5 2/4] dt-bindings: mfd: Add LED subnode binding for MT6323 PMIC sean.wang
2017-03-12 14:05 ` Rob Herring
2017-03-13 12:00 ` Matthias Brugger [this message]
[not found] ` <c86eacdb-d5c8-2f0a-11f1-1a3bc623b4b0-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-03-13 18:35 ` Jacek Anaszewski
2017-03-14 5:40 ` Sean Wang
2017-03-03 13:56 ` [PATCH v5 3/4] leds: Add LED support " sean.wang
[not found] ` <1488549385-19899-1-git-send-email-sean.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2017-03-03 13:56 ` [PATCH v5 4/4] mfd: mt6397: Add MT6323 LED support into MT6397 driver sean.wang-NuS5LvNUpcJWk0Htik3J/w
2017-03-14 14:42 ` 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=c86eacdb-d5c8-2f0a-11f1-1a3bc623b4b0@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jacek.anaszewski@gmail.com \
--cc=keyhaede@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.org \
--cc=rpurdie@rpsys.net \
--cc=sean.wang@mediatek.com \
/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).