From: Jani Nikula <jani.nikula@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 5/5] drm/i915/opregion: debug log about Mailbox #2 for backlight
Date: Thu, 10 Feb 2022 18:17:30 +0200 [thread overview]
Message-ID: <8735kq8zmt.fsf@intel.com> (raw)
In-Reply-To: <YgTxYxPJ9LHjTS2v@intel.com>
On Thu, 10 Feb 2022, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> On Thu, Feb 10, 2022 at 12:36:46PM +0200, Jani Nikula wrote:
>> Start debug logging about the presence of the new Mailbox #2 for
>> backlight. Actual support is to be added later.
>>
>> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> ---
>> drivers/gpu/drm/i915/display/intel_opregion.c | 13 +++++++++----
>> 1 file changed, 9 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_opregion.c b/drivers/gpu/drm/i915/display/intel_opregion.c
>> index 6e32ed6bbf4e..b1ad11b2ebb3 100644
>> --- a/drivers/gpu/drm/i915/display/intel_opregion.c
>> +++ b/drivers/gpu/drm/i915/display/intel_opregion.c
>> @@ -47,10 +47,11 @@
>> #define OPREGION_ASLE_EXT_OFFSET 0x1C00
>>
>> #define OPREGION_SIGNATURE "IntelGraphicsMem"
>> -#define MBOX_ACPI (1<<0)
>> -#define MBOX_SWSCI (1<<1)
>> -#define MBOX_ASLE (1<<2)
>> -#define MBOX_ASLE_EXT (1<<4)
>> +#define MBOX_ACPI BIT(0) /* Mailbox #1 */
>> +#define MBOX_SWSCI BIT(1) /* Mailbox #2 (obsolete from v2.x) */
>> +#define MBOX_ASLE BIT(2) /* Mailbox #3 */
>> +#define MBOX_ASLE_EXT BIT(4) /* Mailbox #5 */
>> +#define MBOX_BACKLIGHT BIT(5) /* Mailbox #2 (valid from v3.x) */
>
> Opregion is such a lovely turd.
Tell me about it. I had to send v2 of patch 4/5 demoting the warn to dbg
because CI apparently has swsci mbox & version combos that supposedly
shouldn't exist. *sigh*.
> Series is
> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Thanks,
Jani.
>
>>
>> struct opregion_header {
>> u8 signature[16];
>> @@ -957,6 +958,10 @@ int intel_opregion_setup(struct drm_i915_private *dev_priv)
>> opregion->asle_ext = base + OPREGION_ASLE_EXT_OFFSET;
>> }
>>
>> + if (mboxes & MBOX_BACKLIGHT) {
>> + drm_dbg(&dev_priv->drm, "Mailbox #2 for backlight present\n");
>> + }
>> +
>> if (intel_load_vbt_firmware(dev_priv) == 0)
>> goto out;
>>
>> --
>> 2.30.2
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2022-02-10 16:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 10:36 [Intel-gfx] [PATCH 0/5] drm/i915/opregion: fixes and cleanups, RESEND Jani Nikula
2022-02-10 10:36 ` [Intel-gfx] [PATCH 1/5] drm/i915/opregion: check port number bounds for SWSCI display power state Jani Nikula
2022-02-10 10:36 ` [Intel-gfx] [PATCH 2/5] drm/i915/opregion: abstract the check for valid swsci function Jani Nikula
2022-02-10 10:36 ` [Intel-gfx] [PATCH 3/5] drm/i915/opregion: early exit from encoder notify if SWSCI isn't there Jani Nikula
2022-02-10 10:36 ` [Intel-gfx] [PATCH 4/5] drm/i915/opregion: handle SWSCI Mailbox #2 obsoletion Jani Nikula
2022-02-10 16:16 ` [Intel-gfx] [PATCH v2] " Jani Nikula
2022-02-10 10:36 ` [Intel-gfx] [PATCH 5/5] drm/i915/opregion: debug log about Mailbox #2 for backlight Jani Nikula
2022-02-10 11:05 ` Ville Syrjälä
2022-02-10 16:17 ` Jani Nikula [this message]
2022-02-10 14:56 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/opregion: fixes and cleanups, RESEND Patchwork
2022-02-10 15:30 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-02-10 17:06 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/opregion: fixes and cleanups, RESEND (rev2) Patchwork
2022-02-10 17:38 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-02-10 20:34 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2022-01-13 11:18 [Intel-gfx] [PATCH 0/5] drm/i915/opregion: fixes and cleanups Jani Nikula
2022-01-13 11:18 ` [Intel-gfx] [PATCH 5/5] drm/i915/opregion: debug log about Mailbox #2 for backlight Jani Nikula
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=8735kq8zmt.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.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