From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/7] drm/i915: move dpll_info to header
Date: Tue, 20 Mar 2018 11:56:11 +0200 [thread overview]
Message-ID: <20180320095611.GQ5453@intel.com> (raw)
In-Reply-To: <20180320062423.9166-2-lucas.demarchi@intel.com>
On Mon, Mar 19, 2018 at 11:24:17PM -0700, Lucas De Marchi wrote:
> This will allow the struct to be embedded in intel_shared_dpll.
>
> Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
> ---
> drivers/gpu/drm/i915/intel_dpll_mgr.c | 7 -------
> drivers/gpu/drm/i915/intel_dpll_mgr.h | 10 ++++++++++
> 2 files changed, 10 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_dpll_mgr.c b/drivers/gpu/drm/i915/intel_dpll_mgr.c
> index 51c5ae4e9116..52d6e731c3e9 100644
> --- a/drivers/gpu/drm/i915/intel_dpll_mgr.c
> +++ b/drivers/gpu/drm/i915/intel_dpll_mgr.c
> @@ -1877,13 +1877,6 @@ static void intel_ddi_pll_init(struct drm_device *dev)
> }
> }
>
> -struct dpll_info {
> - const char *name;
> - const int id;
> - const struct intel_shared_dpll_funcs *funcs;
> - uint32_t flags;
> -};
> -
> struct intel_dpll_mgr {
> const struct dpll_info *dpll_info;
>
> diff --git a/drivers/gpu/drm/i915/intel_dpll_mgr.h b/drivers/gpu/drm/i915/intel_dpll_mgr.h
> index f24ccf443d25..e99d6385478a 100644
> --- a/drivers/gpu/drm/i915/intel_dpll_mgr.h
> +++ b/drivers/gpu/drm/i915/intel_dpll_mgr.h
> @@ -205,6 +205,16 @@ struct intel_shared_dpll_funcs {
> struct intel_dpll_hw_state *hw_state);
> };
>
> +/**
> + * struct dpll_info - display PLL platform specific info
> + */
> +struct dpll_info {
> + const char *name;
> + const int id;
The const here seems pointless. Well, I guess if we go with the copy
then it might not be. Although then we get to wonder why 'flags' isn't
const.
> + const struct intel_shared_dpll_funcs *funcs;
> + uint32_t flags;
This structure seems to be poorly organized for 64bit machines.
> +};
> +
> /**
> * struct intel_shared_dpll - display PLL with tracked state and users
> */
> --
> 2.14.3
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-03-20 9:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 6:24 [PATCH 0/7] drm/i915: move dpll_info inside intel_shared_dpll Lucas De Marchi
2018-03-20 6:24 ` [PATCH 1/7] drm/i915: move dpll_info to header Lucas De Marchi
2018-03-20 9:56 ` Ville Syrjälä [this message]
2018-03-20 21:50 ` Lucas De Marchi
2018-03-21 10:25 ` Ville Syrjälä
2018-03-21 19:21 ` Lucas De Marchi
2018-03-20 6:24 ` [PATCH 2/7] drm/i915: embed dpll_info inside intel_shared_dpll Lucas De Marchi
2018-03-20 6:24 ` [PATCH 3/7] drm/i915: use funcs from dpll_info embedded in intel_shared_dpll Lucas De Marchi
2018-03-20 6:24 ` [PATCH 4/7] drm/i915: use name " Lucas De Marchi
2018-03-20 6:24 ` [PATCH 5/7] drm/i915: use id " Lucas De Marchi
2018-03-20 6:24 ` [PATCH 6/7] drm/i915: use flags " Lucas De Marchi
2018-03-20 6:24 ` [PATCH 7/7] drm/i915: rename dpll_info to intel_dpll_info Lucas De Marchi
2018-03-20 6:40 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: move dpll_info inside intel_shared_dpll Patchwork
2018-03-20 6:57 ` ✗ Fi.CI.BAT: failure " Patchwork
2018-03-20 9:57 ` [PATCH 0/7] " Ville Syrjälä
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=20180320095611.GQ5453@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--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