diff options
| author | Ville Syrjälä <ville.syrjala@linux.intel.com> | 2019-03-08 16:57:28 +0200 |
|---|---|---|
| committer | Jani Nikula <jani.nikula@intel.com> | 2019-03-08 21:23:42 +0200 |
| commit | 8a7dc40606dd94661c70f168132379abe450e83f (patch) | |
| tree | 0ed0bee563ce1e74485e9ed9ebdaa40a1967b0b2 /tools | |
| parent | d51cbd379f8ca9a46b5e426a989d59bddec96714 (diff) | |
tools/intel_vbt_decode: Dump the GPIO value/config/flag as a raw hex byte
The spec is totally confused when it comes to the GPIO flags byte.
To allow us to inspect that the decoded result at least seems
sensible let's also dump the raw byte. Should at least show if
some bits are set which we're not expecting.
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Diffstat (limited to 'tools')
| -rw-r--r-- | tools/intel_vbt_decode.c | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/tools/intel_vbt_decode.c b/tools/intel_vbt_decode.c index 2c71f084..f777e102 100644 --- a/tools/intel_vbt_decode.c +++ b/tools/intel_vbt_decode.c @@ -1190,14 +1190,14 @@ static const uint8_t *mipi_dump_gpio(const uint8_t *data, uint8_t seq_version) number = *data++; flags = *data++; - printf("\t\tGPIO index %u, number %u, set %d\n", - index, number, flags & 1); + printf("\t\tGPIO index %u, number %u, set %d (0x%02x)\n", + index, number, flags & 1, flags); } else { index = *data++; flags = *data++; - printf("\t\tGPIO index %u, source %d, set %d\n", - index, (flags >> 1) & 3, flags & 1); + printf("\t\tGPIO index %u, source %d, set %d (0x%02x)\n", + index, (flags >> 1) & 3, flags & 1, flags); } return data; |