Dominik Riebeling wrote:
> Also, those settings have been there since years and I don't see a
> point in removing them at all.

The point is that the fading code is ballooning. As we add the feature on more targets, we have to add more conditions and settings due to different targets implementing it differently.

We currently have no less than four configuration defines dealing with backlight fading:

#define HAVE_BACKLIGHT_PWM_FADING
#define HAVE_BACKLIGHT_SET_FADING
#define USE_BACKLIGHT_CUSTOM_FADING_BOOL
#define USE_BACKLIGHT_SW_FADING

We also have four different settings for it.

Changing the backlight fading times is such a micro-management option that I think it simply is not useful enough to warrant the mess it causes. I'd go so far as call it configuration in absurdum.

The parallell question I like to ask is: If this is so important, why don't we have a time setting (or two!) for the fade-on-stop feature?

-- 
Björn