From: Jani Nikula <jani.nikula@linux.intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>,
Intel GFX <intel-gfx@lists.freedesktop.org>,
DRI Devel <dri-devel@lists.freedesktop.org>
Cc: Lucas De Marchi <lucas.demarchi@intel.com>,
Matthew Auld <matthew.auld@intel.com>,
Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: [Intel-gfx] [PATCH v7 6/7] drm/i915/gt: Create per-tile RPS sysfs interfaces
Date: Fri, 06 May 2022 14:53:50 +0300 [thread overview]
Message-ID: <87y1zekhbl.fsf@intel.com> (raw)
In-Reply-To: <20220318233938.149744-7-andi.shyti@linux.intel.com>
On Sat, 19 Mar 2022, Andi Shyti <andi.shyti@linux.intel.com> wrote:
> +#define INTEL_GT_RPS_SYSFS_ATTR(_name, _mode, _show, _store) \
> + struct device_attribute dev_attr_gt_##_name = __ATTR(gt_##_name, _mode, _show, _store); \
> + struct device_attribute dev_attr_rps_##_name = __ATTR(rps_##_name, _mode, _show, _store)
Consider this macro...
> +
> +#define INTEL_GT_RPS_SYSFS_ATTR_RO(_name) \
> + INTEL_GT_RPS_SYSFS_ATTR(_name, 0444, _name##_show, NULL)
> +#define INTEL_GT_RPS_SYSFS_ATTR_RW(_name) \
> + INTEL_GT_RPS_SYSFS_ATTR(_name, 0644, _name##_show, _name##_store)
> +
> +static INTEL_GT_RPS_SYSFS_ATTR_RO(act_freq_mhz);
> +static INTEL_GT_RPS_SYSFS_ATTR_RO(cur_freq_mhz);
> +static INTEL_GT_RPS_SYSFS_ATTR_RW(boost_freq_mhz);
> +static INTEL_GT_RPS_SYSFS_ATTR_RO(RP0_freq_mhz);
> +static INTEL_GT_RPS_SYSFS_ATTR_RO(RP1_freq_mhz);
> +static INTEL_GT_RPS_SYSFS_ATTR_RO(RPn_freq_mhz);
> +static INTEL_GT_RPS_SYSFS_ATTR_RW(max_freq_mhz);
> +static INTEL_GT_RPS_SYSFS_ATTR_RW(min_freq_mhz);
...and the static keyword here.
All of the dev_attr_rps_* attributes become non-static, as the static
only applies to the dev_attr_gt_* attributes:
CHECK drivers/gpu/drm/i915/gt/intel_gt_sysfs_pm.c
drivers/gpu/drm/i915/gt/intel_gt_sysfs_pm.c:468:8: warning: symbol 'dev_attr_rps_act_freq_mhz' was not declared. Should it be static?
drivers/gpu/drm/i915/gt/intel_gt_sysfs_pm.c:469:8: warning: symbol 'dev_attr_rps_cur_freq_mhz' was not declared. Should it be static?
drivers/gpu/drm/i915/gt/intel_gt_sysfs_pm.c:470:8: warning: symbol 'dev_attr_rps_boost_freq_mhz' was not declared. Should it be static?
drivers/gpu/drm/i915/gt/intel_gt_sysfs_pm.c:471:8: warning: symbol 'dev_attr_rps_RP0_freq_mhz' was not declared. Should it be static?
drivers/gpu/drm/i915/gt/intel_gt_sysfs_pm.c:472:8: warning: symbol 'dev_attr_rps_RP1_freq_mhz' was not declared. Should it be static?
drivers/gpu/drm/i915/gt/intel_gt_sysfs_pm.c:473:8: warning: symbol 'dev_attr_rps_RPn_freq_mhz' was not declared. Should it be static?
drivers/gpu/drm/i915/gt/intel_gt_sysfs_pm.c:474:8: warning: symbol 'dev_attr_rps_max_freq_mhz' was not declared. Should it be static?
drivers/gpu/drm/i915/gt/intel_gt_sysfs_pm.c:475:8: warning: symbol 'dev_attr_rps_min_freq_mhz' was not declared. Should it be static?
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2022-05-06 11:53 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 23:39 [Intel-gfx] [PATCH v7 0/7] Introduce multitile support Andi Shyti
2022-03-18 23:39 ` Andi Shyti
2022-03-18 23:39 ` [Intel-gfx] [PATCH v7 1/7] drm/i915: Rename INTEL_REGION_LMEM with INTEL_REGION_LMEM_0 Andi Shyti
2022-03-18 23:39 ` Andi Shyti
2022-03-18 23:39 ` [Intel-gfx] [PATCH v7 2/7] drm/i915/gt: add gt_is_root() helper Andi Shyti
2022-03-18 23:39 ` Andi Shyti
2022-03-18 23:39 ` [Intel-gfx] [PATCH v7 3/7] drm/i915: Prepare for multiple GTs Andi Shyti
2022-03-18 23:39 ` Andi Shyti
2022-03-19 12:08 ` [Intel-gfx] " Michal Wajdeczko
2022-03-19 12:08 ` Michal Wajdeczko
2022-03-20 15:51 ` [Intel-gfx] " Andi Shyti
2022-03-20 15:51 ` Andi Shyti
2022-05-11 19:11 ` [Intel-gfx] " Ceraolo Spurio, Daniele
2022-05-11 19:11 ` Ceraolo Spurio, Daniele
2022-05-19 14:53 ` [Intel-gfx] " Ceraolo Spurio, Daniele
2022-05-19 14:53 ` Ceraolo Spurio, Daniele
2022-05-19 22:03 ` [Intel-gfx] " Andi Shyti
2022-05-19 22:03 ` Andi Shyti
2022-03-18 23:39 ` [Intel-gfx] [PATCH v7 4/7] drm/i915/gt: create per-tile sysfs interface Andi Shyti
2022-03-18 23:39 ` Andi Shyti
2022-03-18 23:39 ` [Intel-gfx] [PATCH v7 5/7] drm/i915/gt: Create per-tile RC6 " Andi Shyti
2022-03-18 23:39 ` Andi Shyti
2022-03-18 23:39 ` [Intel-gfx] [PATCH v7 6/7] drm/i915/gt: Create per-tile RPS sysfs interfaces Andi Shyti
2022-03-18 23:39 ` Andi Shyti
2022-05-05 13:14 ` [Intel-gfx] " Tvrtko Ursulin
2022-05-05 13:27 ` Andi Shyti
2022-05-05 13:27 ` Andi Shyti
2022-05-06 11:53 ` Jani Nikula [this message]
2022-05-06 15:21 ` Andi Shyti
2022-05-06 15:21 ` Andi Shyti
2022-03-18 23:39 ` [Intel-gfx] [PATCH v7 7/7] drm/i915/gt: Add sysfs throttle frequency interfaces Andi Shyti
2022-03-18 23:39 ` Andi Shyti
2022-03-18 23:53 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Introduce multitile support Patchwork
2022-03-18 23:55 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-03-19 0:31 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-03-19 2:06 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-03-21 10:05 ` Matthew Auld
2022-03-21 16:44 ` Vudum, Lakshminarayana
2022-03-21 16:28 ` [Intel-gfx] ✓ Fi.CI.IGT: success " Patchwork
2022-03-21 16:43 ` 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=87y1zekhbl.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=andi.shyti@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=matthew.auld@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.