From: Ryder Lee <ryder.lee@mediatek.com>
To: Sam Shih <sam.shih@mediatek.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Thierry Reding <thierry.reding@gmail.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
Subject: Re: [PATCH v2 9/10] dt-bindings: pwm: update bindings for MT7628 SoC
Date: Wed, 14 Aug 2019 19:52:23 +0800 [thread overview]
Message-ID: <1565783543.7006.8.camel@mtkswgap22> (raw)
In-Reply-To: <1565779497-23621-2-git-send-email-sam.shih@mediatek.com>
On Wed, 2019-08-14 at 18:43 +0800, Sam Shih wrote:
> From: sam shih <sam.shih@mediatek.com>
>
> This updates bindings for MT7628 pwm controller.
>
> Signed-off-by: Sam Shih <sam.shih@mediatek.com>
> ---
> .../devicetree/bindings/pwm/pwm-mediatek.txt | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/pwm/pwm-mediatek.txt b/Documentation/devicetree/bindings/pwm/pwm-mediatek.txt
> index c7bd5633d1eb..9d2d893a07ff 100644
> --- a/Documentation/devicetree/bindings/pwm/pwm-mediatek.txt
> +++ b/Documentation/devicetree/bindings/pwm/pwm-mediatek.txt
> @@ -21,6 +21,8 @@ Required properties:
> - pinctrl-0: One property must exist for each entry in pinctrl-names.
> See pinctrl/pinctrl-bindings.txt for details of the property values.
> - num-pwms: the number of PWM channels.
> + - clock-frequency: fix clock frequency, this is an optional property, only use in MT7628 SoC
> + for period calculation. This SoC has no complex clock tree.
Optional properties:
- clock-frequency: ...
> Example:
> pwm0: pwm@11006000 {
> @@ -40,3 +42,13 @@ Example:
> pinctrl-0 = <&pwm0_pins>;
> num-pwms = <5>;
> };
Add a blank here
> +MT7628 Example:
> + pwm: pwm@5000 {
> + compatible = "mediatek,mt7628-pwm";
> + reg = <0x5000 0x1000>;
> + #pwm-cells = <2>;
> + pinctrl-names = "default";
> + pinctrl-0 = <&pwm0_pins>, <&pwm1_pins>;
> + num-pwms = <4>;
> + clock-frequency = <100000>;
> + };
next prev parent reply other threads:[~2019-08-14 11:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 10:43 [PATCH v2 1/10] pwm: mediatek: add a property "num-pwms" Sam Shih
2019-08-14 10:43 ` [PATCH v2 2/10] pwm: mediatek: allocate the clks array dynamically Sam Shih
2019-08-14 10:43 ` [PATCH v2 3/10] pwm: mediatek: use pwm_mediatek as common prefix Sam Shih
2019-08-14 10:43 ` [PATCH v2 4/10] dt-bindings: pwm: add a property "num-pwms" Sam Shih
2019-08-14 10:43 ` [PATCH v2 5/10] arm64: dts: mt7622: add a property "num-pwms" for PWM node Sam Shih
2019-08-14 10:43 ` [PATCH v2 6/10] arm: dts: mt7623: " Sam Shih
2019-08-14 10:43 ` [PATCH v2 7/10] dt-bindings: pwm: update bindings for MT7629 SoC Sam Shih
2019-08-14 10:43 ` [PATCH v2 8/10] pwm: mediatek: add new property and fix mt7628 pwm Sam Shih
2019-08-14 10:43 ` [PATCH v2 9/10] dt-bindings: pwm: update bindings for MT7628 SoC Sam Shih
2019-08-14 11:52 ` Ryder Lee [this message]
2019-08-14 10:43 ` [PATCH v2 10/10] arm: dts: mediatek: add mt7629 pwm support Sam Shih
2019-08-14 11:47 ` Ryder Lee
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=1565783543.7006.8.camel@mtkswgap22 \
--to=ryder.lee@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=sam.shih@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