From: Zhou Yanjie <zhouyanjie@wanyeetech.com>
To: Aidan MacDonald <aidanmacdonald.0x0@gmail.com>,
robh+dt@kernel.org, krzk+dt@kernel.org
Cc: paul@crapouillou.net, linux-mips@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] mips: dts: ingenic: x1000: Add PWM device tree node
Date: Tue, 12 Apr 2022 02:50:13 +0800 [thread overview]
Message-ID: <3ff9ad6b-1437-3789-c180-f7f1c0ab4eab@wanyeetech.com> (raw)
In-Reply-To: <20220411155315.51769-1-aidanmacdonald.0x0@gmail.com>
Hi Aidan,
On 2022/4/11 下午11:53, Aidan MacDonald wrote:
> Copied from the jz4740 devicetree and trimmed to 5 timers, which
> is what the hardware supports.
>
> Signed-off-by: Aidan MacDonald <aidanmacdonald.0x0@gmail.com>
Tested-by: 周琰杰 (Zhou Yanjie) <zhouyanjie@wanyeetech.com>
> ---
> v2: Reduce regmap length since only the first 5 timers need to be accessed,
> and don't wrap the clock-names at 80 columns.
>
> arch/mips/boot/dts/ingenic/x1000.dtsi | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/arch/mips/boot/dts/ingenic/x1000.dtsi b/arch/mips/boot/dts/ingenic/x1000.dtsi
> index 8bd27edef216..c2cdbf947264 100644
> --- a/arch/mips/boot/dts/ingenic/x1000.dtsi
> +++ b/arch/mips/boot/dts/ingenic/x1000.dtsi
> @@ -127,6 +127,18 @@ wdt: watchdog@0 {
> clocks = <&tcu TCU_CLK_WDT>;
> clock-names = "wdt";
> };
> +
> + pwm: pwm@40 {
> + compatible = "ingenic,x1000-pwm";
> + reg = <0x40 0x50>;
> +
> + #pwm-cells = <3>;
> +
> + clocks = <&tcu TCU_CLK_TIMER0>, <&tcu TCU_CLK_TIMER1>,
> + <&tcu TCU_CLK_TIMER2>, <&tcu TCU_CLK_TIMER3>,
> + <&tcu TCU_CLK_TIMER4>;
> + clock-names = "timer0", "timer1", "timer2", "timer3", "timer4";
> + };
> };
>
> rtc: rtc@10003000 {
next prev parent reply other threads:[~2022-04-11 18:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 15:53 Aidan MacDonald
2022-04-11 18:50 ` Zhou Yanjie [this message]
2022-04-27 8:59 ` Thomas Bogendoerfer
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=3ff9ad6b-1437-3789-c180-f7f1c0ab4eab@wanyeetech.com \
--to=zhouyanjie@wanyeetech.com \
--cc=aidanmacdonald.0x0@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=paul@crapouillou.net \
--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
all inboxes | Powered by JetHome®