From: Yixun Lan <dlan@gentoo.org>
To: Alex Elder <elder@riscstar.com>
Cc: Guodong Xu <guodong@riscstar.com>,
ukleinek@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
p.zabel@pengutronix.de, drew@pdp7.com, inochiama@gmail.com,
geert+renesas@glider.be, heylenay@4d2.org, tglx@linutronix.de,
hal.feng@starfivetech.com, unicorn_wang@outlook.com,
duje.mihanovic@skole.hr, linux-pwm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, spacemit@lists.linux.dev
Subject: Re: [PATCH 7/9] riscv: dts: spacemit: Add PWM14 backlight support for BPI-F3
Date: Fri, 11 Apr 2025 14:45:49 +0000 [thread overview]
Message-ID: <20250411144549-GYA22568@gentoo> (raw)
In-Reply-To: <d2c26d3e-787a-490e-9134-8ffe2f6b8333@riscstar.com>
Hi Alex,
On 09:23 Fri 11 Apr , Alex Elder wrote:
> On 4/11/25 9:05 AM, Yixun Lan wrote:
> >
> > On 21:14 Fri 11 Apr , Guodong Xu wrote:
> >> Add a PWM-based backlight node for the Banana Pi BPI-F3 board,
> >> using PWM14. The backlight is defined as a 'pwm-backlight' device with
> >> brightness levels and a default brightness setting. PWM14 is assigned
> >> a period length of 2000 nanoseconds.
> >>
> >> This configuration was used to verify PWM driver changes, with PWM14
> >> tested and its waveform confirmed as correct.
> >>
> >> The node status is set to "disabled", and should be enabled when the
> >> display driver is ready.
> >>
> > .. see comments below
> >> Signed-off-by: Guodong Xu <guodong@riscstar.com>
> >> ---
> >> .../boot/dts/spacemit/k1-bananapi-f3.dts | 32 +++++++++++++++++++
> >> 1 file changed, 32 insertions(+)
> >>
> >> diff --git a/arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts b/arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts
> >> index 816ef1bc358e..d04b57ddeb46 100644
> >> --- a/arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts
> >> +++ b/arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts
> >> @@ -28,6 +28,32 @@ led1 {
> >> default-state = "on";
> >> };
> >> };
> >> +
> >> + pwm_bl: lcd_backlight {
> >> + compatible = "pwm-backlight";
> >> +
> >> + pwms = <&pwm14 2000>;
> >> + brightness-levels = <
> >> + 0 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40
> >> + 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40
> >> + 40 40 40 40 40 40 40 40 40 41 42 43 44 45 46 47
> >> + 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63
> >> + 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79
> >> + 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95
> >> + 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111
> >> + 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127
> >> + 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143
> >> + 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159
> >> + 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175
> >> + 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191
> >> + 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207
> >> + 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223
> >> + 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239
> >> + 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255
> >> + >;
> >> + default-brightness-level = <100>;
> >> + status = "disabled";
> > I'm confused, has DT in board file with disabled status doesn't make sense?
> > it doesn't really useful for placeholder, even worse that functionality may not
> > verified, so I'd suggest sending along with display driver while at it..
>
> I think I suggested he include this. Guodong tested PWM using
> a backlight on a display connected to a Banana Pi PBI-F3 board.
> The above numbers come directly from the downstream code, which
> uses this PWM consistently as a display back light.
>
> But you're right, the exact set of numbers to use is dependent
> on the display used, so it's better to add them when the display
> gets integrated.
>
Ok
> The pwm14 node could update still be added here, but that too
> might as well wait until there's something to use it. So I
> think this patch can just be dropped.
>
thanks for the explanation
--
Yixun Lan (dlan)
Gentoo Linux Developer
GPG Key ID AABEFD55
next prev parent reply other threads:[~2025-04-11 14:45 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 13:14 [PATCH 0/9] pwm: Update PWM_PXA driver for SpacemiT K1 Guodong Xu
2025-04-11 13:14 ` [PATCH 1/9] dt-bindings: pwm: marvell,pxa: add optional property resets Guodong Xu
2025-04-11 16:44 ` Conor Dooley
2025-04-15 8:52 ` Philipp Zabel
2025-04-15 9:54 ` Guodong Xu
2025-04-15 10:12 ` Yixun Lan
2025-04-15 12:11 ` Alex Elder
2025-04-15 12:28 ` Yixun Lan
2025-04-16 5:18 ` Uwe Kleine-König
2025-04-16 11:33 ` Alex Elder
2025-04-16 14:56 ` Uwe Kleine-König
2025-04-11 13:14 ` [PATCH 2/9] pwm: pxa: add optional reset control Guodong Xu
2025-04-11 13:14 ` [PATCH 3/9] dt-bindings: pwm: marvell,pxa: add support to spacemit K1 Guodong Xu
2025-04-11 16:43 ` Conor Dooley
2025-04-12 4:00 ` Guodong Xu
2025-04-11 13:14 ` [PATCH 4/9] pwm: pxa: add support for " Guodong Xu
2025-04-11 13:14 ` [PATCH 5/9] riscv: dts: spacemit: add PWM support for K1 SoC Guodong Xu
2025-04-11 13:14 ` [PATCH 6/9] riscv: dts: spacemit: Add pinctrl configurations for PWM0-PWM19 Guodong Xu
2025-04-11 22:50 ` Inochi Amaoto
2025-04-14 16:42 ` Samuel Holland
2025-04-11 13:14 ` [PATCH 7/9] riscv: dts: spacemit: Add PWM14 backlight support for BPI-F3 Guodong Xu
2025-04-11 14:05 ` Yixun Lan
2025-04-11 14:23 ` Alex Elder
2025-04-11 14:45 ` Yixun Lan [this message]
2025-04-11 23:28 ` Inochi Amaoto
2025-04-12 4:22 ` Guodong Xu
2025-04-11 22:54 ` Inochi Amaoto
2025-04-14 5:58 ` Uwe Kleine-König
2025-04-14 8:03 ` Yixun Lan
2025-04-11 13:14 ` [PATCH 8/9] pwm: Kconfig: add depends on ARCH_SPACEMIT to PWM_PXA Guodong Xu
2025-04-11 13:14 ` [PATCH 9/9] riscv: defconfig: Enable PWM support for SpacemiT K1 SoC Guodong Xu
2025-04-11 22:52 ` Inochi Amaoto
2025-04-12 4:02 ` Guodong Xu
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=20250411144549-GYA22568@gentoo \
--to=dlan@gentoo.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=drew@pdp7.com \
--cc=duje.mihanovic@skole.hr \
--cc=elder@riscstar.com \
--cc=geert+renesas@glider.be \
--cc=guodong@riscstar.com \
--cc=hal.feng@starfivetech.com \
--cc=heylenay@4d2.org \
--cc=inochiama@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=p.zabel@pengutronix.de \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=spacemit@lists.linux.dev \
--cc=tglx@linutronix.de \
--cc=ukleinek@kernel.org \
--cc=unicorn_wang@outlook.com \
/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