From: "Shih-Yuan Lee (FourDollars)" <fourdollars@gmail.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: A better maximum brightness for users.
Date: Tue, 10 Nov 2015 09:59:00 +0800 [thread overview]
Message-ID: <20151110015859.GA4586@localhost> (raw)
In-Reply-To: <874mgvrtzh.fsf@intel.com>
Should I improve this patch or you have rejected this patch?
Regards,
$4
On Mon, Nov 09, 2015 at 06:57:22PM +0200, Jani Nikula wrote:
> On Mon, 09 Nov 2015, Paulo Zanoni <przanoni@gmail.com> wrote:
> > 2015-11-09 8:17 GMT-02:00 Jani Nikula <jani.nikula@linux.intel.com>:
> >> On Mon, 09 Nov 2015, "Shih-Yuan Lee (FourDollars)" <sylee@canonical.com> wrote:
> >>> The PWM brightness level of Dell XPS 13 (2015) is from 10 to 937 however
> >>> the sysfs brightness level always starts from 0 so it is better to use
> >>> 927 as the sysfs maximum brightness level and it becomes easier to map
> >>> from the PWM brightness level to the sysfs brightness level.
> >>
> >> We've been thinking we should provide a fixed range to userspace
> >> instead. Say, 0-100.
> >
> > While not clearly stated, this reply and the further ones sound like a
> > rejection to his patch.
>
> I wanted to understand the motivation rather than bluntly rejecting.
>
> > I'm not really an expert on backlight, but his idea sounds simple and
> > an overall improvement to the codebase. I don't think it's fair to
> > block a simple one-line improvement based on the fact that we have an
> > idea (that may or may not be implemented) for a possibly better
> > implementation. Why not apply his patch (in case we conclude it
> > doesn't have any bugs), and then go for the 0-100 idea once someone
> > actually decides to implement it?
>
> The implementation is
>
> diff --git a/drivers/gpu/drm/i915/intel_panel.c b/drivers/gpu/drm/i915/intel_panel.c
> index a24df35e11e7..d5d86601d411 100644
> --- a/drivers/gpu/drm/i915/intel_panel.c
> +++ b/drivers/gpu/drm/i915/intel_panel.c
> @@ -1211,7 +1211,7 @@ static int intel_backlight_device_register(struct intel_connector *connector)
> * Note: Everything should work even if the backlight device max
> * presented to the userspace is arbitrarily chosen.
> */
> - props.max_brightness = panel->backlight.max;
> + props.max_brightness = 100;
> props.brightness = scale_hw_to_user(connector,
> panel->backlight.level,
> props.max_brightness);
>
> and "just" testing is required.
>
> > Besides, isn't there the possibility of having a panel that has a
> > 0-9999 range where the change from 0 to 9990 is negligible, and only
> > 9991-9999 matters, so when we scale to 0-100 it will become basically
> > a on/off switch? We all learned to never underestimate panel hardware.
>
> That's a somewhat more valid argument. The answer to that should be that
> we map the userspace range to the hardware range according to a curve
> rather than a linear mapping. See Ville's reply.
>
> BR,
> Jani.
>
>
>
> >
> >>
> >> BR,
> >> Jani.
> >>
> >>
> >>
> >>
> >>>
> >>> Signed-off-by: Shih-Yuan Lee (FourDollars) <sylee@canonical.com>
> >>> ---
> >>> drivers/gpu/drm/i915/intel_panel.c | 2 +-
> >>> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>>
> >>> diff --git a/drivers/gpu/drm/i915/intel_panel.c b/drivers/gpu/drm/i915/intel_panel.c
> >>> index a24df35..697fd4d 100644
> >>> --- a/drivers/gpu/drm/i915/intel_panel.c
> >>> +++ b/drivers/gpu/drm/i915/intel_panel.c
> >>> @@ -1211,7 +1211,7 @@ static int intel_backlight_device_register(struct intel_connector *connector)
> >>> * Note: Everything should work even if the backlight device max
> >>> * presented to the userspace is arbitrarily chosen.
> >>> */
> >>> - props.max_brightness = panel->backlight.max;
> >>> + props.max_brightness = panel->backlight.max - panel->backlight.min;
> >>> props.brightness = scale_hw_to_user(connector,
> >>> panel->backlight.level,
> >>> props.max_brightness);
> >>
> >> --
> >> Jani Nikula, Intel Open Source Technology Center
> >> _______________________________________________
> >> Intel-gfx mailing list
> >> Intel-gfx@lists.freedesktop.org
> >> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
> >
> >
> >
> > --
> > Paulo Zanoni
>
> --
> Jani Nikula, Intel Open Source Technology Center
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-11-10 1:59 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-09 6:42 [PATCH] drm/i915: A better maximum brightness for users Shih-Yuan Lee (FourDollars)
2015-11-09 10:17 ` Jani Nikula
2015-11-09 10:30 ` Shih-Yuan Lee (FourDollars)
2015-11-09 10:51 ` Jani Nikula
2015-11-09 11:54 ` Shih-Yuan Lee (FourDollars)
2015-11-09 12:58 ` Jani Nikula
2015-11-09 14:02 ` Shih-Yuan Lee (FourDollars)
2015-11-09 15:25 ` Ville Syrjälä
2015-11-09 16:02 ` Paulo Zanoni
2015-11-09 16:57 ` Jani Nikula
2015-11-10 1:59 ` Shih-Yuan Lee (FourDollars) [this message]
2015-11-10 8:01 ` [PATCH v2] drm/i915: Respect the brightness range from VBT Shih-Yuan Lee (FourDollars)
2015-11-10 10:15 ` Jani Nikula
2015-11-10 11:26 ` Shih-Yuan Lee (FourDollars)
2015-11-10 12:57 ` Jani Nikula
2015-11-10 16:11 ` Shih-Yuan Lee (FourDollars)
2015-11-11 4:11 ` [PATCH v3] drm/i915: Set brightness maximum to a fixed value 100 Shih-Yuan Lee (FourDollars)
2015-11-11 4:57 ` kbuild test robot
2015-11-11 7:31 ` [PATCH v4] " Shih-Yuan Lee (FourDollars)
2015-11-11 12:05 ` Jani Nikula
2015-11-11 13:09 ` Shih-Yuan Lee (FourDollars)
2015-11-11 14:10 ` [PATCH v5] drm/i915: Set backlight class max to 100 and respect the VBT minimum again Shih-Yuan Lee (FourDollars)
2015-11-12 5:43 ` [PATCH v6] drm/i915: respect the VBT minimum backlight brightness again Shih-Yuan Lee (FourDollars)
2015-11-12 8:08 ` Stéphane ANCELOT
2015-11-12 8:28 ` Shih-Yuan Lee (FourDollars)
2015-11-12 8:40 ` Stéphane ANCELOT
2015-11-12 8:57 ` Shih-Yuan Lee (FourDollars)
2015-11-12 9:05 ` Stéphane ANCELOT
2015-11-12 10:01 ` Shih-Yuan Lee (FourDollars)
2015-11-18 9:06 ` Stéphane ANCELOT
2015-11-18 9:11 ` Shih-Yuan Lee (FourDollars)
2015-11-12 13:44 ` Jani Nikula
2015-11-13 3:50 ` [PATCH v7] drm/i915: A better backlight class brightness range Shih-Yuan Lee (FourDollars)
2015-11-13 3:50 ` Shih-Yuan Lee (FourDollars)
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=20151110015859.GA4586@localhost \
--to=fourdollars@gmail.com \
--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