From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>
Cc: <intel-gfx@lists.freedesktop.org>,
Badal Nilawar <badal.nilawar@intel.com>
Subject: Re: [PATCH] drm/i915: Don't enable hwmon for selftests
Date: Wed, 10 Apr 2024 21:59:07 -0700 [thread overview]
Message-ID: <85r0fcjy04.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <ZhaZy5MQtDaP10My@ashyti-mobl2.lan>
On Wed, 10 Apr 2024 06:53:15 -0700, Andi Shyti wrote:
>
Hi Andi,
> please use "git format-patch -v 3 ..." which generates subject
> [PATCH v3] ...". Otherwise it gets confusing to see the patch
> that needs to be reviewed.
Sure, sorry!
>
> On Tue, Apr 09, 2024 at 11:05:49PM -0700, Ashutosh Dixit wrote:
> > There are no hwmon selftests so there is no need to enable hwmon for
> > selftests. So enable hwmon only for real driver load.
> >
> > v2: Move the logic inside i915_hwmon.c
> > v3: Move is_i915_selftest definition to i915_selftest.h (Badal)
> >
> > Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/10366
> > Signed-off-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
> > ---
> > drivers/gpu/drm/i915/i915_hwmon.c | 3 ++-
> > drivers/gpu/drm/i915/i915_selftest.h | 10 ++++++++++
> > 2 files changed, 12 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/i915/i915_hwmon.c b/drivers/gpu/drm/i915/i915_hwmon.c
> > index 8c3f443c8347..cf1689333ebf 100644
> > --- a/drivers/gpu/drm/i915/i915_hwmon.c
> > +++ b/drivers/gpu/drm/i915/i915_hwmon.c
> > @@ -10,6 +10,7 @@
> > #include "i915_drv.h"
> > #include "i915_hwmon.h"
> > #include "i915_reg.h"
> > +#include "i915_selftest.h"
> > #include "intel_mchbar_regs.h"
> > #include "intel_pcode.h"
> > #include "gt/intel_gt.h"
> > @@ -789,7 +790,7 @@ void i915_hwmon_register(struct drm_i915_private *i915)
> > int i;
> >
> > /* hwmon is available only for dGfx */
> > - if (!IS_DGFX(i915))
> > + if (!IS_DGFX(i915) || is_i915_selftest())
> > return;
>
> I wonder if this is the right place to put it or rather place it
> in i915_driver.c and avoid calling i915_hwmon_register() at all.
I thought it was better put it here rather than clutter up common code in
i915_driver.c.
>
> In any case, it's good:
>
> Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
Thanks.
--
Ashutosh
next prev parent reply other threads:[~2024-04-11 4:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 6:05 [PATCH] drm/i915: Don't enable hwmon for selftests Ashutosh Dixit
2024-04-10 6:45 ` ✗ Fi.CI.SPARSE: warning for drm/i915: Don't enable hwmon for selftests (rev3) Patchwork
2024-04-10 6:45 ` [PATCH] drm/i915: Don't enable hwmon for selftests Nilawar, Badal
2024-04-10 6:55 ` ✗ Fi.CI.BAT: failure for drm/i915: Don't enable hwmon for selftests (rev3) Patchwork
2024-04-10 13:53 ` [PATCH] drm/i915: Don't enable hwmon for selftests Andi Shyti
2024-04-11 4:59 ` Dixit, Ashutosh [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-10 20:07 Ashutosh Dixit
2024-04-10 4:58 Ashutosh Dixit
2024-04-10 5:17 ` Nilawar, Badal
2024-04-10 6:06 ` Dixit, Ashutosh
2024-04-10 4:28 Ashutosh Dixit
2024-04-10 4:37 ` Dixit, Ashutosh
2024-04-10 4:56 ` Nilawar, Badal
2024-04-10 11:42 ` Ville Syrjälä
2024-04-11 5:09 ` Dixit, Ashutosh
2024-04-11 10:47 ` Ville Syrjälä
2024-04-13 0:35 ` Dixit, Ashutosh
2024-04-13 0:37 ` Dixit, Ashutosh
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=85r0fcjy04.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=andi.shyti@linux.intel.com \
--cc=badal.nilawar@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
/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