From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/opregion: remove unused lid_state
Date: Wed, 17 Jan 2024 14:46:41 +0200 [thread overview]
Message-ID: <ZafMMXiOlr3H30o4@intel.com> (raw)
In-Reply-To: <20240117122546.1551400-1-jani.nikula@intel.com>
On Wed, Jan 17, 2024 at 02:25:46PM +0200, Jani Nikula wrote:
> Not sure if lid_state has ever been used, but at least not for a long
> time. Remove it.
It was probably used when we had that disgusting lid notifier
thing, but that got killed some years ago.
>
> Suggested-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_opregion.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_opregion.c b/drivers/gpu/drm/i915/display/intel_opregion.c
> index 3f5a20f9153e..f242bb320610 100644
> --- a/drivers/gpu/drm/i915/display/intel_opregion.c
> +++ b/drivers/gpu/drm/i915/display/intel_opregion.c
> @@ -266,7 +266,6 @@ struct intel_opregion {
> void *vbt_firmware;
> const void *vbt;
> u32 vbt_size;
> - u32 *lid_state;
> struct work_struct asle_work;
> struct notifier_block acpi_notifier;
> };
> @@ -958,7 +957,6 @@ int intel_opregion_setup(struct drm_i915_private *dev_priv)
> goto err_out;
> }
> opregion->header = base;
> - opregion->lid_state = base + ACPI_CLID;
>
> drm_dbg(&dev_priv->drm, "ACPI OpRegion version %u.%u.%u\n",
> opregion->header->over.major,
> --
> 2.39.2
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2024-01-17 12:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 12:25 [PATCH] drm/i915/opregion: remove unused lid_state Jani Nikula
2024-01-17 12:46 ` Ville Syrjälä [this message]
2024-01-18 9:36 ` Jani Nikula
2024-01-17 14:10 ` ✓ Fi.CI.BAT: success for " Patchwork
2024-01-17 17:44 ` ✗ Fi.CI.IGT: failure " 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=ZafMMXiOlr3H30o4@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@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