From: Johan Jonker <jbx6244@gmail.com>
To: "Sebastian Reichel" <sebastian.reichel@collabora.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Rob Herring <robh@kernel.org>, Heiko Stuebner <heiko@sntech.de>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
kernel@collabora.com, linux-pwm@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>
Subject: Re: [PATCH 1/1] dt-bindings: pwm: rockchip: Add description for rk3588
Date: Wed, 28 Sep 2022 20:29:35 +0200 [thread overview]
Message-ID: <66b5b616-ae9f-a1aa-e2b5-450f570cfcdd@gmail.com> (raw)
In-Reply-To: <20220913141601.fi6pl2xdo4xmtw6t@mercury.elektranox.org>
On 9/13/22 16:16, Sebastian Reichel wrote:
> Hi,
>
> On Tue, Sep 13, 2022 at 11:12:02AM +0200, Uwe Kleine-König wrote:
>> Hello Rob,
>>
>> On Thu, Sep 01, 2022 at 02:14:55PM -0500, Rob Herring wrote:
>>> On Thu, 01 Sep 2022 15:55:23 +0200, Sebastian Reichel wrote:
>>>> Add "rockchip,rk3588-pwm" compatible string for PWM nodes found
>>>> on a rk3588 platform.
>>>>
>>>> Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com>
>>>> ---
>>>> No driver changes required.
>>>> ---
>>>> Documentation/devicetree/bindings/pwm/pwm-rockchip.yaml | 1 +
>>>> 1 file changed, 1 insertion(+)
>>>>
>>>
>>> Running 'make dtbs_check' with the schema in this patch gives the
>>> following warnings. Consider if they are expected or the schema is
>>> incorrect. These may not be new warnings.
>>>
>>> Note that it is not yet a requirement to have 0 warnings for dtbs_check.
>>> This will change in the future.
>>
>> Is this a list of *new* warnings, or is the report (somewhat) orthogonal
>> to the actual change and you just used the opportunity that someone
>> touched the pwm-rockchip binding to point out that there is some cleanup
>> to do?
>>
>>> Full log is available here: https://patchwork.ozlabs.org/patch/
>>
>> Hm, that gives me a 404.
>
> This is an existing problem with the rv1108 binding.
> The rk3588 does not have pwm interrupts.
Hi,
Could you recheck?
From Rockchip RK3588 Datasheet V0.1-20210727.pdf:
PWM
Support 16 on-chip PWMs(PWM0~PWM15) with interrupt-based operation
Programmable pre-scaled operation to bus clock and then further scaled
Embedded 32-bit timer/counter facility
Support capture mode
Support continuous mode or one-shot mode
Provides reference mode and output various duty-cycle waveform
Optimized for IR application for PWM3, PWM7, PWM11, PWM15
===
ARM: dts: rk3288: add the interrupts property for PWM
https://github.com/rockchip-linux/kernel/commit/16b7b284618d1652e694f6286f575ce82f5f03e5
Comment:
At the moment, we can find the remotectl pwm is needed on box.
We can add the property for all PWMs. AFAIK, the pwm driver don't use it
but the drivers/input/remotectl/rockchip_pwm_remotectl.c
===
From Rockchip RK3568 TRM Part1 V1.1-20210301.pdf
8-bit repeat counter for one-shot operation. One-shot operation will produce N + 1
periods of the waveform, where N is the repeat counter value, and generates a
single interrupt at the end of operation
Continuous mode generates the waveform continuously, and does not generates
any interrupts
>
> -- Sebastian
>
>
> _______________________________________________
> Linux-rockchip mailing list
> Linux-rockchip@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2022-09-28 18:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 13:55 [PATCH 1/1] dt-bindings: pwm: rockchip: Add description for rk3588 Sebastian Reichel
2022-09-01 15:02 ` Krzysztof Kozlowski
2022-09-01 18:49 ` Heiko Stübner
2022-09-01 19:14 ` Rob Herring
2022-09-13 9:12 ` Uwe Kleine-König
2022-09-13 14:16 ` Sebastian Reichel
2022-09-14 7:33 ` Uwe Kleine-König
2022-09-28 11:48 ` Thierry Reding
2022-09-28 13:06 ` Sebastian Reichel
2022-09-28 13:56 ` Thierry Reding
2022-09-28 15:18 ` Johan Jonker
2022-09-28 16:11 ` Sebastian Reichel
2022-09-28 18:29 ` Johan Jonker [this message]
2022-09-29 13:10 ` Sebastian Reichel
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=66b5b616-ae9f-a1aa-e2b5-450f570cfcdd@gmail.com \
--to=jbx6244@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=kernel@collabora.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sebastian.reichel@collabora.com \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
/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).