From: Sam Shih <sam.shih@mediatek.com>
To: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Thierry Reding <thierry.reding@gmail.com>
Cc: Ryder Lee <ryder.lee@mediatek.com>,
John Crispin <john@phrozen.org>,
linux-pwm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
Sam Shih <sam.shih@mediatek.com>
Subject: [PATCH v6 10/11] dt-bindings: pwm: update bindings for MT7629 SoC
Date: Thu, 29 Aug 2019 13:39:19 +0800 [thread overview]
Message-ID: <1567057160-552-11-git-send-email-sam.shih@mediatek.com> (raw)
In-Reply-To: <1567057160-552-1-git-send-email-sam.shih@mediatek.com>
From: Ryder Lee <ryder.lee@mediatek.com>
This updates bindings for MT7629 pwm controller.
Signed-off-by: Ryder Lee <ryder.lee@mediatek.com>
Signed-off-by: Sam Shih <sam.shih@mediatek.com>
Reviewed-by: Matthias Brugger <matthias.bgg@gmail.com>
---
Changes since v1:
- add a Reviewed-by tag
---
Documentation/devicetree/bindings/pwm/pwm-mediatek.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/pwm/pwm-mediatek.txt b/Documentation/devicetree/bindings/pwm/pwm-mediatek.txt
index ea95b490a913..c7bd5633d1eb 100644
--- a/Documentation/devicetree/bindings/pwm/pwm-mediatek.txt
+++ b/Documentation/devicetree/bindings/pwm/pwm-mediatek.txt
@@ -6,6 +6,7 @@ Required properties:
- "mediatek,mt7622-pwm": found on mt7622 SoC.
- "mediatek,mt7623-pwm": found on mt7623 SoC.
- "mediatek,mt7628-pwm": found on mt7628 SoC.
+ - "mediatek,mt7629-pwm", "mediatek,mt7622-pwm": found on mt7629 SoC.
- reg: physical base address and length of the controller's registers.
- #pwm-cells: must be 2. See pwm.txt in this directory for a description of
the cell format.
--
2.17.1
next prev parent reply other threads:[~2019-08-29 5:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 5:39 [PATCH v6 0/11] Add mt7629 and fix mt7628 pwm Sam Shih
2019-08-29 5:39 ` [PATCH v6 01/11] pwm: mediatek: add a property "num-pwms" Sam Shih
2019-08-29 5:39 ` [PATCH v6 02/11] pwm: mediatek: droping the check for of_device_get_match_data Sam Shih
2019-08-29 5:39 ` [PATCH v6 03/11] pwm: mediatek: remove a property "has-clks" Sam Shih
2019-08-29 5:39 ` [PATCH v6 04/11] pwm: mediatek: allocate the clks array dynamically Sam Shih
2019-08-29 5:39 ` [PATCH v6 05/11] pwm: mediatek: use pwm_mediatek as common prefix Sam Shih
2019-08-29 5:39 ` [PATCH v6 06/11] pwm: mediatek: update license and switch to SPDX tag Sam Shih
2019-08-29 5:39 ` [PATCH v6 07/11] dt-bindings: pwm: pwm-mediatek: add a property "num-pwms" Sam Shih
2019-08-29 5:39 ` [PATCH v6 08/11] arm64: dts: mt7622: add a property "num-pwms" for PWM Sam Shih
2019-08-29 5:39 ` [PATCH v6 09/11] arm: dts: mt7623: " Sam Shih
2019-08-29 5:39 ` Sam Shih [this message]
2019-08-29 19:17 ` [PATCH v6 10/11] dt-bindings: pwm: update bindings for MT7629 SoC Rob Herring
2019-08-29 5:39 ` [PATCH v6 11/11] arm: dts: mediatek: add mt7629 pwm support Sam Shih
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=1567057160-552-11-git-send-email-sam.shih@mediatek.com \
--to=sam.shih@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=john@phrozen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pwm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=ryder.lee@mediatek.com \
--cc=thierry.reding@gmail.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).