From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "Navare, Manasi" <manasi.d.navare@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 6/6] drm/i915/display: Dump the new cdclk config values
Date: Mon, 19 Sep 2022 17:10:47 -0400 [thread overview]
Message-ID: <Yyja10cL3ltvGOnS@intel.com> (raw)
In-Reply-To: <20220919194645.GA1061693@mdnavare-mobl1.jf.intel.com>
On Mon, Sep 19, 2022 at 12:46:45PM -0700, Navare, Manasi wrote:
> On Fri, Sep 16, 2022 at 05:44:04PM -0700, Anusha Srivatsa wrote:
> > Add a helper function to get stringify values of the
> > desired cdclk action and dump it with rest of the
> > cdclk config values
> >
> > Signed-off-by: Anusha Srivatsa <anusha.srivatsa@intel.com>
>
> Please add Suggested-by: field to give proper credits as per our
> discussion. This applies to other patches as well to add proper credits
> to other folks who suggested design changes/ fixes.
> This needs to be followed as per the upstream patch review methodology.
Having the suggested by is a good way to give the proper credits when the whole
big idea and design was co authored, or started by the other developer.
We really need to mind about it. However it is not a very good thing for all
of the patches we have. Many ideas come out of conversation with many folks
and we cannot simply start adding the suggested by list with all the names
involved.
There's always a threshold there that we should mind. And the official rule
as reference is this one:
"A Suggested-by: tag indicates that the patch idea is suggested by the person
named and ensures credit to the person for the idea. Please note that this tag
should not be added without the reporter’s permission, especially if the idea
was not posted in a public forum." [1]
As a reference we don't keep adding official suggested-by tags for any and all
of the suggestions we receive during reviews. The simple name version in the
commit message is what we traditionally uses for small things.
Looking to the history of this series here I see that this patch looks like
an evolution of the previous series with small increment and suggestions from
multiple folks. Not sure if it is really worthwhile to have to add the official
tag and start to ping everyone to get the ack if it is okay or not to add it.
[1] - https://www.kernel.org/doc/html/latest/process/submitting-patches.html#using-reported-by-tested-by-reviewed-by-suggested-by-and-fixes
>
> > ---
> > drivers/gpu/drm/i915/display/intel_cdclk.c | 18 ++++++++++++++++--
> > 1 file changed, 16 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/display/intel_cdclk.c b/drivers/gpu/drm/i915/display/intel_cdclk.c
> > index bc627daade3e..12f5e4d23245 100644
> > --- a/drivers/gpu/drm/i915/display/intel_cdclk.c
> > +++ b/drivers/gpu/drm/i915/display/intel_cdclk.c
> > @@ -1688,6 +1688,19 @@ static u32 cdclk_squash_waveform(struct drm_i915_private *dev_priv,
> >
> > return 0xffff;
> > }
>
> Missing newline causing checkpatch error
>
> Manasi
>
> > +static const char *cdclk_sequence_to_string(enum cdclk_sequence cdclk_sequence)
> > +{
> > + switch (cdclk_sequence) {
> > + case CDCLK_SQUASH_ONLY:
> > + return "Squash only";
> > + case CDCLK_CRAWL_ONLY:
> > + return "Crawl only";
> > + case CDCLK_LEGACY:
> > + return "Legacy method";
> > + default:
> > + return "Not a valid cdclk sequence";
> > + }
> > +}
> >
> > static void dg2_prog_squash_ctl(struct drm_i915_private *i915, u16 waveform)
> > {
> > @@ -2083,10 +2096,11 @@ void intel_cdclk_dump_config(struct drm_i915_private *i915,
> > const struct intel_cdclk_config *cdclk_config,
> > const char *context)
> > {
> > - drm_dbg_kms(&i915->drm, "%s %d kHz, VCO %d kHz, ref %d kHz, bypass %d kHz, voltage level %d\n",
> > + drm_dbg_kms(&i915->drm, "%s %d kHz, VCO %d kHz, ref %d kHz, bypass %d kHz, voltage level %d, %s action\n",
> > context, cdclk_config->cdclk, cdclk_config->vco,
> > cdclk_config->ref, cdclk_config->bypass,
> > - cdclk_config->voltage_level);
> > + cdclk_config->voltage_level,
> > + cdclk_sequence_to_string(cdclk_config->steps->action));
> > }
> >
> > /**
> > --
> > 2.25.1
> >
next prev parent reply other threads:[~2022-09-19 21:11 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-17 0:43 [Intel-gfx] [PATCH 0/6] Introduce struct cdclk_step Anusha Srivatsa
2022-09-17 0:43 ` [Intel-gfx] [PATCH 1/6] drm/i915/display Add dg2_prog_squash_ctl() helper Anusha Srivatsa
2022-09-17 0:44 ` [Intel-gfx] [PATCH 2/6] drm/i915/display: add cdclk action struct to cdclk_config Anusha Srivatsa
2022-09-19 9:26 ` Jani Nikula
2022-09-19 19:32 ` Navare, Manasi
2022-09-19 22:42 ` Srivatsa, Anusha
2022-09-20 6:55 ` Jani Nikula
2022-09-17 0:44 ` [Intel-gfx] [PATCH 3/6] drm/i915/display: Embed the new struct steps for squashing Anusha Srivatsa
2022-09-19 9:27 ` Jani Nikula
2022-09-19 19:39 ` Navare, Manasi
2022-09-19 22:54 ` Srivatsa, Anusha
2022-09-17 0:44 ` [Intel-gfx] [PATCH 4/6] drm/i915/display: Embed the new struct steps for crawling Anusha Srivatsa
2022-09-19 9:28 ` Jani Nikula
2022-09-17 0:44 ` [Intel-gfx] [PATCH 5/6] drm/i915/display: Embed the new struct steps for modeset Anusha Srivatsa
2022-09-17 0:44 ` [Intel-gfx] [PATCH 6/6] drm/i915/display: Dump the new cdclk config values Anusha Srivatsa
2022-09-19 19:46 ` Navare, Manasi
2022-09-19 21:10 ` Rodrigo Vivi [this message]
2022-09-19 22:35 ` Navare, Manasi
2022-09-20 7:27 ` Jani Nikula
2022-09-20 18:47 ` Srivatsa, Anusha
2022-09-17 1:13 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Introduce struct cdclk_step Patchwork
2022-09-17 1:13 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-09-17 1:35 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-09-17 2:08 ` Dixit, Ashutosh
2022-09-19 6:35 ` Vudum, Lakshminarayana
2022-09-19 16:33 ` Dixit, Ashutosh
2022-09-19 4:25 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-09-19 5:42 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-09-19 6:25 ` [Intel-gfx] ✓ Fi.CI.IGT: success " Patchwork
2022-09-19 19:48 ` [Intel-gfx] [PATCH 0/6] " Navare, Manasi
2022-09-20 8:20 ` Ville Syrjälä
2022-09-20 18:48 ` Srivatsa, Anusha
2022-09-20 21:59 ` Ville Syrjälä
2022-09-23 16:56 ` Srivatsa, Anusha
2022-09-23 19:04 ` Ville Syrjälä
2022-09-26 17:21 ` Srivatsa, Anusha
2022-09-26 17:29 ` Ville Syrjälä
2022-09-26 17:55 ` Srivatsa, Anusha
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=Yyja10cL3ltvGOnS@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=manasi.d.navare@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