Power on with duration; power on if brightness > 0; fix backlight device selection on KMS systems; handle multiple backlight sysfs nodes correctly

[p1r473]

Hi Linus,
On my Pi, I am able to successfully fade with a duration with rpi-backlight -b 0 -d 3. However, I cant power on/off with a duration rpi-backlight -p off -d 3. I can, however, toggle with a duration just fine rpi-backlight -p toggle -d 3
I believe we should be able to power on/off with a duration based on this line in the code, showing the intention that power setting may indeed be set with a duration.
parser.error("-p/--set-power may only be used with -d/--duration")

After checking the code, I found that powering on/off with a duration wasn't actually implemented yet
So, I added it as a feature:
-Power on/off is now supported with duration

Additionally, I found that if you set the brightness to 100 while the power is off, nothing happens. So, I added an extra 2 features:
-If setting brightness >0, turn the power on first. (This will better the user experience)
-If setting brightness to 0, turn the power off once brightness is 0. (Perhaps $ energy savings?)

I also added a quick check to the code.
-Do not try to power on if already on (This will prevent the brightness from setting to 100 if brightness is already turned up (i.e. 40) and you try to power on) which fixes #44

There is a difference between power and toggle however that needs to be reflected in the code I believe.
If its on, and you try to turn it on, nothing should happen.
If its on, and you try to toggle it, it should turn off.

Toggle does not have this problem, because if you toggle it while its already on, it will just turn off

This code prevents setting the brightness to 100 if lets say, brightness is currently 40 and you power on. Without this code, if you power on an and the screen is already, brightness will just go to 100, which is probably not what the user wanted.

[p1r473]

Update to PR:

Hi @linusg ,

On newer Raspberry Pi systems using KMS (e.g. Pi 5 with DSI), the kernel can expose multiple /sys/class/backlight entries:

• One functional device
• One or more non-functional "ghost" devices returning EIO / EINVAL
• The legacy rpi_backlight stub

The current selection logic picks the first "*-0045" entry by name, which can resolve to a non-functional device depending on enumeration order, causing rpi-backlight to fail at startup.

This PR changes Raspberry Pi backlight selection to be capability-based instead of name-based:

• Enumerate all /sys/class/backlight devices
• Probe each by writing its current brightness value back
• Select the first device that accepts the write
• Fall back to the previous *-0045 / rpi_backlight logic if probing fails

This avoids hardcoding bus numbers or model checks and works across:

• DSI Gen1 and Gen2
• KMS / FKMS
• Pi 4, Pi 5, and future revisions

Additionally, the CLI now rejects "on" and "off" as positional SYSFS_PATH values and guides users to use the proper -p flag, preventing confusing tracebacks when running:

rpi-backlight on
rpi-backlight off