From: Zhou Yanjie <zhouyanjie@wanyeetech.com>
To: Aidan MacDonald <aidanmacdonald.0x0@gmail.com>
Cc: devicetree@vger.kernel.org, krzk+dt@kernel.org,
linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org,
paul@crapouillou.net, robh+dt@kernel.org
Subject: Re: [PATCH] mips: dts: ingenic: x1000: Add PWM device tree node
Date: Tue, 12 Apr 2022 00:08:11 +0800 [thread overview]
Message-ID: <907aedbd-9277-0e65-bd33-49ec2cb7d2f9@wanyeetech.com> (raw)
In-Reply-To: <YlRNgyc6eMTgFjdH@localhost>
Hi Aidan,
On 2022/4/11 下午11:47, Aidan MacDonald wrote:
> On Mon, Apr 11, 2022 at 08:41:26PM +0800, Zhou Yanjie wrote:
>> Hi Aidan,
>>
>> On 2022/4/11 下午6:01, 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>
>>> ---
>>> arch/mips/boot/dts/ingenic/x1000.dtsi | 13 +++++++++++++
>>> 1 file changed, 13 insertions(+)
>>>
>>> diff --git a/arch/mips/boot/dts/ingenic/x1000.dtsi b/arch/mips/boot/dts/ingenic/x1000.dtsi
>>> index 8bd27edef216..0dcf37527c8e 100644
>>> --- a/arch/mips/boot/dts/ingenic/x1000.dtsi
>>> +++ b/arch/mips/boot/dts/ingenic/x1000.dtsi
>>> @@ -127,6 +127,19 @@ wdt: watchdog@0 {
>>> clocks = <&tcu TCU_CLK_WDT>;
>>> clock-names = "wdt";
>>> };
>>> +
>>> + pwm: pwm@40 {
>>> + compatible = "ingenic,x1000-pwm";
>>> + reg = <0x40 0x80>;
>>
>> It seems more reasonable to use "reg = <0x40 0x80>" since the
>> X1000 has only 5 PWM channels.
> I think you mean "reg = <0x40 0x60>" but I'll do that, thanks!
Ah, yes, what a what a stupid mistake... :(
>
>>> +
>>> + #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";
>>
>> One line is now allowed to hold at most 100 characters,
>> so it is possible to use only one line like:
>>
>> clock-names = "timer0", "timer1", "timer2", "timer3", "timer4";
>>
>> to reduce the number of lines in the dtsi file.
> Sounds good to me.
>
>>
>> Thanks and best regards!
>>
>>
>>> + };
>>> };
>>>
>>> rtc: rtc@10003000 {
> Regards,
> Aidan
prev parent reply other threads:[~2022-04-11 16:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 10:01 [PATCH] mips: dts: ingenic: x1000: Add PWM device tree node Aidan MacDonald
2022-04-11 12:41 ` Zhou Yanjie
2022-04-11 15:47 ` Aidan MacDonald
2022-04-11 16:08 ` Zhou Yanjie [this message]
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=907aedbd-9277-0e65-bd33-49ec2cb7d2f9@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