Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>,
	igt-dev@lists.freedesktop.org
Cc: Lucas De Marchi <lucas.demarchi@intel.com>
Subject: Re: [PATCH i-g-t] man: Add --decode to intel_reg.rst
Date: Thu, 30 May 2024 22:39:07 +0300	[thread overview]
Message-ID: <87bk4ngkdg.fsf@intel.com> (raw)
In-Reply-To: <20240530193325.1072381-1-lucas.demarchi@intel.com>

On Thu, 30 May 2024, Lucas De Marchi <lucas.demarchi@intel.com> wrote:

I like to have a commit message, even if it's short, rather than empty.

IMO something can be added while applying,

Reviewed-by: Jani Nikula <jani.nikula@intel.com>


> Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
> ---
>  man/intel_reg.rst | 22 +++++++++++-----------
>  1 file changed, 11 insertions(+), 11 deletions(-)
>
> diff --git a/man/intel_reg.rst b/man/intel_reg.rst
> index d452f7927..0e6c49927 100644
> --- a/man/intel_reg.rst
> +++ b/man/intel_reg.rst
> @@ -41,8 +41,13 @@ Some options are global, and some specific to commands.
>  --binary
>      Output binary values.
>  
> +--decode
> +    Decode registers. By default it only uses the raw offsets, unless
> +    it's a command that would otherwise not work without it or another
> +    option forces it enabled. See COMMANDS below for details.
> +
>  --all
> -    Decode registers for all known platforms.
> +    Decode registers for all known platforms. This option implies --decode.
>  
>  --mmio=FILE
>      Use MMIO bar from FILE.
> @@ -53,7 +58,7 @@ Some options are global, and some specific to commands.
>  
>  --spec=PATH
>      Read register spec from directory or file specified by PATH; see REGISTER
> -    SPEC DEFINITIONS below for details.
> +    SPEC DEFINITIONS below for details. This option implies --decode.
>  
>  --help
>      Show brief help.
> @@ -76,23 +81,18 @@ Write each VALUE to corresponding REGISTER.
>  dump [--mmio=FILE --devid=DEVID]
>  --------------------------------
>  
> -Dump all registers specified in the register spec.
> +Dump all registers specified in the register spec. The option
> +--decode is implicitely enabled.
>  
>  decode REGISTER VALUE
>  ---------------------
>  
> -Decode REGISTER VALUE.
> -
> -snapshot
> ---------
> -
> -Output the MMIO bar to stdout. The output can be used for a later invocation of
> -dump or read with the --mmio=FILE and --devid=DEVID parameters.
> +Decode REGISTER VALUE. The option --decode is implicitely enabled.
>  
>  list
>  ----
>  
> -List the known registers.
> +List the known registers. The option --decode is implicitely enabled.
>  
>  help
>  ----

-- 
Jani Nikula, Intel

  reply	other threads:[~2024-05-30 19:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-30 19:33 [PATCH i-g-t] man: Add --decode to intel_reg.rst Lucas De Marchi
2024-05-30 19:39 ` Jani Nikula [this message]
2024-05-30 19:40   ` Jani Nikula
2024-05-31 12:07     ` Lucas De Marchi
2024-05-30 20:05 ` ✗ CI.xeBAT: failure for " Patchwork
2024-05-30 20:27 ` ✓ Fi.CI.BAT: success " Patchwork
2024-05-31  0:09 ` ✗ CI.xeFULL: failure " Patchwork
2024-05-31 18:23 ` ✗ Fi.CI.IGT: " 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=87bk4ngkdg.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=lucas.demarchi@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