From: Heiko Stuebner <heiko@sntech.de>
To: "Chukun Pan" <amadeus@jmu.edu.cn>,
"Uwe Kleine-König" <ukleinek@kernel.org>
Cc: Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Jonas Karlman <jonas@kwiboo.se>, Yao Zi <ziyao@disroot.org>,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-pwm@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: pwm: rockchip: Add rockchip,rk3528-pwm
Date: Sat, 08 Mar 2025 17:25:09 +0100 [thread overview]
Message-ID: <5942715.DvuYhMxLoT@phil> (raw)
In-Reply-To: <pnlkcc2rl7fegltovgtvp4xdxhonw72rclvhn7qmvb7xyuullm@xf5x6lcigji3>
Hi Uwe,
Am Freitag, 7. März 2025, 18:07:47 MEZ schrieb Uwe Kleine-König:
> On Fri, Mar 07, 2025 at 08:00:03PM +0800, Chukun Pan wrote:
> > Document pwm compatible for rk3528 which is fallback compatible
> > of rk3328-pwm group.
> >
> > Signed-off-by: Chukun Pan <amadeus@jmu.edu.cn>
>
> to prevent binding warnings it's probably sensible to let both patches
> go in via the same tree at the same time. Feel free to take the binding
> patch via rockchip/arm-soc.
>
> Acked-by: Uwe Kleine-König <ukleinek@kernel.org>
You already have the rk3562 binding in your for-next branch [0], which
could create merge-conflicts later on.
This patch already contains it, so should fit neatly onto your branch.
And binding warnings only come from linux-next, so won't trigger as the
pwm will feed the binding there too :-)
So I guess it might be better to take the binding through the pwm tree
and me then picking up the dts patch.
For the binding
Reviewed-by: Heiko Stuebner <heiko@sntech.de>
[0] https://web.git.kernel.org/pub/scm/linux/kernel/git/ukleinek/linux.git/commit/?h=pwm/for-next&id=058210e84b48dbb670a6bf72afaed6fbd8043a37
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: "Chukun Pan" <amadeus@jmu.edu.cn>,
"Uwe Kleine-König" <ukleinek@kernel.org>
Cc: Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Jonas Karlman <jonas@kwiboo.se>, Yao Zi <ziyao@disroot.org>,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-pwm@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: pwm: rockchip: Add rockchip,rk3528-pwm
Date: Sat, 08 Mar 2025 17:25:09 +0100 [thread overview]
Message-ID: <5942715.DvuYhMxLoT@phil> (raw)
In-Reply-To: <pnlkcc2rl7fegltovgtvp4xdxhonw72rclvhn7qmvb7xyuullm@xf5x6lcigji3>
Hi Uwe,
Am Freitag, 7. März 2025, 18:07:47 MEZ schrieb Uwe Kleine-König:
> On Fri, Mar 07, 2025 at 08:00:03PM +0800, Chukun Pan wrote:
> > Document pwm compatible for rk3528 which is fallback compatible
> > of rk3328-pwm group.
> >
> > Signed-off-by: Chukun Pan <amadeus@jmu.edu.cn>
>
> to prevent binding warnings it's probably sensible to let both patches
> go in via the same tree at the same time. Feel free to take the binding
> patch via rockchip/arm-soc.
>
> Acked-by: Uwe Kleine-König <ukleinek@kernel.org>
You already have the rk3562 binding in your for-next branch [0], which
could create merge-conflicts later on.
This patch already contains it, so should fit neatly onto your branch.
And binding warnings only come from linux-next, so won't trigger as the
pwm will feed the binding there too :-)
So I guess it might be better to take the binding through the pwm tree
and me then picking up the dts patch.
For the binding
Reviewed-by: Heiko Stuebner <heiko@sntech.de>
[0] https://web.git.kernel.org/pub/scm/linux/kernel/git/ukleinek/linux.git/commit/?h=pwm/for-next&id=058210e84b48dbb670a6bf72afaed6fbd8043a37
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-03-08 16:27 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 12:00 [PATCH 0/2] arm64: dts: rockchip: Add pwm nodes for RK3528 Chukun Pan
2025-03-07 12:00 ` Chukun Pan
2025-03-07 12:00 ` [PATCH 1/2] dt-bindings: pwm: rockchip: Add rockchip,rk3528-pwm Chukun Pan
2025-03-07 12:00 ` Chukun Pan
2025-03-07 15:35 ` Conor Dooley
2025-03-07 15:35 ` Conor Dooley
2025-03-07 17:07 ` Uwe Kleine-König
2025-03-07 17:07 ` Uwe Kleine-König
2025-03-08 16:25 ` Heiko Stuebner [this message]
2025-03-08 16:25 ` Heiko Stuebner
2025-03-09 0:24 ` Uwe Kleine-König
2025-03-09 0:24 ` Uwe Kleine-König
2025-03-07 12:00 ` [PATCH 2/2] arm64: dts: rockchip: Add pwm nodes for RK3528 Chukun Pan
2025-03-07 12:00 ` Chukun Pan
2025-03-09 18:28 ` Jonas Karlman
2025-03-09 18:28 ` Jonas Karlman
2025-03-12 7:45 ` (subset) [PATCH 0/2] " Heiko Stuebner
2025-03-12 7:45 ` Heiko Stuebner
2025-03-12 14:00 ` Jonas Karlman
2025-03-12 14:00 ` Jonas Karlman
2025-03-12 14:35 ` Chukun Pan
2025-03-12 14:35 ` Chukun Pan
2025-03-12 15:00 ` Jonas Karlman
2025-03-12 15:00 ` Jonas Karlman
2025-03-12 19:38 ` Heiko Stuebner
2025-03-12 19:38 ` Heiko Stuebner
2025-03-13 7:10 ` Chukun Pan
2025-03-13 7:10 ` Chukun Pan
2025-03-13 8:22 ` Jonas Karlman
2025-03-13 8:22 ` Jonas Karlman
2025-03-13 9:01 ` Chukun Pan
2025-03-13 9:01 ` Chukun Pan
2025-03-13 12:03 ` Jonas Karlman
2025-03-13 12:03 ` Jonas Karlman
2025-03-13 13:01 ` Chukun Pan
2025-03-13 13:01 ` Chukun Pan
2025-03-14 15:40 ` Chukun Pan
2025-03-14 15:40 ` Chukun Pan
2025-03-13 22:14 ` Heiko Stuebner
2025-03-13 22:14 ` Heiko Stuebner
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=5942715.DvuYhMxLoT@phil \
--to=heiko@sntech.de \
--cc=amadeus@jmu.edu.cn \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonas@kwiboo.se \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
--cc=ukleinek@kernel.org \
--cc=ziyao@disroot.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.