public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Alex Ivanov <gnidorah@ya.ru>
To: Jani Nikula <jani.nikula@linux.intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: Allow user to override PWM backlight frequency and duty cycle
Date: Wed, 17 Jan 2018 20:49:23 +0300	[thread overview]
Message-ID: <293291516211363@web30o.yandex.ru> (raw)
In-Reply-To: <87y3kw39yk.fsf@intel.com>

17.01.2018, 16:13, "Jani Nikula" <jani.nikula@linux.intel.com>:
> I'm divided. Clearly, the patch at hand is a technically better solution
> than what the blog post has.
>
> But I also think the folks over at the blog know they're directly
> hacking on graphics registers, and whatever it is they're doing is not
> supported. There's also warranted speculation this might be harmful to
> their displays.

But those using such calculators and guides don't know what precisely
they are doing, because authors only provided setup logic for *their own*
hardware, and not for other chips. This leads to more harm than it should
would be there an official way for doing overrides.

> The modulation frequency and the minimum duty cycle have been chosen by
> the OEM to work with their board design and display specs. 

Unfortunately some vendors tend to use "whatever defaults" that are not good
for humans. That's the reason why people poke with PWM registers.

> We don't have enough data to validate the values given by the user are within spec. If
> we add this, it'll get used, it'll be expected to be supported, the
> "unsafe" there will go unnoticed by folks copy-pasting the parameters
> from blogs and forums

I can rename the knobs into e.g. 
"debug_backlight_freq" and "debug_backlight_min_level" and add warnings to
descriptions so there will be FAT warnings.

> and if it breaks displays for folks, they'll be
> angry at us, not at some random blog poster.

The license on i915 driver says that its provided "as is" without any warranty.
With added warnings on kernel parameters people MUST know what they're
doing and take all responsibility.

>
> I guess damned if you do, damned if you don't.
>
> BR,
> Jani.
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2018-01-17 17:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-16 13:40 [PATCH] drm/i915: Allow user to override PWM backlight frequency and duty cycle Alex Ivanov
2018-01-16 14:41 ` ✗ Fi.CI.BAT: failure for " Patchwork
2018-01-16 15:36   ` gnidorah
2018-01-16 19:26     ` Saarinen, Jani
2018-01-17  7:22 ` [PATCH] " Alex Ivanov
2018-01-17  7:46 ` ✓ Fi.CI.BAT: success for drm/i915: Allow user to override PWM backlight frequency and duty cycle (rev2) Patchwork
2018-01-17  8:59 ` ✗ Fi.CI.IGT: warning " Patchwork
2018-01-17 13:12 ` [PATCH] drm/i915: Allow user to override PWM backlight frequency and duty cycle Jani Nikula
2018-01-17 17:49   ` Alex Ivanov [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=293291516211363@web30o.yandex.ru \
    --to=gnidorah@ya.ru \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.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