From: Jani Nikula <jani.nikula@intel.com>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Cc: Lucas De Marchi <lucas.demarchi@intel.com>
Subject: Re: [RFC 1/2] drm/i915: add display uncore helpers
Date: Tue, 05 Nov 2019 15:33:07 +0200 [thread overview]
Message-ID: <87eeym78j0.fsf@intel.com> (raw)
In-Reply-To: <157295766711.9970.15611348396761467196@jlahtine-desk.ger.corp.intel.com>
On Tue, 05 Nov 2019, Joonas Lahtinen <joonas.lahtinen@linux.intel.com> wrote:
> Quoting Jani Nikula (2019-10-29 12:51:55)
>> Add convenience helpers for the most common uncore operations with
>> struct drm_i915_private * as context rather than struct intel_uncore *.
>>
>> The goal is to replace all instances of I915_READ(),
>> I915_POSTING_READ(), and I915_WRITE() in display/ with these, to finally
>> be able to get rid of the implicit dev_priv local parameter use.
>>
>> The idea is that any non-u32 reads or writes are special enough that
>> they can use the intel_uncore_* functions directly.
>>
>> Cc: Chris Wilson <chris@chris-wilson.co.uk>
>> Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
>> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
>> Cc: Lucas De Marchi <lucas.demarchi@intel.com>
>> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
>> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
> <SNIP>
>
>> +++ b/drivers/gpu/drm/i915/display/intel_display_uncore.h
>> @@ -0,0 +1,36 @@
>> +/* SPDX-License-Identifier: MIT */
>> +/*
>> + * Copyright © 2019 Intel Corporation
>> + */
>> +
>> +#ifndef __INTEL_DISPLAY_UNCORE_H__
>> +#define __INTEL_DISPLAY_UNCORE_H__
>
> intel_de_uncore.c/.h for easier finding?
>
>> +
>> +#include "i915_drv.h"
>> +#include "i915_reg.h"
>> +#include "intel_uncore.h"
>> +
>> +static inline u32 intel_de_read(struct drm_i915_private *i915, i915_reg_t reg)
>
> I think it'd be good a opportunity to pass struct intel_de{,_uncore}
> as a parameter, and start grouping DE stuff underneath it?
>
> It'll of course be much bigger change.
One of the main points here was that for display code passing struct
drm_i915_private * should be the easiest thing to do. If there's a need
to group stuff within i915, fine, but no need to pass that here.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@intel.com>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Cc: Lucas De Marchi <lucas.demarchi@intel.com>
Subject: Re: [Intel-gfx] [RFC 1/2] drm/i915: add display uncore helpers
Date: Tue, 05 Nov 2019 15:33:07 +0200 [thread overview]
Message-ID: <87eeym78j0.fsf@intel.com> (raw)
Message-ID: <20191105133307.EbEQBnYNmqj8q4U3n0b8avpeGJPW19-qIvkhOV5Fx_g@z> (raw)
In-Reply-To: <157295766711.9970.15611348396761467196@jlahtine-desk.ger.corp.intel.com>
On Tue, 05 Nov 2019, Joonas Lahtinen <joonas.lahtinen@linux.intel.com> wrote:
> Quoting Jani Nikula (2019-10-29 12:51:55)
>> Add convenience helpers for the most common uncore operations with
>> struct drm_i915_private * as context rather than struct intel_uncore *.
>>
>> The goal is to replace all instances of I915_READ(),
>> I915_POSTING_READ(), and I915_WRITE() in display/ with these, to finally
>> be able to get rid of the implicit dev_priv local parameter use.
>>
>> The idea is that any non-u32 reads or writes are special enough that
>> they can use the intel_uncore_* functions directly.
>>
>> Cc: Chris Wilson <chris@chris-wilson.co.uk>
>> Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
>> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
>> Cc: Lucas De Marchi <lucas.demarchi@intel.com>
>> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
>> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
> <SNIP>
>
>> +++ b/drivers/gpu/drm/i915/display/intel_display_uncore.h
>> @@ -0,0 +1,36 @@
>> +/* SPDX-License-Identifier: MIT */
>> +/*
>> + * Copyright © 2019 Intel Corporation
>> + */
>> +
>> +#ifndef __INTEL_DISPLAY_UNCORE_H__
>> +#define __INTEL_DISPLAY_UNCORE_H__
>
> intel_de_uncore.c/.h for easier finding?
>
>> +
>> +#include "i915_drv.h"
>> +#include "i915_reg.h"
>> +#include "intel_uncore.h"
>> +
>> +static inline u32 intel_de_read(struct drm_i915_private *i915, i915_reg_t reg)
>
> I think it'd be good a opportunity to pass struct intel_de{,_uncore}
> as a parameter, and start grouping DE stuff underneath it?
>
> It'll of course be much bigger change.
One of the main points here was that for display code passing struct
drm_i915_private * should be the easiest thing to do. If there's a need
to group stuff within i915, fine, but no need to pass that here.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-11-05 13:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 10:51 [RFC 1/2] drm/i915: add display uncore helpers Jani Nikula
2019-10-29 10:51 ` [Intel-gfx] " Jani Nikula
2019-10-29 10:51 ` [RFC 2/2] drm/i915/audio: replace I915_*() calls with the new intel_de_*() calls Jani Nikula
2019-10-29 10:51 ` [Intel-gfx] " Jani Nikula
2019-10-29 14:26 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [RFC,1/2] drm/i915: add display uncore helpers Patchwork
2019-10-29 14:26 ` [Intel-gfx] " Patchwork
2019-10-29 16:02 ` ✓ Fi.CI.BAT: success " Patchwork
2019-10-29 16:02 ` [Intel-gfx] " Patchwork
2019-10-29 21:20 ` [RFC 1/2] " Daniele Ceraolo Spurio
2019-10-29 21:20 ` [Intel-gfx] " Daniele Ceraolo Spurio
2019-10-30 5:09 ` ✓ Fi.CI.IGT: success for series starting with [RFC,1/2] " Patchwork
2019-10-30 5:09 ` [Intel-gfx] " Patchwork
2019-11-05 12:41 ` [RFC 1/2] " Joonas Lahtinen
2019-11-05 12:41 ` [Intel-gfx] " Joonas Lahtinen
2019-11-05 13:33 ` Jani Nikula [this message]
2019-11-05 13:33 ` 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=87eeym78j0.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=lucas.demarchi@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