From: Heiko Stuebner <heiko@sntech.de>
To: Chukun Pan <amadeus@jmu.edu.cn>
Cc: amadeus@jmu.edu.cn, conor+dt@kernel.org,
devicetree@vger.kernel.org, jonas@kwiboo.se, krzk+dt@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-pwm@vger.kernel.org,
linux-rockchip@lists.infradead.org
Subject: Re: [PATCH 0/2] arm64: dts: rockchip: Add pwm nodes for RK3528
Date: Thu, 13 Mar 2025 23:14:15 +0100 [thread overview]
Message-ID: <1819496.VLH7GnMWUR@phil> (raw)
In-Reply-To: <20250313071031.1840032-1-amadeus@jmu.edu.cn>
Hi,
Am Donnerstag, 13. März 2025, 08:10:31 MEZ schrieb Chukun Pan:
> Hi,
>
> > so yes of course the pinctrl needs to be default - simply because
> > that's the only pinctrl state mainline supports.
>
> > But judging by the fact that you're discussing working vs. non-working
> > below, can you please check if we should drop the patch for 6.15 till
> > that is solved?
>
> I suggest dropping this patch first, I will send v2
> when this issue is solved.
I've dropped the patch now.
Heiko
prev parent reply other threads:[~2025-03-13 22:14 UTC|newest]
Thread overview: 20+ 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 ` [PATCH 1/2] dt-bindings: pwm: rockchip: Add rockchip,rk3528-pwm Chukun Pan
2025-03-07 15:35 ` Conor Dooley
2025-03-07 17:07 ` Uwe Kleine-König
2025-03-08 16:25 ` Heiko Stuebner
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-09 18:28 ` Jonas Karlman
2025-03-12 7:45 ` (subset) [PATCH 0/2] " Heiko Stuebner
2025-03-12 14:00 ` Jonas Karlman
2025-03-12 14:35 ` Chukun Pan
2025-03-12 15:00 ` Jonas Karlman
2025-03-12 19:38 ` Heiko Stuebner
2025-03-13 7:10 ` Chukun Pan
2025-03-13 8:22 ` Jonas Karlman
2025-03-13 9:01 ` Chukun Pan
2025-03-13 12:03 ` Jonas Karlman
2025-03-13 13:01 ` Chukun Pan
2025-03-14 15:40 ` Chukun Pan
2025-03-13 22:14 ` Heiko Stuebner [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=1819496.VLH7GnMWUR@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 \
/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).