From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 2/2] tools/intel_vbt_decode: dump all backlight data
Date: Fri, 23 Aug 2019 17:27:43 +0300 [thread overview]
Message-ID: <20190823142743.GU5942@intel.com> (raw)
In-Reply-To: <20190823122912.28180-2-jani.nikula@intel.com>
On Fri, Aug 23, 2019 at 03:29:12PM +0300, Jani Nikula wrote:
> We were missing the level and control method.
>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> ---
> tools/intel_vbt_decode.c | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/tools/intel_vbt_decode.c b/tools/intel_vbt_decode.c
> index 25399d33b8db..deba47994c89 100644
> --- a/tools/intel_vbt_decode.c
> +++ b/tools/intel_vbt_decode.c
> @@ -229,6 +229,7 @@ static void dump_backlight_info(struct context *context,
> {
> const struct bdb_lfp_backlight_data *backlight = block->data;
> const struct lfp_backlight_data_entry *blc;
> + const struct lfp_backlight_control_method *control;
> int i;
>
> if (sizeof(*blc) != backlight->entry_size) {
> @@ -250,8 +251,14 @@ static void dump_backlight_info(struct context *context,
> printf("\t\tActive low: %u\n", blc->active_low_pwm);
> printf("\t\tPWM freq: %u\n", blc->pwm_freq_hz);
> printf("\t\tMinimum brightness: %u\n", blc->min_brightness);
> - }
>
> + printf("\t\tLevel: %u\n", backlight->level[i]);
> +
Missing version check?
> + control = &backlight->backlight_control[i];
> +
> + printf("\t\tControl type: %u\n", control->type);
Decoding that to a human readable string might be nice.
> + printf("\t\tController: %u\n", control->controller);
> + }
> }
>
> static const struct {
> --
> 2.20.1
>
> _______________________________________________
> igt-dev mailing list
> igt-dev@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/igt-dev
--
Ville Syrjälä
Intel
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-08-23 14:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 12:29 [igt-dev] [PATCH i-g-t 1/2] tools/intel_vbt_decode: dump backlight data for all panels Jani Nikula
2019-08-23 12:29 ` [igt-dev] [PATCH i-g-t 2/2] tools/intel_vbt_decode: dump all backlight data Jani Nikula
2019-08-23 13:37 ` Ser, Simon
2019-08-23 14:27 ` Ville Syrjälä [this message]
2019-08-23 13:16 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/2] tools/intel_vbt_decode: dump backlight data for all panels Patchwork
2019-08-23 13:35 ` [igt-dev] [PATCH i-g-t 1/2] " Ser, Simon
2019-08-23 13:43 ` Jani Nikula
2019-08-24 9:30 ` [igt-dev] ✓ Fi.CI.IGT: success for series starting with [i-g-t,1/2] " Patchwork
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=20190823142743.GU5942@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jani.nikula@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.